Tesla Wall charger (TWC3) support via vehicle-command API for Tesla vehicles

[yipikaye]

Is your feature request related to a problem? Please describe.
The introduction of the Tesla vehicle-command SDK has changed the APIs for Tesla vehicle management. The TWC3 charger cannot be controled via EVCC and must be managed via changing the charging parameters on the Tesla vehicle via the SDK. The new SDK requires additional Public/Private key pairs and authority from the user for EVCC to manage the vehicle.

Describe the solution you'd like
The new vehicle-command SDK is only implemented in a read-only implementation. Read-write is needed to re-indroduce the EVCC functionallity that existed with the old API. The API gateway is now region specific so additional checks are needed to use the correct gateway: You can query the users region and appropriate fleet-api URL so you should be able to dynamically assign it
https://developer.tesla.com/docs/fleet-api?shell#region

Describe alternatives you've considered
Other projects are also tackeling this same challenge. To date there are implementations by;

• https://chargehq.net/
• https://github.com/pkuehnel/TeslaSolarCharger
• https://www.tessie.com/

Additional context
Thank you

[vtml]

It will be good if this is implemented to control charging, as the charging is then controlled directly on the vehicle itself. That means any charger (including mobile chargers) can work with a Tesla vehicle, very much like Charge HQ.

[andig]

Couple of things:

1. Make sure that Add Tesla using official vehicle command library #10802 works for you, i.e. you can retrieve soc.
2. Get a Tesla developer account- follow steps at https://github.com/teslamotors/vehicle-command and note Open-source / self-hosted applications teslamotors/vehicle-command#111
3. Any insight about other self-hosted solutions is welcome. Key issue here is, that controlling the vehicle needs a private key installed on the vehicle. evcc does have a private key that can be installed but we obviously not distribute that.
4. When 1+2 are completed we can look into implementation. Depends on Proposal: create Account from refreshing oauth2.TokenSource teslamotors/vehicle-command#29.

[FuR1u5]

Hi @andig

if you need someone to test, you are welcome to get in touch. I have two evcc instances available, each with a TWC3 and a Tesla.

[andig]

Problem is that in order to send vehicle commands, one must have the private key corresponding to the public key installed on the vehicle. That private key is a SECRET. One way of not distributing the secret might be running a vehicle command proxy (see https://github.com/teslamotors/vehicle-command/tree/main/cmd/tesla-http-proxy).

Not sure if thats doable- needs more investigation:

Do not listen on a network interface without adding client authentication. Unauthorized clients may
be used to create excessive traffic from your IP address to Tesla's servers, which Tesla may respond
to by rate limiting or blocking your connections.

...which would bring us to client certificates.

[yipikaye]

This sounds promising, the app would run the proxy or is it something EVCC needs to host?

[infinus]

@andig confirmed #1 is now working in US and can retrieve SOC with latest nightly. @yipikaye can you try and see if it works for you too?

[yipikaye]

@infinus yes I plan to, I'm away for a few days and for some reason it seems I can't ssh into home 😔
When is it going into the stable branch, I'll see if I can get it done before then

[FuR1u5]

Problem is that in order to send vehicle commands, one must have the private key corresponding to the public key installed on the vehicle. That private key is a SECRET. One way of not distributing the secret might be running a vehicle command proxy (see https://github.com/teslamotors/vehicle-command/tree/main/cmd/tesla-http-proxy).

Not sure if thats doable- needs more investigation:

Do not listen on a network interface without adding client authentication. Unauthorized clients may
be used to create excessive traffic from your IP address to Tesla's servers, which Tesla may respond
to by rate limiting or blocking your connections.

...which would bring us to client certificates.

Sounds great, can't wait to test it :)

[manuelmrmorgado]

@andig May I suggest a creation of Template based on Tessie API? https://developer.tessie.com/docs/about
They provide their users an API that I guess works the same way Tesla API used to work.

Thanks! ;)

[infinus]

@manuelmrmorgado

Tessie has private servers and can host the client secret which is needed and should not be shared. EVCC is open sourced and usually run at home so they have can’t protect those like Tessie can. They are looking at setting up a proxy but that it a work in progress. It is much easier for projects like Tessie, teslafi, or Optiwatt to introduce these changes than open source projects like EVCC or Teslamate. It’s trying to find a delicate balance between ease of use, privacy, and security.

[yipikaye]

This proxy seems promising!
It's great to see the improvements and the active team. This is what open source is all about!