In https://github.com/evcc-io/evcc/pull/10802 I've done some prototyping with vehicle-commands library. Basically, same requests as with this module are executed against fleet-api endpoints. Option 1 would be to switch this module to use the new endpoints.
What does not work is sending commands- these must now be signed. This can be achieved by using the new API or by running a Tesla-provided proxy that converts REST API to signed commands.
That said I will experiment some with which changes would need to be made to connect to arbitrary endpoint urls for simple requests or commands. Especially the response definitions are not part of the vehicle-commands library and still super helpful.
In https://github.com/evcc-io/evcc/pull/10802 I've done some prototyping with vehicle-commands library. Basically, same requests as with this module are executed against fleet-api endpoints. Option 1 would be to switch this module to use the new endpoints.
What does not work is sending commands- these must now be signed. This can be achieved by using the new API or by running a Tesla-provided proxy that converts REST API to signed commands.
That said I will experiment some with which changes would need to be made to connect to arbitrary endpoint urls for simple requests or commands. Especially the response definitions are not part of the vehicle-commands library and still super helpful.