500 Internal Server Error and 429 Too Many Requests after changing to tesla Developer fleet API

[Stevansell]

I updated my EVCC to use myteslamate and tesla developer fleet api, as per the config instructions.
My assumption was that this change was made to bypass the limited API issue introduced last year.

Changed my interval time back to 30s down from the 150s i had it beforehand and got hit with these errors

[lp-1 ] ERROR 2025/02/04 00:00:14 max charge current 32A: 500 Internal Server Error: Server error: POST https://client-tecdfep9law-teslamate-cmd:4443/api/1/vehicles/LRWYHCFS8NC579070/command/set_charging_amps resulted in a 500 Internal Server Error response:
{"response":null,"error":"vehicle unavailable: vehicle is offline or asleep","error_description":""}
[lp-1 ] ERROR 2025/02/04 00:00:39 max charge current 32A: 429 Too Many Requests
[lp-1 ] ERROR 2025/02/04 00:01:12 max charge current 32A: 500 Internal Server Error: Server error: POST https://client-tecdfep9law-teslamate-cmd:4443/api/1/vehicles/LRWYHCFS8NC579070/command/set_charging_amps resulted in a 500 Internal Server Error response:
{"response":null,"error":"vehicle unavailable: vehicle is offline or asleep","error_description":""}
[lp-1 ] ERROR 2025/02/04 00:01:39 max charge current 32A: 429 Too Many Requests
[lp-1 ] ERROR 2025/02/04 00:02:12 max charge current 32A: 500 Internal Server Error: Server error: POST https://client-tecdfep9law-teslamate-cmd:4443/api/1/vehicles/LRWYHCFS8NC579070/command/set_charging_amps resulted in a 500 Internal Server Error response:
{"response":null,"error":"vehicle unavailable: vehicle is offline or asleep","error_description":""}
[lp-1 ] ERROR 2025/02/04 00:02:19 max charge current 32A: 500 Internal Server Error: Server error: POST https://client-tecdfep9law-teslamate-cmd:4443/api/1/vehicles/LRWYHCFS8NC579070/command/set_charging_amps resulted in a 500 Internal Server Error response:
{"response":null,"error":"vehicle unavailable: vehicle is offline or asleep","error_description":""}

Is this an issue on my end, or was this update just for a new way of getting the tokens, and not a fix for the limited API issue?

[mucki12]

See #18400

Solution: use nightly or wait for the next final