You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tesla-motors.0 2024-06-15 11:41:41.854 error "Retry in 51499 seconds\n"
tesla-motors.0 2024-06-15 11:41:41.854 error AxiosError: Request failed with status code 429
tesla-motors.0 2024-06-15 11:41:41.853 error https://owner-api.teslamotors.com/api/1/vehicles/CENSORED/vehicle_data
tesla-motors.0 2024-06-15 11:41:41.853 error General error
tesla-motors.0 2024-06-15 11:41:11.828 error "Retry in 51529 seconds\n"
tesla-motors.0 2024-06-15 11:41:11.827 error AxiosError: Request failed with status code 429
tesla-motors.0 2024-06-15 11:41:11.827 error https://owner-api.teslamotors.com/api/1/vehicles/CENSORED/vehicle_data
tesla-motors.0 2024-06-15 11:41:11.827 error General error
Versions:
Adapter version: 1.3.2
JS-Controller version: 5.0.19
Node version: v18.19.0
Operating system: Raspberry OS 64bit 11.9
Additional context
This may require a significant rewrite to be more conservative with requesting vehicle data. However, I am using tesla-motors information to control solar overflow charging of my vehicle, and this requires the charge state, current, battery etc. to be available in at least 30s to 1min intervals during charging. I also run TeslaMate to collect the rest of my vehicle stats.
Addressing this should be a collaborative effort and I'd be willing to help!
The text was updated successfully, but these errors were encountered:
I began to experiment it since yestedar after a long drive. This morning it was working until I started to charge up the car at home, after 3 hours, now Teslamate shows teh error 429.
Describe the bug
See $SUBJECT. See also just every other Tesla API integration, e.g. TeslaMate: teslamate-org/teslamate#3957
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Adapter should be able to poll the API the whole day. Instead, requests are rate limited according to https://developer.tesla.com/docs/fleet-api#membership-levels:
Screenshots & Logfiles
Versions:
Additional context
This may require a significant rewrite to be more conservative with requesting vehicle data. However, I am using tesla-motors information to control solar overflow charging of my vehicle, and this requires the charge state, current, battery etc. to be available in at least 30s to 1min intervals during charging. I also run TeslaMate to collect the rest of my vehicle stats.
Addressing this should be a collaborative effort and I'd be willing to help!
The text was updated successfully, but these errors were encountered: