search

hjdhjd / homebridge-myq

:car: myQ Liftmaster and Chamberlain Plugin for Homebridge https://github.com/nfarina/homebridge
Other
568 stars 43 forks source link

Unable to connect to myQ API (429) #1109

Closed nullren closed 10 months ago

nullren commented 10 months ago

Describe The Problem:

Unable to connect to myQ API from Homebridge.

I first suspected maybe something out of sync or outdated plugin, so I upgraded it. Also confirmed my credentials are valid and working in the myQ application.

This is causing HomeKit when trying to read the current state (or change it) to just hang and eventually timeout.

Logs:

[9/16/2023, 10:06:53 PM] [myQ] myQ API: Temporary myQ API server-side issues encountered: 429. Retrying the API call.
[9/16/2023, 10:06:53 PM] [myQ] myQ API: Switching to myQ cloud region: east.
[9/16/2023, 10:06:53 PM] [myQ] myQ API: Temporary myQ API server-side issues encountered: 429. Retrying the API call.
[9/16/2023, 10:06:53 PM] [myQ] myQ API: Switching to myQ cloud region: west.
[9/16/2023, 10:06:54 PM] [myQ] myQ API: Temporary myQ API server-side issues encountered: 429. Retrying the API call.
[9/16/2023, 10:06:54 PM] [myQ] myQ API: Switching to myQ cloud region: auto.
[9/16/2023, 10:06:54 PM] [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429.
[9/16/2023, 10:06:54 PM] [myQ] myQ API: Unable to access the OAuth authorization endpoint.

Environment:

hjdhjd commented 10 months ago

I've seen this before - shutdown the plugin for a period of time, perhaps an hour, and then retry - that may do the trick. I've seen this issue go on for a few hours to a day. It's API-related on the myQ end. a 429 means it's locking you out for making too many requests...that may be do to a bug on the myQ end, or it may be that the plugin has been retrying too many times in a short-ish time horizon. Give those things a go. I encountered this myself over the past few days. Cheers.

Damien514 commented 10 months ago

I had the same issue but it fixed by itself. I think that was on myQ side. Today, I have a new error code on my console:

[9/18/2023, 2:13:38 PM] [myQ] myQ API error: API call returned error: 522.
[9/18/2023, 2:15:39 PM] [myQ] myQ API error: API call returned error: 522.
[9/18/2023, 2:17:41 PM] [myQ] myQ API error: API call returned error: 522.
[9/18/2023, 2:19:57 PM] [myQ] myQ API error: API call returned error: 522.
[9/18/2023, 2:21:43 PM] [myQ] myQ API error: API call returned error: 522.
[9/18/2023, 2:23:44 PM] [myQ] myQ API error: API call returned error: 522.

Any clue?

hjdhjd commented 10 months ago

Yep...myQ server issues...those are Cloudflare connection timeout issues connecting back to the myQ backend.

github-actions[bot] commented 10 months ago

This issue is locked to prevent necroposting on closed issues. Please create a new issue for related support requests, bug reports, or feature suggestions.