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

yipikaye · 2024-01-25T09:06:18Z

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;

Additional context
Thank you

vtml · 2024-01-25T09:15:10Z

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 · 2024-01-25T09:30:22Z

Couple of things:

Make sure that Add Tesla using official vehicle command library #10802 works for you, i.e. you can retrieve soc.
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
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.
When 1+2 are completed we can look into implementation. Depends on Proposal: create Account from refreshing oauth2.TokenSource teslamotors/vehicle-command#29.

FuR1u5 · 2024-01-26T15:21:35Z

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 · 2024-01-26T16:54:32Z

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 · 2024-01-26T22:06:56Z

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

infinus · 2024-01-27T03:32:20Z

@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 · 2024-01-27T05:54:18Z

@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 · 2024-01-27T11:14:35Z

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 · 2024-01-30T02:27:49Z

@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 · 2024-01-30T03:11:13Z

@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 · 2024-01-30T04:31:15Z

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

andig · 2024-01-30T06:31:33Z

Feel free to open a PR for Tessi integration.

andig · 2024-02-01T08:46:57Z

@haroldboom this Issue is about TWC. Please don't cross-post. Tesla integration is confirmed working. Feel free to share login information with info@evcc.io for further diagnosis.

andig · 2024-02-01T08:49:39Z

@manuelmrmorgado re Tessi that would mean that the old Tesla integration would continue to work 1:1 by swapping the URL. That's an interesting idea.
Since we're using https://github.com/bogosj/tesla under the hood, swapping URI and adding API key would need to be done there. I suggest to open an issue with bogosj/tesla.

andig · 2024-02-01T12:20:39Z

...which is why this issue exists.

andig · 2024-02-01T14:15:01Z

Has anything changed here?

No and that‘s why we have this issue open. It is not about login errors!

haroldboom · 2024-02-04T11:29:10Z

Hi @andig is the proxy in the nightly or still in draft stage?

andig · 2024-02-04T11:40:14Z

See PR- it is nowhere yet.

mucki12 · 2024-02-06T07:01:59Z

Don't know if it helps, but here they are also looking at a solution with a proxy:
https://github.com/llamafilm/tesla-http-proxy-addon?tab=readme-ov-file

yipikaye · 2024-02-15T23:16:06Z

Small thing. It would be good if tesla.evcc.io had an english translation. I missed the TWC step the first time.

Working 100%. You @andig sir are a true gentleman! 🧐

TheJDJ13 · 2024-02-15T23:18:44Z

I get a 500 server error but I have generated new tokens... Do i need to revoke the existing and start again?

I did not need to revoke existing.

Did you continue below and add the virtual key using the QR to add it in the Tesla app?

yipikaye · 2024-02-15T23:20:22Z

No i missed that last step as I cannot read German :) I updated the above comment.
It is working well!

TheJDJ13 · 2024-02-15T23:21:33Z

No i missed that last step as I cannot read German :) I updated the above comment. It is working well!

I had to have my browser translate the page to English so I could read that part.

yipikaye · 2024-02-15T23:33:13Z

Is anyone else getting server errors from the proxy?
ERROR 2024/02/16 10:22:11 charger disable: Post "https://tesla.evcc.io/api/1/vehicles/LRWYHCEK5PC906710/command/charge_stop": read tcp [2406:2d40:406f:d900:9e8c:167c:3ba4:ba50]:60448->[2a09:8280:1::69:9409]:443: read: connection reset by peer

TheJDJ13 · 2024-02-15T23:36:03Z

Is anyone else getting server errors from the proxy? ERROR 2024/02/16 10:22:11 charger disable: Post "https://tesla.evcc.io/api/1/vehicles/LRWYHCEK5PC906710/command/charge_stop": read tcp [2406:2d40:406f:d900:9e8c:167c:3ba4:ba50]:60448->[2a09:8280:1::69:9409]:443: read: connection reset by peer

I am not seeing that or any other errors.

yipikaye · 2024-02-15T23:39:44Z

Hmm something has gone wrong. It was working for a short while, now:
ERROR 2024/02/16 10:38:42 charger enable: 500 Internal Server Error

yipikaye · 2024-02-15T23:45:00Z

It appears the car went to sleep and with the proxy it doesn't wake. I restarted the EVCC service and got the following

Feb 16 10:43:28 raspberrypi evcc[11093]: [main  ] ERROR 2024/02/16 10:43:28 vehicle status: asleep
Feb 16 10:43:28 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:43:28 max charge current 5A: vehicle not capable of current control
Feb 16 10:43:30 raspberrypi evcc[11093]: [lp-1  ] INFO 2024/02/16 10:43:30 vehicle updated: unknown -> Pikachu

yipikaye · 2024-02-15T23:48:29Z

Yes, if I wake the car via the moble app then the charging control starts working properly again with no intervention on EVCC from me.

So we have a minor wake the vehicle issue :)

Feb 16 10:43:42 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:43:42 vehicle odometer: asleep
Feb 16 10:43:42 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:43:42 vehicle soc: asleep
Feb 16 10:43:45 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:43:45 max charge current 5A: 500 Internal Server Error
Feb 16 10:44:00 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:44:00 max charge current 5A: 500 Internal Server Error
Feb 16 10:44:15 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:44:15 max charge current 5A: 500 Internal Server Error
Feb 16 10:44:30 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:44:30 max charge current 5A: 500 Internal Server Error
Feb 16 10:44:44 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:44:44 max charge current 5A: 500 Internal Server Error
Feb 16 10:44:59 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:44:59 max charge current 5A: 500 Internal Server Error
Feb 16 10:45:15 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:45:15 max charge current 5A: 500 Internal Server Error
Feb 16 10:45:42 raspberrypi evcc[11093]: [lp-1  ] INFO 2024/02/16 10:45:42 start charging ->
Feb 16 10:46:27 raspberrypi evcc[11093]: [lp-1  ] INFO 2024/02/16 10:46:27 stop charging <-

haroldboom · 2024-02-16T00:21:35Z

Yes, if I wake the car via the moble app then the charging control starts working properly again with no intervention on EVCC from me.

So we have a minor wake the vehicle issue :)

Feb 16 10:43:42 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:43:42 vehicle odometer: asleep
Feb 16 10:43:42 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:43:42 vehicle soc: asleep
Feb 16 10:43:45 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:43:45 max charge current 5A: 500 Internal Server Error
Feb 16 10:44:00 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:44:00 max charge current 5A: 500 Internal Server Error
Feb 16 10:44:15 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:44:15 max charge current 5A: 500 Internal Server Error
Feb 16 10:44:30 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:44:30 max charge current 5A: 500 Internal Server Error
Feb 16 10:44:44 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:44:44 max charge current 5A: 500 Internal Server Error
Feb 16 10:44:59 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:44:59 max charge current 5A: 500 Internal Server Error
Feb 16 10:45:15 raspberrypi evcc[11093]: [lp-1  ] ERROR 2024/02/16 10:45:15 max charge current 5A: 500 Internal Server Error
Feb 16 10:45:42 raspberrypi evcc[11093]: [lp-1  ] INFO 2024/02/16 10:45:42 start charging ->
Feb 16 10:46:27 raspberrypi evcc[11093]: [lp-1  ] INFO 2024/02/16 10:46:27 stop charging <-

Hi all, I also have the same issue, EVCC cant wake the vehicle to charge. If I wake manually with the app it will start. Also getting the
evcc[632]: [lp-1 ] ERROR 2024/02/16 00:20:02 max charge current 5A: 500 Internal Server Error when trying to wake

TheJDJ13 · 2024-02-16T00:43:02Z

No errors for me so far, but I will test this.

As soon as I run out of sunlight today, I will set my car to higher than the current SOC. I'll leave it alone until tomorrow and see if it wakes up to charge when there is enough solar. I generally get enough sun by 10AM (PST).

haroldboom · 2024-02-16T01:38:35Z

No errors for me so far, but I will test this.

As soon as I run out of sunlight today, I will set my car to higher than the current SOC. I'll leave it alone until tomorrow and see if it wakes up to charge when there is enough solar. I generally get enough sun by 10AM (PST).

I just let the car go to sleep and switched EVCC to fast or minpv and that forces the error for me

oysteing · 2024-02-16T03:22:39Z

Seems I need to rebuild the proxy, too. Will shortly.

Done- should offer the virtual key now.

I seem to get 500 Server when trying to control the vehicle

Virtual key installed?! Likely not. Trace log for Tesla would help.

I can also confirm that vehicle control works after installing the virtual key. Thanks for the great work!

yipikaye · 2024-02-16T03:51:40Z

I just let the car go to sleep and switched EVCC to fast or minpv and that forces the error for me

Yes I can replicate the same too.

TheJDJ13 · 2024-02-16T04:26:58Z

I just let the car go to sleep and switched EVCC to fast or minpv and that forces the error for me

Yes I can replicate the same too.

OK I can replicate it as well. That is not something I will do normally so I am going to continue my planned test, but I expect I will see that same error.

haroldboom · 2024-02-16T04:36:40Z

I think the vehicle is also going to sleep while charging and EVCC cant change the current, see below

Feb 16 04:05:07 testrig evcc[630]: [lp-1 ] ERROR 2024/02/16 04:05:07 max charge current 27A: Post "https://tesla.evcc.io/api/1/vehicles/LRWYHCFS3NC428511/command/set_charging_amps": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Feb 16 04:05:12 testrig evcc[630]: [site ] DEBUG 2024/02/16 04:05:12 ----
Feb 16 04:05:12 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:12 charge power: 391W
Feb 16 04:05:12 testrig evcc[630]: [site ] DEBUG 2024/02/16 04:05:12 pv power: 8030W
Feb 16 04:05:12 testrig evcc[630]: [site ] DEBUG 2024/02/16 04:05:12 grid power: -4388W
Feb 16 04:05:12 testrig evcc[630]: [site ] DEBUG 2024/02/16 04:05:12 site power: -4388W
Feb 16 04:05:12 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:12 charge voltages: [244 1.5 0]V
Feb 16 04:05:12 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:12 detected connected phases: 1p
Feb 16 04:05:12 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:12 charge currents: [1.6 0 0.2]A
Feb 16 04:05:12 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:12 detected active phases: 1p
Feb 16 04:05:12 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:12 charger status: C
Feb 16 04:05:12 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:12 soc estimated: 72.38% (vehicle: 72.00%)
Feb 16 04:05:12 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:12 vehicle soc: 72%
Feb 16 04:05:12 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:12 vehicle soc limit: 100%
Feb 16 04:05:12 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:12 vehicle range: 301km
Feb 16 04:05:12 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:12 pv charge current: 22.7A = 3.6A + 19.1A (-4388W @ 1p)
Feb 16 04:05:22 testrig evcc[630]: [lp-1 ] ERROR 2024/02/16 04:05:22 max charge current 22A: Post "https://tesla.evcc.io/api/1/vehicles/LRWYHCFS3NC428511/command/set_charging_amps": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Feb 16 04:05:27 testrig evcc[630]: [site ] DEBUG 2024/02/16 04:05:27 ----
Feb 16 04:05:27 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:27 charge power: 756W
Feb 16 04:05:27 testrig evcc[630]: [site ] DEBUG 2024/02/16 04:05:27 pv power: 8143W
Feb 16 04:05:27 testrig evcc[630]: [site ] DEBUG 2024/02/16 04:05:27 grid power: -5033W
Feb 16 04:05:27 testrig evcc[630]: [site ] DEBUG 2024/02/16 04:05:27 site power: -5033W
Feb 16 04:05:27 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:27 charge voltages: [244 1.5 0]V
Feb 16 04:05:27 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:27 detected connected phases: 1p
Feb 16 04:05:27 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:27 charge currents: [3.1 0 0.2]A
Feb 16 04:05:27 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:27 detected active phases: 1p
Feb 16 04:05:27 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:27 charger status: C
Feb 16 04:05:27 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:27 soc estimated: 72.39% (vehicle: 72.00%)
Feb 16 04:05:27 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:27 vehicle soc: 72%
Feb 16 04:05:27 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:27 vehicle soc limit: 100%
Feb 16 04:05:27 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:27 vehicle range: 301km
Feb 16 04:05:27 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:27 pv charge current: 27A = 5.1A + 21.9A (-5033W @ 1p)
Feb 16 04:05:37 testrig evcc[630]: [lp-1 ] ERROR 2024/02/16 04:05:37 max charge current 26A: Post "https://tesla.evcc.io/api/1/vehicles/LRWYHCFS3NC428511/command/set_charging_amps": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Feb 16 04:05:42 testrig evcc[630]: [site ] DEBUG 2024/02/16 04:05:42 ----
Feb 16 04:05:42 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:42 charge power: 1193W
Feb 16 04:05:42 testrig evcc[630]: [site ] DEBUG 2024/02/16 04:05:42 pv power: 8156W
Feb 16 04:05:42 testrig evcc[630]: [site ] DEBUG 2024/02/16 04:05:42 grid power: -4579W
Feb 16 04:05:42 testrig evcc[630]: [site ] DEBUG 2024/02/16 04:05:42 site power: -4579W
Feb 16 04:05:42 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:42 charge voltages: [244 1.5 0]V
Feb 16 04:05:42 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:42 detected connected phases: 1p
Feb 16 04:05:42 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:42 charge currents: [4.9 0 0.2]A
Feb 16 04:05:42 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:42 detected active phases: 1p
Feb 16 04:05:42 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:42 charger status: C
Feb 16 04:05:42 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:42 soc estimated: 72.39% (vehicle: 72.00%)
Feb 16 04:05:42 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:42 vehicle soc: 72%
Feb 16 04:05:42 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:42 vehicle soc limit: 100%
Feb 16 04:05:42 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:42 vehicle range: 301km
Feb 16 04:05:42 testrig evcc[630]: [lp-1 ] DEBUG 2024/02/16 04:05:42 pv charge current: 26.8A = 6.9A + 19.9A (-4579W @ 1p)
Feb 16 04:05:52 testrig evcc[630]: [lp-1 ] ERROR 2024/02/16 04:05:52 max charge current 26A: Post "https://tesla.evcc.io/api/1/vehicles/LRWYHCFS3NC428511/command/set_charging_amps": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

When I opened the app and woke the car up the errors stopped

Stacykid · 2024-02-16T07:08:53Z

I am apparently also on the new API because it stopped working recently and I have been following this issue.

I have now done everything exactly according to the instructions but my vehicle is only specified as a guest vehicle.
I even removed the token from Tesla again and recreated it, also did the latest update, but it didn't change anything

Can anyone help me?

yipikaye · 2024-02-16T07:32:35Z

Did you install the nightly build, setup the car again with the new template and new tokens?

Stacykid · 2024-02-16T07:39:08Z

Did you install the nightly build, setup the car again with the new template and new tokens?

I have done the following:
-evcc update, but only the one that is available for everyone
-new token for Tesla with all approvals
-added sponsoring (is also recognised)

Could it be because I only did a normal update to 124.2 and the unstable nightly is not integrated?
I am not familiar with nightly

mucki12 · 2024-02-16T07:40:32Z

Of course - as always with new implementations

Likemike24 · 2024-02-16T07:40:52Z

Could it be because I only did a normal update to 124.2 and the unstable nightly is not integrated?

The changes are only in the nightly for now. You have to switch the release channel to get the new integration.

Stacykid · 2024-02-16T07:42:49Z

I assumed, since it is already on the homepage, that it works without nightly.

I'll be patient until it's official.

Thank you

yipikaye · 2024-02-16T07:43:37Z

Its not working properly anyway (vehicle wakeup).
This is why nightly builds exist, so us gunie pigs can find issues :)

mucki12 · 2024-02-16T08:42:49Z

Sorry - but I also have a stupid question:
is the template Tesla-proxy again a pure combination between TWC3 and Tesla, or should the control (when recognizing the Tesla vehicle) also be done with other wallboxes via the Fleet API?

FuR1u5 · 2024-02-16T08:54:41Z

Seems I need to rebuild the proxy, too. Will shortly.

@andig Great, after the change everything works perfectly. The virtual key is created via the evcc page and you can add it in the Tesla app. The control via evcc also works so far :)

Many thanks for your work!

yipikaye · 2024-02-16T09:41:55Z

everything works perfectly.

Until your car goes to sleep ;)

andig · 2024-02-16T10:56:28Z

@yipikaye please open new issue with trace log. I guess api responses are different than before and hence we may not be detecting this. Handling on evcc side hasn't changed afaia.

yipikaye · 2024-02-16T11:14:54Z

let the car go to sleep and switched EVCC to fast or minpv and that forces the error for me

New issue here: #12294

TheJDJ13 · 2024-02-16T17:45:52Z

I just let the car go to sleep and switched EVCC to fast or minpv and that forces the error for me

Yes I can replicate the same too.

OK I can replicate it as well. That is not something I will do normally so I am going to continue my planned test, but I expect I will see that same error.

Yes, as expected, I did see the error when I had enough excess solar to start charging. After waking the car up with app, charging started.

yipikaye mentioned this issue Jan 25, 2024

Tesla Integration via official vehicle-command library #10460

Closed

andig added the enhancement New feature or request label Jan 25, 2024

andig mentioned this issue Jan 26, 2024

Tesla Powerwall Battery Control not working anymore #11875

Closed

andig mentioned this issue Jan 27, 2024

Tesla Command: add proxy #11893

Closed

This comment was marked as off-topic.

Sign in to view

litithio mentioned this issue Feb 1, 2024

Change to new Tesla API doesn't work #11985

Closed

andig mentioned this issue Feb 1, 2024

Support swap-in api replacement based on vehicle-command proxy like Tessi bogosj/tesla#125

Open

This comment was marked as resolved.

Sign in to view

andig mentioned this issue Feb 5, 2024

Tesla M3 Laderegelung funktioniert nicht mehr #12073

Closed

litithio mentioned this issue Feb 6, 2024

Tesla m3 kann immer noch nicht gesteuert werden #12097

Closed

yipikaye mentioned this issue Feb 16, 2024

Tesla Proxy for TWC3 does not wake vehicle from sleep #12294

Closed

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

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

Comments

yipikaye commented Jan 25, 2024

vtml commented Jan 25, 2024

andig commented Jan 25, 2024

FuR1u5 commented Jan 26, 2024 • edited Loading

andig commented Jan 26, 2024 • edited Loading

yipikaye commented Jan 26, 2024

infinus commented Jan 27, 2024

yipikaye commented Jan 27, 2024

FuR1u5 commented Jan 27, 2024

manuelmrmorgado commented Jan 30, 2024

infinus commented Jan 30, 2024

yipikaye commented Jan 30, 2024

andig commented Jan 30, 2024

This comment was marked as off-topic.

This comment was marked as off-topic.

andig commented Feb 1, 2024

andig commented Feb 1, 2024 • edited Loading

andig commented Feb 1, 2024

This comment was marked as resolved.

andig commented Feb 1, 2024 • edited Loading

haroldboom commented Feb 4, 2024

andig commented Feb 4, 2024

mucki12 commented Feb 6, 2024

yipikaye commented Feb 15, 2024 • edited Loading

TheJDJ13 commented Feb 15, 2024 • edited Loading

yipikaye commented Feb 15, 2024

TheJDJ13 commented Feb 15, 2024

yipikaye commented Feb 15, 2024

TheJDJ13 commented Feb 15, 2024

yipikaye commented Feb 15, 2024

yipikaye commented Feb 15, 2024 • edited Loading

yipikaye commented Feb 15, 2024 • edited Loading

haroldboom commented Feb 16, 2024

TheJDJ13 commented Feb 16, 2024

haroldboom commented Feb 16, 2024

oysteing commented Feb 16, 2024

yipikaye commented Feb 16, 2024

TheJDJ13 commented Feb 16, 2024

haroldboom commented Feb 16, 2024 • edited Loading

Stacykid commented Feb 16, 2024 • edited Loading

yipikaye commented Feb 16, 2024

Stacykid commented Feb 16, 2024 • edited Loading

mucki12 commented Feb 16, 2024

Likemike24 commented Feb 16, 2024

Stacykid commented Feb 16, 2024

yipikaye commented Feb 16, 2024

mucki12 commented Feb 16, 2024

FuR1u5 commented Feb 16, 2024 • edited Loading

yipikaye commented Feb 16, 2024

andig commented Feb 16, 2024

yipikaye commented Feb 16, 2024

TheJDJ13 commented Feb 16, 2024

FuR1u5 commented Jan 26, 2024 •

edited

Loading

andig commented Jan 26, 2024 •

edited

Loading

andig commented Feb 1, 2024 •

edited

Loading

andig commented Feb 1, 2024 •

edited

Loading

yipikaye commented Feb 15, 2024 •

edited

Loading

TheJDJ13 commented Feb 15, 2024 •

edited

Loading

yipikaye commented Feb 15, 2024 •

edited

Loading

yipikaye commented Feb 15, 2024 •

edited

Loading

haroldboom commented Feb 16, 2024 •

edited

Loading

Stacykid commented Feb 16, 2024 •

edited

Loading

Stacykid commented Feb 16, 2024 •

edited

Loading

FuR1u5 commented Feb 16, 2024 •

edited

Loading