It did not work for me and decided to remove the MyQ integration and re-install it, but every time I try it tells me:
It was not disabled before the update. I deleted MyQ and waited 33 min before trying to log in and no joy.
It is deleated and I have rebooted and MyQ shows up as an ignored integration, I will let the system sit for a couple hours before I try to login through the integration.
Working here after HA update to 2023.10.2 took 19 minutes after the update to get the connection back with myQ cloud.
Added MyQ after 7hrs and the same problem of “failed to connect”
Do you have a pymyq folder in your config folder? If so, remove it and restart HA.
1 Like
Removing pymyq folder worked for me. Thank you
Removed pymyq folder and restart HA worked for me.
Same here!
Thanks; I renamed the pymyq folder, restarted, and waited about an hour, and everything appears to be working for me also. Hope so for everyone else!
I don’t see a pymyq folder in my config folder but it’s still failing to connect. Located at ~/config ?
It is broken again.
Looks like a new error in the logs has popped up. “ * Error fetching myq devices data: Got 429 error - stopping request until 2023-10-18 18:29:55.663589. there were 6148 request”
I finally got fed up with all the issues with the myq integration not working with HA, and removed it from HA altogether. I replaced it by using couple of ZooZ ZEN17 Relays - https://www.amazon.com/dp/B096LLL1C6 and a couple of Ecolink Tilt Sensors https://www.amazon.com/dp/B00HGVJRX2 . These are Z-Wave based and I was already using Z-Wave with HA. They all work perfectly with my two garage doors that are Liftmaster/Chamberlain (Red Learn Button from 2005) using older Security+ protocol (not the Security+ 2.0). I no longer have any dependence on the cloud for the garage doors.
1 Like
Mine disconnected itself 10 hours ago. On the latest 10.3 build.
Going to get a Aqara door sensor and just use that as a open close notification sensor. Since the myq app takes an eternity to send a notification when the door is opened and closed.
Are your openers MyQ? The Zooz website explicitly says the Zen17 does not work with MyQ
They are not MyQ based natively. I have the MyQ Hub for each of them but that just adds aftermarket MyQ support for the openers to use with their mobile app, etc… which works fine, but I wanted to be able to control the openers via HA and drive through scripts, automations, etc… I noticed that there is an adapter for 2.0 that can be used Security+ 2.0 Wired Dry Contact Adapter – Garadget - but I have no need for it, so not used it.
Not sure if this is relavent. I logged out of the MyQ app on Android, now I can not log back in. This may all be a massive Chamberlin issue.
FWIW, It looks like Chamberlain is trying to monetize their API. I just logged in and they are trying to get me to sign up for their “premium” service @ $45/year, which seems to be aimed at Tesla owners, which I am not. I would not be at all surprised if they come at the HA community with the same sort of offering.
I personally am not 100% opposed to this as I totally understand that it costs money to keep an API running (esp if they are using CF now). I am a Nabu Casa member simply because I feel that they are doing fantastic work and want to see it continue. That said, I did purchase the Chamberlain hardware specifically for this functionality and maybe $45/year is a little steep for something they used to offer for free. Chamberlain, if you are paying attention to these threads (as I suspect you are), it would probably be a little easier to swallow if it was a monthly charge of somewhere around $1-3 USD, IMHO.
Has anyone tried the user agent name from the app (IOS_CGI_MYQ)? I’m away from home or I’d try it myself.