OCPP apparently confirmed to be coming to Tesla Wall Connector Gen 3

[pssturges]

This will be very useful for some users

https://www.solarquotes.com.au/blog/tesla-ev-charger-sa/

[geertvanheusden]

It appears that the certification process is finished as well: https://openchargealliance.org/wp-content/uploads/2024/10/Certificate_OCA.0016.0900.CS_Tesla.pdf

[mfuchs1984]

Plug the charger into the vehicle, authorization, charging starts, charging finishes. And the transaction is complete

That's not correct. Transactions end when the car is unplugged or a transaction is actively stopped. A finished charging process does not automatically stop an active transaction.

[lincolnharmer]

Correct, that's a good clarification. However, the OCPP chargers I've tested don't provide an easy way to start providing power once the car has reached its charge setpoint. While you're correct the transaction is not complete, charging is effectively complete because resuming charging is not straight forward.

[mfuchs1984]

Most likely more a problem of the backend than of the charger.

[lincolnharmer]

Yeah it can be worked around via the backend. But what happens if the internet is spotty or the backend goes offline? Just trying to think through this. What specific OCPP configuration settings would need to be in place on the client side to allow power to flow to the vehicle to power things like keeping the battery warm after the vehicle met it's charging setpoint and the server is offline?

[mfuchs1984]

Free charging or local RFID authentication, then the charger starts the transaction by itself and does not need the backend to do so. I control my charger through modbus via evcc and at the same time, I use Home Assistant as an ocpp backend to visualize things. The backend is completely passive.

[TheJDJ13]

Something happening maybe?

(From https://www.notateslaapp.com/tesla-app-updates/version/4.47.5/release-notes)

Wall Connector OCPP Support

Here are some of the phrases related to the OCPP Wall Connector:
Access Wall Connector Charging Data
Control Your Wall Connector
This is a supported Open Charge Point Protocol (OCPP) program.
Remove access at any time in Vehicle Charging settings.
Share Charging Data for Reimbursement


[jonasman]

So i think i figured this out.

so far there is one partner using tesla ocpp called Monta Charge, they have an app.

you add your gen 3 to their app via serial number then you need to press a button that will jump you to the tesla app and configure the ocpp there. You also need to add an address in one of the supported countries (check the last link for all countries).
the jump is done via a deeplink/universal link so i was not yet able to see what data is passed to try to fake the ocpp via any app.

The idea is that you can then pass the home charging cost to your employer. The Monta app will handle all that for you by counting kWh?

the Monta app supports both gen 3 and gen 3 MID.
the MID is sold in Denmark at least.

My Monta app is a bit buggy so im not able to do the final config where we should jump to the tesla app :( can someone try and post a screenshot?

Some links:
https://monta.com/en/supported-charge-points/tesla-wall-connector-3/

https://shop.tesla.com/da_dk/product/wall-connector

https://www.tesla.com/da_dk/support/charging/wall-connector/charging-reimbursements

[kevbenjam]

"Just to clarify, the Tesla Universal Wall Connector, in its newer model does support OCPP 1.6, making it compatible with Monta.

We’ve seen successful integrations with these units when configured correctly and connected to a stable internet source.

If you're looking to connect a Tesla charger to Monta, we recommend verifying that the unit is indeed the Universal Wall Connector and that OCPP is enabled in its settings."

It seems that the Tesla Wall Connector Gen 3 is still not supporting OCPP currently, while the Tesla Universal Wall Connector in some cases does.

[jonasman]

@kevbenjam the API says the non universal is supported, there is some OCPP field saying true

[jonasman]

@kevbenjam you might be right, another site saying that only the universal charger supports OCPP: https://support.plugchoice.com/en/articles/15420517-how-to-connect-tesla-wall-connector

[creedda]

Is this only in certain regions?

I have a universal wall connector and just did a pass through the Tesla app and did not find an option to enable ocpp.

In the US.

[jonasman]

Is this only in certain regions?

I have a universal wall connector and just did a pass through the Tesla app and did not find an option to enable ocpp.

In the US.

no idea. But i saw in reddit another user in the US that cannot set up the OCPP https://www.reddit.com/r/TeslaSupport/comments/1uydyby/is_the_tesla_universal_wall_connector_compatible/ so this is probably locked somehow.

I think the universal charger is US only

[cicob]

Hi, I bumped into this page. Is this old news, or does that bring some hope that the residential EU wall-charger will include OCPP in the (near) future?

https://openchargealliance.org/certified-companies/
(search for "tesla")

[cicob]

Sorry, I see that's exactly what you've already covered in this thread.

[jonasman]

Guys, the box supports OCPP. So this discussion is not really going anywhere. We just need to figure out how to configure it. There is an API that reports ocpp enabled. Joao Sent from my iPhone On 27 Nov 2025, at 19:25, mfuchs1984 ***@***.***> wrote:  Free charging or local RFID authentication, then the charger starts the transaction by itself and does not need the backend to do so. I control my charger through modbus via evcc and at the same time, I use Home Assistant as an ocpp backend to visualize things. The backend is completely passive. — Reply to this email directly, view it on GitHub<#15588 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANOMXXCDS5YDW3GWS7UD4D364XZJAVCNFSM6AAAAABM46CSK2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMBZHA4TENY>. You are receiving this because you commented.Message ID: ***@***.***>

[jonasman]

Update, monta app now opens the Tesla app. However in my case the Tesla app does nothing

[JohanMeppelinkDRA]

Same issue. Tesla app does nothing

[rbrooklyn]

Ahoy hoy…

[jonasman]

The button to open the Tesla app stop working here. Which country did you try? We just need to figure out the deeplink now

…

Sent from my iPhone On 27 Dec 2025, at 18:06, rbrooklyn ***@***.***> wrote:  Ahoy hoy… IMG_1621.png (view on web)<https://github.com/user-attachments/assets/fdccf4e2-a1c5-4bf1-9953-4a5101ef7939> IMG_1622.png (view on web)<https://github.com/user-attachments/assets/1825fcb0-3ebf-4191-bf12-b788b3396948> IMG_1623.png (view on web)<https://github.com/user-attachments/assets/fa40ce18-8e04-4a0c-948d-3789a0e0dd00> IMG_1624.png (view on web)<https://github.com/user-attachments/assets/6801e024-da90-4756-ab3c-de3a3a7384a6> IMG_1625.png (view on web)<https://github.com/user-attachments/assets/62a49489-87f4-438d-951f-0db6c2ff975e> IMG_1626.png (view on web)<https://github.com/user-attachments/assets/dfddb22a-a62c-4d6c-abc7-665323d4ca53> — Reply to this email directly, view it on GitHub<#15588 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANOMXUKA777KX4LM3PIHET4D2U6LAVCNFSM6AAAAABM46CSK2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMZVGI3DANI>. You are receiving this because you commented.Message ID: ***@***.***>

[rbrooklyn]

United Kingdom.

Happy to do more testing if you can talk me through what you need.

[rbrooklyn]

A bit more information here, as well as partners (just Monta currently) and supported countries: https://www.tesla.com/en_gb/support/charging/wall-connector/charging-reimbursements

I have a feeling that this will only work with Monta currently, even if the deep link is found, I suspect something will be hard coded to prevent anything other than Monta from working. The Monta app only asked for the charger's serial number and it automagically did the rest. No IP address etc was needed.

[jonasman]

I found a video of the whole Monta process: <https://x.com/theteslaspace/status/1856304080391397521?s=46> [nRX8RMtflq9_LkHu.jpg] BREAKING: as the first in the world, Tesla wall connectors can now connect to Monta. This is a win for EV fleets and employees who want to use home charging reimbursement. FULL PRESS RELEASE: Monta will integrate with Tesla’s home Wall Connector to offer a fully digital EV [https://pbs.twimg.com/profile_images/1428061023471235077/O3JztFdT_200x200.jpg]<https://x.com/theteslaspace/status/1856304080391397521?s=46> The Tesla Space ***@***.***) 25 likes · 3 replies<https://x.com/theteslaspace/status/1856304080391397521?s=46> x.com<https://x.com/theteslaspace/status/1856304080391397521?s=46>

…

Sent from my iPhone On 27 Dec 2025, at 19:21, rbrooklyn ***@***.***> wrote:  A bit more information here, as well as partners (just Monta currently) and supported countries: https://www.tesla.com/en_gb/support/charging/wall-connector/charging-reimbursements I have a feeling that this will only work with Monta currently, even if the deep link is found, I suspect something will be hard coded to prevent anything other than Monta from working. The Monta app only asked for the charger's serial number and it automagically did the rest. No IP address etc was needed. — Reply to this email directly, view it on GitHub<#15588 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANOMXR2II5TXCBFBBXGCGT4D25ZZAVCNFSM6AAAAABM46CSK2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMZVGI4TKMI>. You are receiving this because you commented.Message ID: ***@***.***>

[rbrooklyn]

Here is an intent being fired from Monta to pair the charger. I told Monta that my serial number was 1. When I changed the 1 to 2, then the "1&cp_id=1" portion changed to "2&cp_id=2":

Action: android.intent.action.VIEW
Data: https://www.tesla.com/dl/ocpp#connect_url=wss://ocpp.monta.app/1&cp_id=1&auth_key=MONTA&root_cert_id=monta&sec_prof=2&return_url=monta://home&cst_provider_name=monta
URI: intent://www.tesla.com/dl/ocpp#connect_url=wss://ocpp.monta.app/1&cp_id=1&auth_key=MONTA&root_cert_id=monta&sec_prof=2&return_url=monta://home&cst_provider_name=monta#Intent;scheme=https;launchFlags=0x3000400;end
Flags:
FLAG_ACTIVITY_REQUIRE_NON_BROWSER
FLAG_ACTIVITY_PREVIOUS_IS_TOP
FLAG_ACTIVITY_FORWARD_RESULT
Extras:
com.android.browser.headers
Bundle[EMPTY_PARCEL]

The issue I think we have is that the root_cert_if and the auth_key are probably locking the ocpp.monta.app domain in. And even then you may need to parse the response you get from the Tesla app to actually figure out how to connect (which I suspect will be the easy part)

I don't currently have a working ocpp server in my setup, and don't have time to set this up right now. But maybe someone with a ocpp server and/or the time can have a play and see if they get anywhere.

[rbrooklyn]

Woomp woomp

Editing the url is not enough, sadly.

[jonasman]

Hm, so maybe we need to fake some dns entries in our local network?

[rbrooklyn]

Way ahead of you. Already tried that.

It sort of works. The Tesla app accepts the bullshit I'm sending it when I change the string to ws://ocpp.monta.app:9000 (note the protocol changing to ws to remove security, and I added in a port) and seems to work okay, however, the charger never connects and I just see "connecting" or "invalid" come up on the app and the ocpp server never reacts.

I suspect the root_cert_id setting in the URL is our undoing on this one. If it's omitted the app refuses to continue.

Tesla are outsmarting us on this one.

[jonasman]

So we need tesla to open up the ocpp access outside the charging reimbursement feature :(

…

Sent from my iPhone On 6 Apr 2026, at 22:19, rbrooklyn ***@***.***> wrote:  Way ahead of you. Already tried that. It sort of works. The Tesla app accepts the bullshit I'm sending it when I change the string to ws://ocpp.monta.app:9000 (note the protocol changing to ws to remove security, and I added in a port) and seems to work okay, however, the charger never connects and I just see "connecting" or "invalid" come up on the app and the ocpp server never reacts. I suspect the root_cert_id setting in the URL is our undoing on this one. If it's omitted the app refuses to continue. Tesla are outsmarting us on this one. — Reply to this email directly, view it on GitHub<#15588 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANOMXRTD5BTAW7ULDKS43T4UP7L7AVCNFSM6AAAAABM46CSK2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNBWG4ZTIMI>. You are receiving this because you commented.Message ID: ***@***.***>

[rbrooklyn]

I think you’re SOL currently.

for what it’s worth I removed the Monta connection for now. It was too slow and glitchy and clearly not designed for what I wanted so you’re probably not missing out.

[unpplex]

do you have any news? I have a gen 3 wall connector and I live in Italy, I've tried everything but the Tesla app opens and from then on it's impossible to continue, no popup appears

[jonasman]

@rbrooklyn i think the idea is more to be able to send a custom OCPP config to the WC3 than to use Monta at all.

[unpplex]

I contacted Monta support and I didn't receive any help, I also contacted Tesla support but they also don't know what to do or how to solve it, it seems absurd to me

[rbrooklyn]

@jonasman yes, that’s what I have been trying to do.

The wall connector refuses to work with the configuration. It’s either blocked at the Tesla app or the wall connector errors.

[jonasman]

Hi, does anyone have a universal wall connector?

according to this site it is the only one supported and the OCPP is configured via the Tesla App:
https://support.plugchoice.com/en/articles/15420517-how-to-connect-tesla-wall-connector

[jonasman]

update: a guy with this charger says he cannot see the OCPP setting https://www.reddit.com/r/TeslaSupport/comments/1uydyby/is_the_tesla_universal_wall_connector_compatible/

[rbrooklyn]

universal wall connector?

That's the American variant I believe. I think many might get them confused with the Gen3s (to be fair they look identical externally).

Seems very dumb to only have settings on the US variant and not others. Hopefully Tesla will rectify that in a future software update.