My myq controller went offline last weekend. Running on Raspberry Pi using docker. I hadn’t updated to the latest image. I tried stopping the container, pulling the new image, and re-running the container but was getting an error. I deleted the container and image, pulled the lastest image and created docker container and it has been running without issue since. I did not have to to anything with the controller or door. This is the second time I’ve had to completely delete the docker container and image. As a novice using docker, is there a way to pull the latest image and update without having to uninstall and start from scratch?
Here are the docker commands I used. Running container
sudo docker run -d --restart=‘always’ --name=‘smartthings-myq-edge’ --network=host ‘brbeaird/smartthings-myq-edge:latest’
To stop and restart
sudo docker stop container [ID]
docker pull brbeaird/smartthings-myq-edge
sudo docker start container [ID]
I’m currently on Hubitat where new MyQ app users cannot log in, and came here hoping to find an anwer
So now I’m just letting foks here know that MyQ/Chamberlain seems obsessed with removing all non sanctioned aka non paying apps from their system. The developer of a recent login fix on Home Assistand told me that MyQ just broke his most recent solution.
Many folks on Hubitat are moving to local solutions dumping the MyQ cloud.
Mine went back online at 7 PM EST on 10/19 as well. Weird outage there, but I’m glad it works again!
@brbeaird do you see any issues with using local utp port 49160 (auto selected) instead of 1900? The app is set to auto detect the port and seems to work fine. Running Docked on a Synology NAS. Thx!
Well, I knew I shouldn’t have said anything yesterday, because this morning I’ve got the dreaded “Unauthorized” error. I’ve gone through all the usual gymnastics this morning to try to restore the connection … but nothing.
We have learned that MyQ has implemented CloudFlare bot protection on their login endpoint. It seems to be super aggressive in detecting setups like ours. It also appears to only be an issue on the initial login, so if you get a successful login, you are probably fine until you need to restart. If you trigger bot detection, you likely get yourself locked out for an hour or more, so you’re best shutting things down and trying again later.
I know several people are experimenting with ways to get around it. We’ll just have to wait and see how things go.
It’s a good recommendation. Don’t blame anyone for going that direction.
Seems if you are behind a VPN you can change to a different server IP and get instantly un-blocked… then switch back again and it appears to still work. But if you re-start the bridge server for any reason while connected to that blocked IP, you will get 429 - or at least that is my experience.
Since we are already well into the rabbit hole of workarounds, @brbeaird I wonder if an idea might be (assuming possible) for the bridge server to automatically halt itself after a set number of 429 errors for a period of time and then try again? Currently when a 429 error occurs I think the user has to manually stop the bridge server or it will continue to throttle the API and maintain the ban.
I noticed that my Win64 v1.06 went offline this morning around 2:15am
Terminated the program; Power-Cycled the v3 SmartThings, but still kept getting the 429 error.
Terminated the program, then waited one hour. Upon starting, saw a blast of 429 errors all at once within seconds of each other (see first screenshot below).
I’ve never seen that before!
Typically there is an error, then a wait time, then another 429; wait; etc. (see second screenshot below).
QUESTION: Could there be something in the login code (behind the scenes) that is rapid-firing Login Attempts, but that are not being seen/displayed in the myQBridge?
That might explain why the MyQ Servers are rejecting logins, perceiving them as spam attempts coming so quickly & frequently ???
Had to reboot my Windows PC for an Office update yesterday. When i tried to restart my MyQ server i got stuck in the 429 error loop. Shut everything down for in excess of 12 hours, then again today i tried to restart everything… got the same rapid fire 429 error same as you. I will give it a shot later.
I shut down MyQ Server for 90+ minutes and still had the 429 errors on restart. I shut it down again and forgot about it for 17 hours. Restarted and worked perfectly. So it looks like something between 9 (see above post) and 17 hours. My guess is cloudflare has a greater than 12 hour rate limiting duration (Rate limiting rules · Cloudflare Web Application Firewall (WAF) docs)
