Following @johnonline 's lead here…
I left my Win64 Bridge down since my last post (13 hours ago), loaded it this morning, and it logged in successfully.
So I guess sometime between 9 and 13 hours now 
Hey @brbeaird … any thoughts on that initial “blast” of log in attempts? That would certainly appear to a Server to be a bot of some sort. Any way to prevent that from happening?
@BartschLabs … did you get the “blast” of 429 errors that I saw? (this post)
Hit with 429s this morning. I stopped at 9a so we’ll see how long it takes. I was thinking of attempting at 10 hour mark as a test. I can go longer or shorter to help any testing needed.
Mine went down overnight too. I have some ideas on possibly separating out the initial token part. Will just have to play around with it as always.
Awesome! Is that the thing causing the “rapid blast” of multiple log-ins?
I have been rock solid for a few weeks now… hopefully it stays that way. Thanks for looking into it B.
I have not observed the rapid wave of errors and my time looking over the code would usually make me say it shouldn’t be possible. I’ll have to add more logging.
Mine went down at 1041pm last night. I tried stopping the docker container and restarting it but am getting an unable to login to myq with credentials error. I tried removing my credentials in the app and backing out, clearing cache and then re-entering. Same error
2023-10-23T16:03:44.504317149+00:00 INFO MyQ Connector Unable to login to MyQ with credentials. Will try again after a delay. Updating credentials will trigger an instant retry.
2023-10-23T16:03:44.509787483+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-10-23T16:03:54.511279154+00:00 INFO MyQ Connector Unable to login to MyQ with credentials. Will try again after a delay. Updating credentials will trigger an instant retry.
2023-10-23T16:03:54.520525821+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-10-23T16:04:04.772883159+00:00 ERROR MyQ Connector Non-200 response calling: http://192.168.1.xxx:8090/devices - 401 - body: Unauthorized
2023-10-23T16:04:04.777678159+00:00 INFO MyQ Connector Failure count 668
2023-10-23T16:04:04.778513492+00:00 INFO MyQ Connector 401
2023-10-23T16:04:04.818695159+00:00 ERROR MyQ Connector Refresh Failed.
2023-10-23T16:04:04.822381159+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-10-23T16:04:14.531617497+00:00 INFO MyQ Connector Unable to login to MyQ with credentials. Will try again after a delay. Updating credentials will trigger an instant retry.
2023-10-23T16:04:14.536909830+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-10-23T16:04:24.540223835+00:00 INFO MyQ Connector Unable to login to MyQ with credentials. Will try again after a delay. Updating credentials will trigger an instant retry.
2023-10-23T16:04:24.544669835+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-10-23T16:04:34.545493506+00:00 INFO MyQ Connector Unable to login to MyQ with credentials. Will try again after a delay. Updating credentials will trigger an instant retry.
2023-10-23T16:04:34.550776173+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-10-23T16:04:44.558479511+00:00 INFO MyQ Connector Unable to login to MyQ with credentials. Will try again after a delay. Updating credentials will trigger an instant retry.
2023-10-23T16:04:44.562737178+00:00 DEBUG MyQ Connector MyQ-Controller device thread event handled
2023-10-23T16:04:54.554122516+00:00 INFO MyQ Connector Unable to login to MyQ with credentials. Will try again after a delay. Updating credentials will trigger an instant retry.
As I think many of us are now seeing, this is no longer true. Personally, I worry that if MyQ is intent on blocking all those hits to their servers, that’s exactly what’s going to happen. At best,they’ll change strategies as we do and turn this into an interminable game of whack-a-mole.
But maybe I’m too pessimistic. Obviously, there are some really smart people out there and maybe a longer term solution will be found. But given all the time that you and others have invested in this over the years, I’m starting to wonder if instead of constantly reverse engineering all this, it isn’t time to find some way to work with MyQ. Not that I’ve seen any evidence that they’re interested. 
For now, I’m going to “wait and see,” although not without looking at the other options. You know, I’d even put my tilt sensors back up if that were still an option. Not anywhere near so many server hits with that method…
Grateful as always for all the work you put in this.
No, just the typical 2 Login Failed and then the API Error, on repeat.
Reconnected without issue. Waited about 18 hours between attempts.
As of now, the bot protection is still only on the first auth call. You can see this visually on the official app by logging out an in - it takes you to a web page where you put in your info. That form is now bot protected that our library has always attempted to handle behind the scenes.
Once you get a token successfully from that piece, you are normally fine for some amount of time because the token refresh process is a lot more straight forward.
Still, your point has some validity because something is seeming to cause setups to sometimes fail back to the original login process without restart and explanation, so I am not totally sure what is happening there.
I have an idea of how to modify the approach to let users enter in their login info through a browser like MyQ wants, but it will take me a bit to prove it out and test it. Will post updates here as I go.
What exactly does this mean? Do I just need to stop the docker container or is there more to it?
Yes… Scroll back a few posts and you’ll see some guys are able to log in after an hour, some after 9 hours, myself was 13 hours.
A good post by the maintainer of the home assistant integration.
I was flipping back and forth between this and HA installs until the problems hit both (this is literally all that’s left on my ST install). I have since gone on the probably huge waiting list for a device that allows local control in home assistant.
Disappointing but sounds like the bot detection they’ve implemented is a pretty impressive tool, though a smaller user base is an advantage.
Attempted to restart container after 12ish hours off and same flurry of 429 errors. Will try again after 13 hours.
Yup, that says it all.
I actually feared the same thing. If Chamberlain/MyQ is looking at intentionally putting up more obstacles to prevent 3rd party developers from making their product better, then it may be a continuous battle.
What have we seen in last 8 months? Like 4 different instances where it went down and needed some more tweaking from Brian? And I do greatly appreciate all of Brian’s work and the community at large that have helped me.
That’s being said, i just installed the Meross MSG200hk smart garage door opener. Basically a WiFi relay switch that integrates any garage door opener with ST, Google, Alexa, and HomeKit. Works like a charm. I still have this MyQ Edge container running as a back up and still has been up for last 2 weeks now.
As much as I appreciate Brian’s efforts this has become a pain with the constant need for updates to keep up. I can no longer rely on the ST integration.
myQ (along with the original Echo) were my first modern smart home devices. I purchased them in December 2014. I think I’m going to switch over to the Meross solution.
