This repository has been archived by the owner on Apr 28, 2024. It is now read-only.
Feature Request: Exponentially Backoff requests after receiving Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity. #1125
Labels
enhancement
New feature or request
not a bug
Not a bug...working as intended.
wontfix
This will not be worked on
Is your feature request related to a problem? Please describe:
Looks like myQ wants to throttle, which is reasonable. HOwever, we keep on making requests every 3 seconds for 90 minutes. That's 1800 dead requests, network traffic, and love that myQ won't give us back. ;)
Describe the solution you'd like:
Could we do an exponential backoff retry strategy for requests, e.g. after 3s, 10s, 30s, 90s, 150s, 300s up to that max?
Describe alternatives you've considered:
Ignore it and let traffic be. Disable plugin temporarily (although that deletes myQ devices from homebridge)
Additional context:
Related to #1121 and #1119
Examples of continuous network requests and errors, every 3 seconds.
[10/15/2023, 6:46:30 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
[10/15/2023, 6:46:33 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
[10/15/2023, 6:46:36 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
[10/15/2023, 6:46:39 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
[10/15/2023, 6:46:42 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
[10/15/2023, 6:46:45 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
[10/15/2023, 6:46:48 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
[10/15/2023, 6:46:51 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
[10/15/2023, 6:46:54 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
[10/15/2023, 6:46:57 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
[10/15/2023, 6:47:00 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
[10/15/2023, 6:47:03 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.
The text was updated successfully, but these errors were encountered: