Open Andymulb opened 1 year ago
https://developer.tesla.com/docs/fleet-api Die Authentifizierung passt leider nicht so gut zu iobroker.
Seems now to be mandatory for executing remote commands:
https://owner-api.teslamotors.com/api/1/vehicles/XXXXXXXX/command/door_unlock
AxiosError: Request failed with status code 403
{"response":null,"error":"Tesla Vehicle Command Protocol required, please refer to the documentation here: https://developer.tesla.com/docs/fleet-api#2023-10-09-rest-api-vehicle-commands-endpoint-deprecation-warning","error_description":""}
I need an account to implement a workaround for the new api
How can I help?
account credential with an affected car via mail tombox2020@gmail.com
Tesla Solar Charger already implemented the new Tesla API. It is supported since release 2.23.0. Maybe something similar could be implemented for iobroker?
is there a solution in sight?
Any updates here?
I am using this adapter for solar surplus charge. This has been working fine for the last 12 months. Now this is broken. So any updates here?
Just to be sure, sending commands is fully broken until someone fixes this, right? Only receiving data is possible atm?
@TA2k I sent you an E-Mail.
Hey, has anybody a solution? I now have the same Problem.
Any updates or workarounds?
Any updates or workarounds?
I am still waiting...too ;-)
The best way to send commands to your tesla is now a BleHttpProxy like this one: https://github.com/wimaha/TeslaBleHttpProxy
I am using it together with evcc for solar surplus charging.
Homeassistant community integration for Tesla implemented the new Tesla API. Maybe it makes sense to have a look at their solution. It's a bit complicated but it's working for me since month
Tesla announced its official API. I just wanted to inform you about it.