@sdbg @Tamerfakhry and others who are having issues - are you running on Docker or executables? I ask because the latest Docker image actually has one extra commit that the executables don’t have that automatically tries to failover to multiple MyQ endpoints.
My setup has had no issues today, but I can see earlier in the logs where it switched over to MyQ-West at some point, so I wonder if the default (east) is currently having troubles.
I’m running the latest windows executable. Maybe that’s it and their (east?) endpoint is offline…
Any chance you can incorporate that extra commit into the windows version? Seems like a great idea to have .
Ok yeah I bet that’s it. Let me see if I can get those published today.
1 Like
thanks in advance.
I am running mine with docker and had to restart my machine (Mac) and once it came back back it is constantly giving error 429.
Looking through the Home Assistant issue report in Github, it sounds like HA, HomeBridge and NodeRed are now starting to get the same errors.
1 Like
Windows executable.
1 Like
I am running docker and started getting this 429 error around 10:35am Eastern today. Hasn’t connected since.
Any updates?
Not great news…I built new executables, but login fails for me when I run the Windows one. It looks like any new session just fails with a 429 error right now. Region failover makes no difference. For anyone who still has a setup working, I would suggest you not restart it.
Other integrations (home-assistant included) are dealing with this, too. I’m afraid there is not much we can do but wait it out. The library author’s policy at this point is to not do anything with these random outages unless they prove to last longer than a couple days. If he does decide something needs to change, I’ll update things on our side as needed.
5 Likes
This has been happening to me since I tried to set it up. I got it to work once for a few hours, but I have gotten the same error perpetually since then. I even set the refresh to a minute and no luck.
Oh @brbeaird when will I heed your warnings LOL ?
My system had never missed a beat, until…
I was performing a Windows 10 Update this morning and rebooted.
Now I’m getting the same sad message as many others 
Looks like the super nerds over at Home Assistant figured out a fix. Not sure if @brbeaird can do the same or not
1 Like
Yes, I have been following that, and it is good news. I have made a couple attempts to translate that into the library we are using but have been unsuccessful so far. If I can’t beat him to it, I’m sure the myq Node library author will get this update in fairly soon, which should get us back up and running.
4 Likes
until MyQ breaks it again 
2 Likes
I confirmed those updates work locally. Also, hjd confirmed he’s working on an update to the myq library, so as soon as that’s out, I can update my fork and push out a new version with Docker image and executables.
5 Likes
Awesome.
Thanks for all your efforts.
Library has been updated. I should get something out later tonight.
5 Likes
I have the update ready but as soon as I stopped my working setup and tested the new one, it also quit working. It’s possible I just need to wait it out - will revisit tomorrow.
1 Like
Good Morning & Good News 
Thanks for your efforts as always on this!!!
As of 6:00am 10/13/2023:
- started the old v1.04 and it did not work.
- started new v1.05 and received the 429 - Too Many Requests message
- left it running, but Power-Cycled my v3 SmartThings Hub
- Bam! Up & Running!!!
Never forget the power of a therapeutic power-cycle (not just a reboot/or/restart)
Note to v2 Hub Users: Don’t forget to pull the batteries out of the bottom!
Edit: I’m running the Win64 Executable on Win10.
1 Like