MyQ will not initialize

[scangasn]

The problem

Until about a month ago, I had no issues with MyQ. Now, it will not initialize. It just says "Failed Setup, will retry" but it doesn't appear to retry. When I manually reload, it fails immediately. I am already updated to the latest core which I believe was intended to fix this issue. I still have full control via the MyQ app.

What version of Home Assistant Core has the issue?

2023.10.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

MyQ

Link to integration documentation on our website

https://www.home-assistant.io/integrations/myq/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

If I hover over the words "Failed Setup, will retry", I am one of the below messages (it seems to alternate between the two):

1. "Error requesting data from https://partner-identity.myq-cloud.com/connect/token: 401 - Unauthorized"
2. Got 429 error - stopping request until 2023-10-10 18:59:45.893607. there were 1 request"

[home-assistant]

Hey there @ehendrix23, @Lash-L, mind taking a look at this issue as it has been labeled with an integration (myq) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of myq can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign myq Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

myq documentation
myq source
_{^{(message by IssueLinks)}}

[rlyons20]

I wish I could say mine had been stable up to now, but I've been hit by every service interruption lately!

My gateway/devices became unavailable 2 hours ago.

[neydah700]

Stopped working again for me today. Tried deleting and reconfiguring the integration and I get this in my logs.

2023-10-10 11:02:05.431 DEBUG (MainThread) [pymyq.api] Performing initial authentication into MyQ
2023-10-10 11:02:05.431 DEBUG (MainThread) [pymyq.api] Scheduling token refresh, last refresh was None
2023-10-10 11:02:05.431 DEBUG (MainThread) [pymyq.api] Initiating OAuth authentication
2023-10-10 11:02:05.431 DEBUG (MainThread) [pymyq.api] Retrieving authentication page
2023-10-10 11:02:05.431 DEBUG (MainThread) [pymyq.request] Sending myq api request https://partner-identity.myq-cloud.com/connect/authorize and headers {'redirect': 'follow'} with connection pooling
2023-10-10 11:02:05.608 DEBUG (MainThread) [pymyq.request] Attempt 1 request failed with exception : 429 - Too Many Requests

[scangasn]

I wish I could say mine had been stable up to now, but I've been hit by every service interruption lately!

My gateway/devices became unavailable 2 hours ago.

That is roughly when mine went out as well. To be precise, 11:44 EST.

[marylarry]

Same issue here. Happened about two hours ago @Lash-L

[BradenJ6164]

Same issue here, can’t login to my account anymore. Started 2 hours ago and told me I was locked for 1 hour, it’s been 2 now.

[dakoellis]

Mine went out 8:39 AM Pacific

[thechriswick]

Info from another thread, it was stated that Chamberlin has not capped their API calls to 60 per hour (once a minute) and the current build requests every 5 seconds. This would seem correct as users are being "locked out" likely due to excessive calls. Changing the build to once every minute really hinders the reporting capabilities as a garage door could open and close within a minute and not be known.

[kilrgt]

Yup..same here , feels like MyQ is changing things on their side again.

[Lash-L]

Closing this issue in favor of #101763 as it was older - please move all relevant discussion there to limit the amount of notifications I receive - potentially hiding any important information. As a reminder if you have the same problem as someone, you should thumbs up their issue - do not make a comment stating that you are having the same problem unless you have more information to share.

[Lash-L]

@home-assistant close