MyQ Devices Offline

[MikeMcGlinch]

The problem

There does not seem to be any problem with the integration, but as of an hour ago, all my MyQ devices went offline. I have confirmed that it is not a physical disconnect of the device hub, nor is my network down.

What version of Home Assistant Core has the issue?

2023.10.3

What was the last working version of Home Assistant Core?

2023.10.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

MyQ

Link to integration documentation on our website

https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+myq%22

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

(MyName) MyQ Gateway
2 hours ago
Disconnected
History
Show more
Logbook
Show more
October 18, 2023
Was disconnected
12:42:16 PM - 2 hours ago

Additional information

Was working since upgrade last week. No problems with my devices - had access all the way through, my Automations with these devices were working (almost) perfectly. I think Chamberlain may have shut down access - I still have access to the devices via my cell phone app.

[wrmacj]

I have the sme issue and here is an exerpt from the debug log. I can use the MyQ app without any issues.

2023-10-18 15:29:11.418 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Mask' for myq integration not ready yet: Got 429 error - stopping request until 2023-10-18 20:14:11.418694. there were 1 request; Retrying in background 2023-10-18 15:29:25.806 DEBUG (MainThread) [pymyq.api] Performing initial authentication into MyQ 2023-10-18 15:29:25.806 DEBUG (MainThread) [pymyq.api] Scheduling token refresh, last refresh was None 2023-10-18 15:29:25.807 DEBUG (MainThread) [pymyq.api] Initiating OAuth authentication 2023-10-18 15:29:25.807 DEBUG (MainThread) [pymyq.api] Retrieving authentication page 2023-10-18 15:29:25.807 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:25.917 DEBUG (MainThread) [pymyq.request] Attempt 1 request failed with exception : 429 - Too Many Requests 2023-10-18 15:29:25.917 DEBUG (MainThread) [pymyq.request] Too many request have been made - putting a temporary pause on sending any requests for 45 minutes 2023-10-18 15:29:25.918 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Mask' for myq integration not ready yet: Got 429 error - stopping request until 2023-10-18 20:14:25.918381. there were 1 request; Retrying in background 2023-10-18 15:29:31.023 DEBUG (MainThread) [pymyq.api] Performing initial authentication into MyQ 2023-10-18 15:29:31.023 DEBUG (MainThread) [pymyq.api] Scheduling token refresh, last refresh was None 2023-10-18 15:29:31.023 DEBUG (MainThread) [pymyq.api] Initiating OAuth authentication 2023-10-18 15:29:31.023 DEBUG (MainThread) [pymyq.api] Retrieving authentication page 2023-10-18 15:29:31.023 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:31.148 DEBUG (MainThread) [pymyq.request] Attempt 1 request failed with exception : 429 - Too Many Requests 2023-10-18 15:29:31.149 DEBUG (MainThread) [pymyq.request] Too many request have been made - putting a temporary pause on sending any requests for 45 minutes 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

[wrmacj]

When I logon to the MyQ app on my cell phone after a reboot, it does this security check one time. It does not do it again if I reboot my phone. It will do the same security check if I logout of the MyQ app before I reboot the phone. If I change form cellular to Wifi, logout and reboot it goes through this security check and I get a different Ray ID. After it passes this check I can reboot the phone and it does not do the check again and I am presented with a different window that says "Welcome back!" when I select login. So it now knows that I have passed the security check(Not a Bot, Not HA?, but the actual MyQ App?) but I still have to login.

[okoyfman]

Does not work any more since this morning

[jermanoid]

FYI: go ahead and disable your myq homeassistant addon until this is resolved. You'll be timed out when another patch comes out and you're trying to log in. Mine got catastrophically locked out. I had to go reset my password, and the myQ password reset wigged out, and thought it sent me a bunch of password resets when it never sent one. So I just ditched that account and re-created a new one

[alexandrezia]

They seem to be using cloudflare, perhaps some kind of bot manager solution.

[TomBrandt]

All I know it's frustrating. Ratgdo Shield may be a solution that is local only. I just use the integration for alerts on my phone when the door has been open for more than x minutes.

[sanctas]

Looks like the integration is going to have to start using Selenium to bypass the bot detection.

[jermanoid]

I went ahead and ordered a couple ratgdo devices. I can't keep wasting my time with this. losing access to my garage doors constantly because chaimberland thinks people are going to pay for their lame cloud that provides basic features at a premium subscription. They are being petty and fighting a battle they will never win.

[alexandrezia]

yeah me too! Giving up on MyQ, losing access constantly of my garage doors sucks. In fact all cloud based integrations eventually will fail you ... I'll hook up original remotes into an ESP32 and make a DIY definitive local operated automation. If they are putting bot-manager on front of the API to make it accessible only to their horrible mobile apps that have ADs!!! (while in fact they should make the API accessible to third-party integrations instead), it will not worth the time wasted to constantly put it back online.

[wrmacj]

I went ahead and ordered a couple ratgdo devices. I can't keep wasting my time with this. losing access to my garage doors constantly because chaimberland thinks people are going to pay for their lame cloud that provides basic features at a premium subscription. They are being petty and fighting a battle they will never win.

Agree with everything except "fighting a battle they will never win" I think you just demonstrated they won? They have prevented us from using the API with HA.

Ratgdo, gets us our cake and we can eat it too. Problem is it is still pricey, a bunch of work to put together and setup. $60 + box $15 or $75 cdn plus install and configuration. Plus you have to come up with another power source for each of these new units. Far from a simple solution but better than any other, I think.

Don't get me wrong, I think the Ratgdo is awsome for a bunch of reasons!! I just don't see spending $100 to enable my two garage doors, when it was free before, "winning"? I would call winning, sticking it to Chamberline by having LocalMyQ created similar to LocalTuya. That is the wish list. :)

[home-assistant[bot]]

Hey there @ehendrix23, @lash-l, mind taking a look at this issue as it has been labeled with an integration (myq) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `myq` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign myq` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

myq documentation myq source _{^{(message by IssueLinks)}}

[JBDenton]

I had a Merlin door motor for a few months and bought the hub, sensor beams a month ago. I had the integration working for 1 day before this shenanigans started. My wife and I spent so much time drilling holes, running cables, etc. Now spending so much time on this integration. I spent a ton of money to get this working very recently, I don't know what path to take. I don't want to get a subscription or buy a homebrew device which will still need a bunch of work to install it. Just extremely lost on what to do next. Wondering if there's a way we can flash their hub to do what we want Tuya/Tasmota stuff.

[jermanoid]

@JBDenton Does your setup utilize MyQ?

[VincentClement1]

Chamberlain are really screwing this up. I won't be recommending their devices to anyone. This is just dumb. If I have to I go the ratdgo route.

[JBDenton]

@JBDenton Does your setup utilize MyQ?

Yeah, I use the MyQ app, hub and sensors for my door. I'm guessing a bunch of sub brands are being hit by this too. Whether they are aware of this or had much control is another question.

[TomBrandt]

Looks like I have started something I didn't intend. I am sure the code owners will fix this issue also. The API does change from time to time but it gets updated with a week or so in my experience. If only they would allow third party access by opting in like Ecobee does. FYI Ratdgo currently is backordered. His sales page states all backorders were to be caught up by October. But no new info.

[MikeMcGlinch]

Well, after I submitted this, my stuff magically appeared again within HA just in time for my Automations to work. but then, they were out again just in time for my Automations to turn everything off would work, so my lights were on all night. Watched what was going on all day, and now they have again reappeared! There is nothing in my logs other than "MyQ Hub Gateway was connected" at 3:30:47 PM. I fully expect that my stuff will be gone again when I wake up tomorrow. How can I rely on this ineptitude?

At what point, after having purchased my Garage Door Openers over 7 years ago, and the wall switches almost as long, do I "OWN" my products? Why do I need to be dependent on a cloud server to be able to open my doors remotely? I had purchased the 1st generation hub to be able to access remotely - again, at what point do I "own" it?

[MikeMcGlinch]

@JBDenton Does your setup utilize MyQ?

Yeah, I use the MyQ app, hub and sensors for my door. I'm guessing a bunch of sub brands are being hit by this too. Whether they are aware of this or had much control is another question.

Chamberlain, MyQ, LiftMaster, Merlin, Grifco, and Poweram McGuire DLM Systems LLC are all owned by Chamberlain Group. I read somewhere that they have 65% of this market (in US).

[JBDenton]

@JBDenton Does your setup utilize MyQ?

Yeah, I use the MyQ app, hub and sensors for my door. I'm guessing a bunch of sub brands are being hit by this too. Whether they are aware of this or had much control is another question.

Chamberlain, MyQ, LiftMaster, Merlin, Grifco, and Poweram McGuire DLM Systems LLC are all owned by Chamberlain Group. I read somewhere that they have 65% of this market (in US).

Merlin/MyQ is pretty common in Australia too, is all through our home hardware store Bunnings.

Can't believe I went with this. I was unsure of what option to get, was looking at the Shelly things, the iSmart, few others. Went MyQ cos it was so built in to HA and it's so accessible at the store....

[TomBrandt]

Can't believe I went with this. I was unsure of what option to get, was looking at the Shelly things, the iSmart, few others. Went MyQ cos it was so built in to HA and it's so accessible at the store....

There's a You tube video review of ratdgo, wish I saw that first. spent money on Gocontrol and it won't work with the myq because of security 2.0 +. ratdgo creates the rolling code generator of the wall unit. Anyway watch the video better explained there.

[wrmacj]

Here is a good review of ratdgo with an interview with the creator of Ratdgo.
Review by https://youtu.be/F6IVu7cIEf4 Ratdgo Pauls website with tech info https://paulwieland.github.io/ratgdo/ Paul said he hopes to integate directly with HomeKit in future version.

[wrmacj]

According to the HA MyQ integration page, it indicates that the following Using HomeKit controller for local control - No Apple device required If you have a 819LMB or ### MYQ-G0303-SP, Home Assistant can speak HomeKit Accessory Protocol and control the device over the local network without the need to access to the cloud service. As a bonus, updates are push and near-instantaneous. Does that mean if you have either of these two devices, that you still can purchase, you will be free of all these problems?

[jermanoid]

The hub works with homekit, which you can import your garage doors from there into HA as a homekit device cloud free. The problem with this hub is you're supporting MyQ by buying it. Also I don't trust that their hub would not end up magically gimped at some point.

[rm-rf-asterisk]

According to the HA MyQ integration page, it indicates that the following Using HomeKit controller for local control - No Apple device required If you have a 819LMB or ### MYQ-G0303-SP, Home Assistant can speak HomeKit Accessory Protocol and control the device over the local network without the need to access to the cloud service. As a bonus, updates are push and near-instantaneous. Does that mean if you have either of these two devices, that you still can purchase, you will be free of all these problems?

I actually do have this device. How do I import said device as a homekit device? I am not sure what you mean by that. I though that is how myq is added to HA.

[jermanoid]

@rm-rf-asterisk Connect your homekit device to your wifi network. From the HA integrations page, click add integration. Search for apple and you can select "Homekit Device". it should show homekit devices on your network.

[kristof-mattei]

Those devices are discontinued.

According to the HA MyQ integration page, it indicates that the following Using HomeKit controller for local control - No Apple device required If you have a 819LMB or ### MYQ-G0303-SP, Home Assistant can speak HomeKit Accessory Protocol and control the device over the local network without the need to access to the cloud service. As a bonus, updates are push and near-instantaneous. Does that mean if you have either of these two devices, that you still can purchase, you will be free of all these problems?

[rm-rf-asterisk]

@rm-rf-asterisk Connect your homekit device to your wifi network. From the HA integrations page, click add integration. Search for apple and you can select "Homekit Device". it should show homekit devices on your network.

Nothing ever shows up as Homekit device. In the myq app I can see that it sees my other homekit devices so it knows there is a homekit just no ability to control or add it. I am ignoring using HA even to confirm it works with my iPhone first.

I think you mean the black myq hub. none of the white myq hubs are homekit compatible.

[kristof-mattei]

I'm actually looking at the device's reviews: https://9to5mac.com/2019/08/15/homekit-garage-door-myq-home-bridge-review-video/

They communicate directly with the garage door via that rotating signal, but don't have that puck on the door to essentially sense whether the garage door is opened or closed.

Maybe that was an issue & that's why they pulled it?

Edit: I take that back, it needs to have a smart device like the 821LMC to check whether the door is open or not.

But then how does it communicate this status? If everything happens locally then there must be an interface on the 821LMC directly to send the open/close signal.

[Whaledad]

Has anybody tried this? I've been holding off because I'm using Amazon Key Delivery and that will stop to work with this solution:

• integrate the garage door with Alarm.com (which will disable it in the MyQ app (hence will stop Amazon Key delivery)
• I have already integrated Alarm.com with HA and it is working surprisingly well
• the two Zwave Kwikset locks that I have integrated into Alarm.com are perfectly operational through the Alarm.com integration; will the same be true for the MyQ integration into Alarm.com?

[wrmacj]

I actually do have this device. How do I import said device as a homekit device? I am not sure what you mean by that. I though that is how myq is added to HA.

@rm-rf-asterisk Instructions in HA, https://www.home-assistant.io/integrations/myq/

[Thayios]

Welp, mine suddenly started working again. I left it disabled for 24 hours and came back today, it wouldn't accept my credentials the first few times but about two hours ago it accepted them but wouldn't display devices. Suddenly about 20 minutes later, it went through and my devices showed back up. On the other hand, people really never appreciated the auto open/close I setup with automation until it went down.

EDIT: Spoke too soon. Devices just became unavailable.

[kendadk]

Athom is in stock and $18.75 +shipping https://www.athom.tech/blank-1/garage-door-opener-for-esphome

[rm-rf-asterisk]

I actually do have this device. How do I import said device as a homekit device? I am not sure what you mean by that. I though that is how myq is added to HA.

@rm-rf-asterisk Instructions in HA, https://www.home-assistant.io/integrations/myq/

I figured out the issue the links redirect to the non-homekit device. The device mentioned is the bigger black hub not the smaller white one. AKA the one they do not sell anymore, how convenient.

[jclendineng]

This issue has been going on for ages now. Garage door is pretty important, maybe I just need to do esphome. I don’t need another project…

[Donkendall]

Athom home has a pre programmed esphome garage opener for $18.75

[akballow]

I honestly would just subscribe if they offered something reasonable. Tesla myQ specific to just the car offering is offensive so I doubt it. I will see if this is the end of myQ this month.

[ChadGnad]

I went ahead and ordered a couple ratgdo devices. I can't keep wasting my time with this. losing access to my garage doors constantly because chaimberland thinks people are going to pay for their lame cloud that provides basic features at a premium subscription. They are being petty and fighting a battle they will never win.

Agree with everything except "fighting a battle they will never win" I think you just demonstrated they won? They have prevented us from using the API with HA.

Ratgdo, gets us our cake and we can eat it too. Problem is it is still pricey, a bunch of work to put together and setup. $60 + box $15 or $75 cdn plus install and configuration. Plus you have to come up with another power source for each of these new units. Far from a simple solution but better than any other, I think.

Don't get me wrong, I think the Ratgdo is awsome for a bunch of reasons!! I just don't see spending $100 to enable my two garage doors, when it was free before, "winning"? I would call winning, sticking it to Chamberline by having LocalMyQ created similar to LocalTuya. That is the wish list. :)

I will happily pay 89 bucks with shipping for two units to a guy who created what we all wanted 5 years ago. MyQ is not getting any better, and this simplifies my Home Assistant and removes yet another cloud based service. I use a HomeKit Bridge to my phone so I can create automations based on my phone location to control my garage door. And the wiring is nothing if you mount this adjacent to the opener.

F%$# MyQ. Once I get HA stabilized again and running 99.99999% up time I will gladly pull the MyQ hub out.

[codycrypto]

What a CF

[cferra]

For the cloudflare issue, can something like flaresolverr be used to mitigate?

https://github.com/FlareSolverr/FlareSolverr

in the meantime, since i can’t ditch MyQ altogether thanks to the tesla integration, i have added on a supplemental ismartgate device that has local control for any that is interested in an out of the box package.

[kristof-mattei]

I honestly would just subscribe if they offered something reasonable. Tesla myQ specific to just the car offering is offensive so I doubt it. I will see if this is the end of myQ this month.

I honestly disagree. This is a device that sits at home and translates home signal to something that is exposed via an API.

Having them expose an API is literally more costly than me allowing to talk to the device directly.

I don't want to have to see an ad every time I open up the app to send a command to something I paid for in full.

Their website might cost money, but if I have the device at home listening to commands there is no ongoing cost for them.

This is pure rent seeking.

[Whaledad]

OK, I left it disabled for almost 3 hours yesterday and enabled it, and it came back on. Int has now been back on for about 24 hours.... Fingers crossed....

[ironjaw72]

OK, I left it disabled for almost 3 hours yesterday and enabled it, and it came back on. Int has now been back on for about 24 hours.... Fingers crossed....

You inspired me to try after the same downtime. It's working and I was able to control my door.

[ironjaw72]

And it died again with 429's

[akballow]

And it died again with 429's

Sounds like a rate api issue. Can this integration be rewritten to not check for status therefore reducing the number of api calls? I don’t really care for the status of the door. Maybe once in a while to keep the api calls down but having just calls to open or close the door should prevent this obvious rate limit problem we are hitting

[jermanoid]

Has anyone tried to sniff the traffic coming from the MyQ garage doors to see what those calls looks like? I'm not an expert in this. But perhaps there is a way to emulate their server locally instead of authenticating with MyQ cloud as a client. Then use a local DNS entry to route the myq-cloud.com domains to the homeassistant server.

[jd3073]

Experiencing the same: "failed setup, will retry" along with "failed to connect" errors after working flawlessly for 2-3 years. Monitoring this thread for any ideas to restore. Guessing reverting back to previous HA version has nothing to do with issue? Currently running: Home Assistant 2023.10.3 Supervisor 2023.10.0 Operating System 11.0 Frontend 20231005.0 - latest

[some-guy-23]

Has anyone tried to sniff the traffic coming from the MyQ garage doors to see what those calls looks like? I'm not an expert in this. But perhaps there is a way to emulate their server locally instead of authenticating with MyQ cloud as a client. Then use a local DNS entry to route the myq-cloud.com domains to the homeassistant server.

This would be the equivalent of a MitM attack, so would only work if the MyQ device was ignoring server certificate errors. Which... would be quite a bad security issue for something that can control access to your home.

[radhoo2k10]

Experiencing the same: "failed setup, will retry" along with "failed to connect" errors after working flawlessly for 2-3 years. Monitoring this thread for any ideas to restore. Guessing reverting back to previous HA version has nothing to do with issue? Currently running: Home Assistant 2023.10.3 Supervisor 2023.10.0 Operating System 11.0 Frontend 20231005.0 - latest

No. This is Myq that has changed the API. I went back to impulse from zwave device and tilt sensor and created a generic garage door cover. This helped: https://www.youtube.com/watch?v=-rLD8GzZQu4&t=1s

[buskeyl]

For whatever its worth, mine is still broken, can't even install the MyQ integration now. I'm on Home Assistant Yellow, fullt updated. I had "fixed" mine a while back by providing a user string value within the container. It worked for a while and now has stopped. I was successfully able to back out those changes by following this specific set of instructions collected here.

docker exec -it homeassistant /bin/bash pip uninstall python-myq rm -rf config/pymyq rm -rf /usr/src/homeassistant/homeassistant/components/myq/ wget https://github.com/home-assistant/core/archive/refs/tags/2023.10.3.tar.gz cp -f core-2023.10.3/homeassistant/components/myq /usr/src/homeassistant/homeassistant/components/| tar -xvf 2023.10.3.tar.gz cp -fr core-2023.10.3/homeassistant/components/myq /usr/src/homeassistant/homeassistant/components/ rm -rf core-2023.10.3 rm 2023.10.3.tar.gz

And restarted HA. I still get the same error of too many connections:

2023-10-21 15:59:30.743 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-21 15:59:30.840 DEBUG (MainThread) [pymyq.request] Attempt 1 request failed with exception : 429 - Too Many Requests 2023-10-21 15:59:30.840 DEBUG (MainThread) [pymyq.request] Too many request have been made - putting a temporary pause on sending any requests for 45 minutes

So I disabled the MyQ integration, restarted HA, went out for about three hours, came back, enabled the Integration and instantly got the same error. This has happened a few times. Anyone wants to start an open letter to the Chamberlan Group that states this marketing approach motivates me to take my brand new Lift Master garage door opener and shitcan it for this reason alone, I'll sign it.

In the meantime, I have been able to log out of and back into the MyQ app using the exact same credentials as the Add-on, without error. So the issue doesn't seem to be connected to the credentials.

[Donkendall]

Experiencing the same: "failed setup, will retry" along with "failed to connect" errors after working flawlessly for 2-3 years. Monitoring this thread for any ideas to restore. Guessing reverting back to previous HA version has nothing to do with issue? Currently running: Home Assistant 2023.10.3

Supervisor 2023.10.0

Operating System 11.0

Frontend 20231005.0 - latest

This is not a Homeassistant problem it is a MYQ problem that they purposely caused to make us stop using our own data and have to use their apps so we will see their ads on the app.