HTTP 429 Too Many Requests with multiple HA restarts

[pkolbus]

Occasionally I get into a situation that requires multiple HA restarts (updating integrations, developing/testing yaml configuration, or other maintenance). When this happens, the Parcel integration gets into a failure loop with a dreaded 429 Too Many Requests error, the only fix seems to be to disable the integration for a while.

It would be awesome if the integration could remember its data across HA restarts, and/or gracefully handle the 429 during setup and adjust the retry interval. (I haven’t looked at whether the web service serves x-retry-after or similar).

[jmdevita]

Hey @pkolbus, I can add this in. I should also implement a back-off system as well so it doesn't accidentally use all 20 api calls / hr trying to connect. Should get that done in the next few days.

I did make the PR for #82, I just haven't done all the testing yet but this should work.

[PlayerSite3]

Hi there, I See in my logs the same issue but it is Not triggered during a restart or something else. I also set the API call Limit from 5 to 10 min. So in my case they would call 6 times in a hour (Limit 20 times a hour).

Dieser Fehler stammt von einer benutzerdefinierten Integration

Logger: custom_components.parcelapp.coordinator
Quelle: custom_components/parcelapp/coordinator.py:139
Integration: Parcel App (Dokumentation, Probleme)
Erstmals aufgetreten: 04:55:06 (2 Vorkommnisse)
Zuletzt protokolliert: 08:20:09

Parcel API rate limit hit (429). Backing off for 300 seconds

[jmdevita]

Thanks for the log @PlayerSite3. 6 calls/hr against a 20/hr limit shouldn't trip on its own, so my guess is Parcel enforces a tighter rolling or burst window under the hood that the docs don't spell out.

I put up #86 with exponential backoff on consecutive 429s, each successive 429 doubles the wait (capped at 1h), and the counter resets the moment a call succeeds. That should keep the integration from poking the API at the same cadence while you're still inside whatever window tripped it.

Will let you know when it's released. If you still see 429s after upgrading, let me know, at that point we'd want to check whether anything else is using the same API key.

[pkolbus]

I find the "2 occurrences" and the timestamps (3h25m apart) telling. It would seem that the simple backoff is working to prevent getting stuck in a 429 loop-- the next attempt after 04:55:06 was successful.

It's probably worth going to the next stage- check when the integration actually makes each API call, and look for other uses (maybe even open browser windows to web.parcelapp.net). Perhaps revoke the API key (on web.parcelapp.net) and create a new one, if there might be a forgotten use.