TeslaUSB Refresh_Token error - Endpoint is only available on fleetapi" about teslausb

[marcone]

As I understand it, Tesla has a new API to interact with the car and the old API has been turned off.
My layman's understanding of the new API is that it requires signing up with Tesla as a developer and obtaining a secret key to be used when communicating with the API server. That is not going to work for TeslaUSB I think.

[KrzysztofHajdamowicz]

Teslamate had same issue. Fortunately, legacy API still works, but you have change /vehicle to /products.

Migrating to new API is the best option long-term.

[miles267]

Am able to create new Tesla Refresh Tokens without issue. Also update config file and delete the json file from /mutable folder to clear any old, cached tokens.

[miles267]

Are there any other automated methods to keep the car awake long enough to complete the sync before allowing it to sleep? Only the Teslafi API?

[Arthur-Philip-Dent]

1. Try to switch sentry mode on -> keeps the MCU/middle console powered, but causes “Vampire Drain”.
2. Powerbank/UPS for the SBC. You have to search a bit to find the appropriate one, also being able charging while powering the SBC. Also some UPS cause to reboot the SBC when power line comes back on.

[miles267]

Thanks @KrzysztofHajdamowicz. I’ve since opted to move to TeslaFi’s API which I’m now testing. It seems to be working and not reporting errors in Teslausb archive log. I’ll set thid up for our other car tonight which has a significant backlog of videos that need to sync. That will be true test if it stays awake. Before paying for 2 TeslaFi subscriptions.

[marcone]

Teslamate had same issue. Fortunately, legacy API still works, but you have change /vehicle to /products.

I could only get the basic "list_vehicles" to work using the /products URL, but actually getting vehicle state or controlling the vehicle doesn't seem to work.

[marcone]

Teslamate had same issue. Fortunately, legacy API still works, but you have change /vehicle to /products.

I could only get the basic "list_vehicles" to work using the /products URL, but actually getting vehicle state or controlling the vehicle doesn't seem to work.

OK that's not entirely true.The "list" API works on the /products URL and can be used to get the vehicle ID. That ID can then be used with the /vehicles URL to get vehicle info. A lot of the other legacy API commands no longer work this way though.