Looking forward to it!
Working again with 10.2. Thanks!
Not working here after 10.2 update.
Also not working for me after 10.2 update.
UPDATE: Just started working on it’s own.
1 Like
Tried disabling and re-enabling Integration. No go.
Tried deleting and re-adding the Integration. Won’t let me log in to MyQ to complete the adding process.
If you applied the old “fix” from a few weeks ago, you may want to delete or rename the folder \config\pymyq that it created.
After the upgrade to 10.2 today, it seems to be working (for now)
Thanks!!
Some combination of renaming the old “fix” folder and/or waiting about an hour seemed to do it. Thx.
1 Like
Worked for me by reinstalling the MyQ integration.
Greg
P.S.
Thank you for all your hard work!
So, I am sure that someone has discovered this… But I think that MyQ is actually throttling requests from IPs.
I couldn’t remember my password, so used my phone app, and tried logging in again, and I received a JSON error message (Can’t recall what it said, something about too many connection attempts) disconnected from Wifi and then, there was no problem getting to the login page.
sorry if this is duplicate info.
Myq integration failing again today. Seeing this in the logs repeatedly.
2023-10-18 11:24:45.321 DEBUG (MainThread) [pymyq.api] Performing initial authentication into MyQ
2023-10-18 11:24:45.321 DEBUG (MainThread) [pymyq.api] Scheduling token refresh, last refresh was None
2023-10-18 11:24:45.327 DEBUG (MainThread) [pymyq.api] Initiating OAuth authentication
2023-10-18 11:24:45.327 DEBUG (MainThread) [pymyq.api] Retrieving authentication page
2023-10-18 11:24:45.329 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-18 11:24:46.609 DEBUG (MainThread) [pymyq.request] Attempt 1 request failed with exception : 429 - Too Many Requests
2023-10-18 11:24:46.611 DEBUG (MainThread) [pymyq.request] Too many request have been made - putting a temporary pause on sending any requests for 45 minutes
2023-10-18 11:24:46.744 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘[email protected]’ for myq integration not ready yet: Got 429 error - stopping request until 2023-10-18 19:09:46.612365. there were 1 request; Retrying in background
@wxman60, I have the same problem today
2023-10-18 15:29:41.446 DEBUG (MainThread) [pymyq.api] Performing initial authentication into MyQ
2023-10-18 15:29:41.446 DEBUG (MainThread) [pymyq.api] Scheduling token refresh, last refresh was None
2023-10-18 15:29:41.446 DEBUG (MainThread) [pymyq.api] Initiating OAuth authentication
2023-10-18 15:29:41.446 DEBUG (MainThread) [pymyq.api] Retrieving authentication page
2023-10-18 15:29:41.446 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-18 15:29:41.546 DEBUG (MainThread) [pymyq.request] Attempt 1 request failed with exception : 429 - Too Many Requests
2023-10-18 15:29:41.546 DEBUG (MainThread) [pymyq.request] Too many request have been made - putting a temporary pause on sending any requests for 45 minutes
I’m still seeing issues with it in the following package versions…
Home Assistant 2023.10.3
Supervisor 2023.10.0
Operating System 11.0
As several have mentioned above, some throttling seems to be part of this too. May need to adjust how often data is being polled to overcome that.
This is what I see in my logbook from today…
18 October 2023
Garage Door became unavailable
08:48:11 - 8 hours ago
Garage Door was closed
08:31:41 - 9 hours ago
Garage Door was opened
08:30:41 - 9 hours ago
Garage Door was closed
08:16:41 - 9 hours ago
Garage Door is closing
08:16:11 - 9 hours ago
Garage Door was opened
08:15:41 - 9 hours ago
I’m seeing that same 429 error code that others are seeing (too many requests)…
2023-10-18 16:25:23.118 WARNING (MainThread) [homeassistant.config_entries] Config entry ‘[email protected]’ for myq integration not ready yet: Got 429 error - stopping request until 2023-10-19 00:10:23.117741. there were 1 request; Retrying in background
Thanks for this suggestion, I just ordered a homekit bridge for mine, seems better to just bypass the cloud at this point with the amount of problems that we’re having with the integration thanks to whatever they changed on the MyQ side of things.
Have you also noticed that there is no “was opening” anymore?
And btw, it stopped working again.
1 Like
I don’t understand why the original github issue was marked as closed when the PR they did clearly hasn’t fixed the problem.
Looks like someone thankfully opened a new issue for it…
I just noticed that there’s more info about the issue from the dev here: The Current State of MyQ - From the codeowner
Now MYQ is sending out surveys on use of their Paid MYQ - Tesla service. I told them small/tiny fees maybe make sense for Cloud API access to pay for servers, but if I pay, then I should be able to use the API securely with any method including Home Assistant. They clearly know what is going on and are trying to monetize it as much as possible. Fools, imagine every vendor trying to charge for cloud access including Tesla. The cost should be inherent in the purchase, basic expectation so low hit rate API cloud access to control things. I bet this gets coded into law at some point, that electronic products of a certain type are required to provide basic, secure API access for controlling.
1 Like