-
Notifications
You must be signed in to change notification settings - Fork 743
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tesla API: Retry in 60497 seconds #3957
Comments
I am encountering the same issue starting at June 14, 12AM EDT, might related to tesla server side problem. I updated to the latest version of Teslamate, restarted the container, issue still persists.
|
Don't have great logs since I rebuilt my container, thinking it was my fault. My dashboards stop showing data at around 20:30 Pacific (https://time.is/1718336220), although my retry time suggests 21:00 Pacific exactly (if cooldown time is 20 hours). Hope this isn't the end of the OwnerAPI.
As an aside, I'm super conflicted since I just got 2024.14.9, should I wait to update until I can have my statistics reflected properly? 😶 |
Looks like not only on 2024.14.9, |
Same issues as @jheredianet appears to have flat lined around 11:20pm Eastern on both my 2021 MY and 2022 M3. Hopefully there’s a way to fix this soon! |
Same here stop working around 03:23 UTC Log GMT+1
|
I’m seeing the same issue, however the Tesla add-on in Home Assistant which I still have setup via the old owners API is able to poll and control the car. |
FleetAPI is wave updata. All vehicle can command via Fleet and some old vehicle also command via OwnerAPI. But those will updata to FleetAPI only final. |
Same here, as of today 14 Jun: 2024-06-14 11:06:18.449 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/9290931261318626/vehicle_data -> 429 (69.356 ms) |
Mine was down earlier but it seems to have reconnected now. Healthcheck failed but can still see the data updated |
Yep, mine seems to have recovered now too |
indeed, recovered now on my side too. |
back online
|
Tesla changed the 429 to display the instruction in the body for developers who didn't see the header. @jheredianet @prato1976 408 response codes (Device Not Available) are not counted against the WAF quota. Only calls returning a 200 are taken into account in the quota which then causes the 429 (too many requests). @mrgaolei @prato1976 did it work (with response code 200 on the vehicle_data call) after the indicated time? or sooner ? I see that @b89dan should have waited a long time according to the message received... |
Same problem here since this night. |
I am also seeing this since yesterday. There goes my solar overflow charging automation :-( Can we collaborate on a solution which still allows getting vehicle charge / battery charge often enough so that solar overflow charging still is feasible, i.e. once every minute at least? I'm willing to help & discuss. |
Same here, has anyone found a solution yet? |
Same here, starting 2024-06-15 13:04 EET. Legacy Model S, '16 S75 with MCU1 |
This is what it's happening now: Tesla implemented API rate limiting, now adapter gets blocked with HTTP/429 |
Same problem here...but Home Assistant complement still working with the same Owner API |
Getting the same retrying error in Teslamate version 1.29.1. Home Assistant also does not work. 429 error (Too Many Requests) by the looks of it:
|
Same issue for the past ~5 hours.
Running TeslaMate with Docker on Linux with only Docker and TeslaMate running. |
Same problem here. Since 01:15 UTC on June 15, only 429 answer are logged without interruption. Although the time counter jumps quite quickly to 30s, and then decreases. Once reaching 1s it always jumps back to several hours.
I have no other services or apps using the owner API. |
I ran into the same issue, and found there seems to be a relation to me also running Home Assistant with Tesla integration 3.23.0. There seems to be an issue in 3.23.0 where the integration, despite chosing the option "use MQTT to retrieve data from Teslamate" periodically polls the car directly via the Tesla API. It's too early for conclusions, but it's possible that the HA integration triggered some rate limit on the Tesla server side. There is a new version 3.23.1 which I just installed. For Teslamate, I will have to wait until the rate limit is lifted in 30039 seconds. |
hi @jlestel, I was driving till 19:39
Refres token
my car start charging midnight
then at 04:23 no more info/data available on teslamate and starting to get the 429
and i continue getting 429 till 12:24:57 and starting having 408 at 12:25:28
since 2024-06-14 12:25:28 i don't see any 429 till now and working normal regarding the 200 i got |
#3958 it happened to me, too Just an idea: the real weakness is that teslamate doesn't give any feedback about those errors in the Web page. |
Same error here. We need to limit the Api request or go to fleetapi asap |
Reading from Tessie api status seems that Tesla have turned off the deprecated Owner API https://status.tessie.com/incident/384149 |
Same here
|
This morning my Teslamate started working again randomly. I did not generate a new token. |
I had the same issues starting yesterday. No connection to the two connected cars without showing any errors in the teslamte ui. just realized the missing connection because even after charging the cars for a few hours the soc got stuck at low percentages. updated my teslamate-docker-stack-thingy yesterday -> no change stopped all services today morning for around one hour and now teslamte gets updated from both cars again while charging. didnt change anything in the settings and never renewed any keys, tokens, whatsoever. lets see how long it is working again... |
Mine works again. I shut it down for ~10 hours since the "Retry after X seconds" was around 9 hours. Now it's working once again, so either the API just works once again or it helpt to keep it down for the retry time. |
Here too. Today everything works again - so far. This incident might also have been a warning shot by Tesla - so we should take this seriously and upgrade the api. |
Several points:
|
@brianmay one thing to note is that retry-after value can lie. A couple of us who originally posted this issue were given retry times of 20h, but with the original constant polling behavior, I was able to get a successful response after less than 8h (as visible from my logs), and a couple others posted similar behavior.
|
Yuck. Does that mean we should be putting a cap on the upper retry time? Or is this just a transit issue while they implement the feature correctly? |
@brianmay it's yuck but it's a lesser evil since the new streaming only sends events every minute @4U6U57 i made the same observation. It would be interesting to know at what time you were able to access again. I have the impression that this is a daily limit. maybe the counters are finally reset daily at a certain time... |
Mine started working at 03:00 AM EET, when the car started charging. I don't know if updating to the latest build helped, but I don't see any rate-limiting errors in the log any more. I haven't driven today, but at least the charge got recorded. docker-compose.yml from
to
i.e. from latest release to the latest build. |
Mine is on "Latest" and simply worked as soon as the ban from Tesla was expired. |
Would it be an option to make the polling interval(s) configurable? This way, users can decide between higher responsiveness with a higher risk of running into the API limits, or slower updates but lower risk. |
This is what I prepared in this PR. |
Between this quoted comment and release 1.29.2, is this resolved? |
It did not happen again for me. In my case, it was enough to install a new version of the Tesla integration for Home Assistant, no updates to TM were necessary. |
Is there an existing issue for this?
What happened?
Can't fetch car data.
I found that Teslamate upgrade API endpoint from OwnerAPI to FleetAPI, but what ClientID is?
How can I set my ClientID?
I think there's no common ClientID
Sorry!, updated:
I was wrong, is OwnerAPI, not FleetAPI.
but why prompt me "Retry in 60466 seconds"?
I test another TeslaID on my same Server goes OK.
Is this TeslaID blocked?
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output
Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
v20.10.12
The text was updated successfully, but these errors were encountered: