MyQ fails with 403 forbidden error after recent cloud changes

[Nairou]

The problem

This is the first time the MyQ integration has given me any trouble, and it started shortly after I opened the garage door today. I closed it 30 minutes later, but Home Assistant never received that notification.

This is what I see repeating in the log:

2023-09-08 10:47:32.661 ERROR (MainThread) [homeassistant.components.myq] Error fetching myq devices data: Error requesting data from https://devices.myq-cloud.com/api/v5.2/Accounts/86f16316-3d74-4c7c-af7b-2d137be0693d/Devices: 403 - Forbidden

What version of Home Assistant Core has the issue?

core-2023.9.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

MyQ

Link to integration documentation on our website

https://www.home-assistant.io/integrations/myq/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @ehendrix23, 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)}}

[ryanmboyce]

Getting the same error, following thread for solution

[RockMonkey]

Same issue here

[donhoffman]

As am I.

[tggman]

Having the same issue as well. My opener disconnected at 9:47 CDT. IF @Nairou is one hour ahead of me, that would mean our issues started at exactly the same time.

[FsFalcon]

Seeing the same error as well - it appears to have started around 10:30 US Eastern time today

[jihaekor]

Having the same issue here as well; seems like it started happening at around the same time.

[Nairou]

Additional data point: After noticing the failure, I checked the MyQ app on my phone. It had no issue, and correctly showed that the garage door was closed.

[nk3750]

Having the same issue. Getting 403 forbidden reponse

[jbhorner]

I am also having this issue, and also do not have issues with the MyQ app. That said, it feels like it is still something on Chamberlain's side...a change or something that has impacted this integration. Nothing changed in my Home Assistant between the time this was working and the time it stopped.

[webmogul1]

+1

[tggman]

The MyQ app on my phone is working as well. What version of HAC is everyone running (since that was recently released).

I'm Running: Home Assistant 2023.9.0 Supervisor 2023.08.3 Operating System 10.5 Frontend 20230906.1 - latest

By the way, I also tried removing/restoring power but NOJOY.

[ryanmboyce]

Home Assistant 2023.9.0 Supervisor 2023.08.3 Operating System 10.5 Frontend 20230906.1 - latest

[nk3750]

I would honestly take a look at the Pymq library first. I WIll update y'all when I get a chance. https://github.com/arraylabs/pymyq/tree/master

[shinhwas]

+1

[Betanu701]

Same here mine went out around 10:30. I was on 2023.08.4 I just updated to 2023.09.0 same issue.

[tapash68]

I am having the same issue after installing 2023.09.0. Then i went back to the previous installation Home Assistant 2023.8.4 Supervisor 2023.08.3 Operating System 10.5 Frontend 20230802.1 - latest It was working on this but no longer.

[rk25862]

Same error here, offline since September 8, 2023 9:47:33 AM CDT.

Home Assistant 2023.9.0 Supervisor 2023.08.3 Operating System 10.5 Frontend 20230906.1 - latest

[PBrooksMac]

9:47 AM CDT for me as well.

Following.

[Lucas319315]

I am running into the same error. Following this thread.

[eengert]

Following

[brg468]

I think its safe to assume its down for everybody. Probably no need for everybody to chime in saying the same thing.

[billdwhite]

Also following

[itzalgd24]

Following

Stopped working @ 10:47am EST like everyone else Power cycle did not fix App is working fine

Possibly another API change on Chamberlain's side?

[bigmak40]

Definitely feels like an external API change.

I got annoyed and bought a ratgdo to not have to worry about this anymore...

[mrunowho]

Same issue for me.

[joshtbernstein]

that would be odd; given that it happened right after people updated to HA 2023.9, I'd suspect it is tied directly to that

I think this is it. Mine was working 12 minutes ago (12:17 PM PST) and I just upgraded to 2023.9 and it's now broken.

[nk3750]

I can confirm there are no API changes, The request for fetching devices is going through fine via Postman. (The same request the logs show to be failing for the myq integration on HA)

[clintkev251]

I rolled back to 2023.8.4 and it's still not working, so I'm not 100% convinced that this is a 2023.9 issue

[brg468]

Is anyone experiencing this that hasn't upgraded to 2023.9 yet? Quick look at the code, there weren't any significant changes in this release.

[starsoccer]

+1 on having this issue. Seems like updating somehow triggers it to break though

[garycampbellha]

I am having the same issue. I updated my Home Assistant last night and the MyQ integration worked until 11:47 AM CST today and then it became unavailable.

[brianl62]

I have not updated and it does not work. It quit at the same time everyone else had noted earlier.

[rk25862]

My instance was not working with 2023.8.3. I upgraded to 2023.9.0 after it stopped working and it was still not working after the upgrade. Seems unrelated to 2023.9.

[mrunowho]

I upgraded a few days ago and it worked fine. I had to restart to update something else and after restarting today, it no longer works.

[bigmak40]

I don't think it's base version related. Mine stopped working on a reboot while I was doing some work; I think restarting knocks you offline, not the upgrade.

[cassidyjames]

Chiming in here as well, mine stopped working earlier today. I'm guessing Chamberlain is having an outage or changed how the API works. As other have noted, the myQ app continue to works for me, so it's not as easy as chalking it up to a total outage.

[Betanu701]

Is anyone experiencing this that hasn't upgraded to 2023.9 yet? Quick look at the code, there weren't any significant changes in this release.

It was not do to the release. I think it was an API change on their end. I was running 08.4 thought the upgrade may fix it. Same issue.

Perhaps they blocked us from accessing it through the unofficial API?

[nk3750]

To reiterate. I can confirm there are no API changes. The request for fetching devices is going through fine via Postman.

[ceddy441]

I rolled back to 2023.8.4 and it's still not working, so I'm not 100% convinced that this is a 2023.9 issue

I can confirm this is NOT a 2023.9 issue.

I was running 2023.8.4 and this intermittently stop working during the past few hours. I figured there was a core change so I updated to 2023.9 and it still doesn't work.

[nebhale]

This showed up over on Scrypted as well, and it's worth noting that the entire MyQ web application appears to have shutdown which is strong candidate for root cause.

[nk3750]

Interesting, although I can still call the same APIs and fetch the devices manually.

[mkagawa]

it's weird that pymyq (https://pypi.org/project/pymyq/) still works for me. receives device list as well.

[mkagawa]

Interesting, although I can still call the same APIs and fetch the devices manually.

yeah, I did same thing via curl, and successfully got device list.

[ceddy441]

Not just a HA issue https://community.hubitat.com/t/can-no-longer-use-hubitat-to-open-garage-door/124183

Furthermore I power cycled (with battery removed) one of my two devices, however same boat.

[fender4645]

Is anyone experiencing this that hasn't upgraded to 2023.9 yet? Quick look at the code, there weren't any significant changes in this release.

I have not updated yet and it stopped working this morning.

[rk25862]

For those succeeding with postman, what addresses are you getting for devices.myq-cloud.com?

nslookup devices.myq-cloud.com Non-authoritative answer: Name: devices.myq-cloud.com.cdn.cloudflare.net Addresses: 2606:4700:4400::ac40:9876 2606:4700:4400::6812:238a 104.18.35.138 172.64.152.118 Aliases: devices.myq-cloud.com cff5top-myq-devices.trafficmanager.net

[nk3750]

I'd like to mention that, within the Home Assistant (HA) logs, there is evidence of successful login and authentication token retrieval. This suggests that there may not be any IP blocking implemented. However, I am still in the process of understanding why Postman functions correctly while HA does not simultaneously.

[rk25862]

Perhaps check the useragent sent by postman. They may have implemented blocking of the user agent or of the SSL signature.

[nk3750]

It seems the Python library pymyq is also working as expected. The issue is definitely on the HA side.