MyQ fails to setup with 401 or 429 error

[atruest]

The problem

HA 2023.10.1 worked ok for a few days but now similar failure when trying a reload. See error log below

What version of Home Assistant Core has the issue?

2023.10.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

MyQ

Link to integration documentation on our website

No response

Diagnostics information

Logger: homeassistant.components.myq Source: helpers/update_coordinator.py:322 Integration: MyQ (documentation, issues) First occurred: 10:19:24 AM (1 occurrences) Last logged: 10:19:24 AM

Error fetching myq devices data: Error trying to re-authenticate to myQ service: Error requesting data from https://partner-identity.myq-cloud.com/connect/token: 401 - Unauthorized

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Same issue as before but now with 401 instead of 403

Additional information

No response

[MikeMcGlinch]

Now that the patch has been merged, you should be able to just run this command from your HA install/container.

pip install https://github.com/Python-MyQ/Python-MyQ/releases/download/v3.1.13/python_myq-3.1.13-py3-none-any.whl

I tried and it said "No such file or directory"?

[mojomojoman]

so 429 means just wait for cooldown?

Yes and anyone reading this thinking I'll fix it later or I'll wait for the official fix should at least DISABLE the integration in the meantime. I disabled it when I realized it was broken and saw this thread and knew it would not be a quick fix. And whenever I failed to fix it I immediately disable again. So I never had to deal with the 429's. If you leave it enabled and broken it will retry to aggressively and get you throttled every time.

[VinnyD12]

so 429 means just wait for cooldown?

Yes and anyone reading this thinking I'll fix it later or I'll wait for the official fix should at least DISABLE the integration in the meantime. I disabled it when I realized it was broken and saw this thread and knew it would not be a quick fix. And whenever I failed to fix it I immediately disable again. So I never had to deal with the 429's. If you leave it enabled and broken it will retry to aggressively and get you throttled every time.

thank you for that info, will disable in the meantime

[ratsputin]

Has anyone tried setting up the integration again from scratch? After this whole thing started, I deleted the integration. Now, when I try to set it up, I receive the following after entering the username/password:

ERROR (MainThread) [pymyq.api] Authentication failed: Error requesting data from https://partner-identity.myq-cloud.com/connect/token: 401 - Unauthorized

I've reset my password twice and it works fine in the app.

This is with the v3.1.13 of Python-MyQ with the fix.

[shanelord01]

Has anyone tried setting up the integration again from scratch? After this whole thing started, I deleted the integration. Now, when I try to set it up, I receive the following after entering the username/password:

ERROR (MainThread) [pymyq.api] Authentication failed: Error requesting data from https://partner-identity.myq-cloud.com/connect/token: 401 - Unauthorized

I've reset my password twice and it works fine in the app.

This is with the v3.1.13 of Python-MyQ with the fix.

I've got the same issue. Did the below and can't login:

---

I'm running: Home Assistant 2023.10.1 Supervisor 2023.10.0 Operating System 10.5 Frontend 20231005.0 - latest

In "Advanced SSH & Web Terminal":

docker exec -it homeassistant /bin/bash
cd /config
pip install Python-MyQ==v3.1.13

Then rebooted Home Assistant.

[ratsputin]

Now that the patch has been merged, you should be able to just run this command from your HA install/container.

pip install https://github.com/Python-MyQ/Python-MyQ/releases/download/v3.1.13/python_myq-3.1.13-py3-none-any.whl

I tried and it said "No such file or directory"?

Try:

pip install Python-MyQ==v3.1.13

[MikeMcGlinch]

Now that the patch has been merged, you should be able to just run this command from your HA install/container.

pip install https://github.com/Python-MyQ/Python-MyQ/releases/download/v3.1.13/python_myq-3.1.13-py3-none-any.whl

I tried and it said "No such file or directory"?

Try:

pip install Python-MyQ==v3.1.13

zsh: command not found: on-MyQ==v3.1.13

[MikeMcGlinch]

Now that the patch has been merged, you should be able to just run this command from your HA install/container.

pip install https://github.com/Python-MyQ/Python-MyQ/releases/download/v3.1.13/python_myq-3.1.13-py3-none-any.whl

I tried and it said "No such file or directory"?

Try: pip install Python-MyQ==v3.1.13

zsh: command not found: on-MyQ==v3.1.13

Finally got it done.

[MikeMcGlinch]

403 Forbidden

[jermanoid]

Egh. I was getting the 429. But my account was locked out. Tried to reset the pw and myq freaked out and never sent me an email, but locked me out of the password reset as well without sending the email. pure comedy.

[dmperl]

Looks good:

System information
  IPv4 addresses for enp1s0: 
  IPv6 addresses for enp1s0: 

  OS Version:               Home Assistant OS 10.5
  Home Assistant Core:      **2023.8.3**

  Home Assistant URL:       http://homeassistant.local:8123
  Observer URL:             http://homeassistant.local:4357
➜  ~
➜  ~
➜  ~ docker exec -it homeassistant /bin/bash
homeassistant:/config# cd /config
homeassistant:/config# pip install Python-MyQ==v3.1.13
Collecting Python-MyQ==v3.1.13
  Downloading python_myq-3.1.13-py3-none-any.whl (22 kB)
Requirement already satisfied: aiohttp<4.0,>=3.7 in /usr/local/lib/python3.11/site-packages (from Python-MyQ==v3.1.13) (3.8.5)
Requirement already satisfied: beautifulsoup4<5.0.0,>=4.9.3 in /usr/local/lib/python3.11/site-packages (from Python-MyQ==v3.1.13) (4.11.1)
Requirement already satisfied: pkce<2.0.0,>=1.0.2 in /usr/local/lib/python3.11/site-packages (from Python-MyQ==v3.1.13) (1.0.3)
Requirement already satisfied: attrs>=17.3.0 in /usr/local/lib/python3.11/site-packages (from aiohttp<4.0,>=3.7->Python-MyQ==v3.1.13) (22.2.0)
Requirement already satisfied: charset-normalizer<4.0,>=2.0 in /usr/local/lib/python3.11/site-packages (from aiohttp<4.0,>=3.7->Python-MyQ==v3.1.13) (3.2.0)
Requirement already satisfied: multidict<7.0,>=4.5 in /usr/local/lib/python3.11/site-packages (from aiohttp<4.0,>=3.7->Python-MyQ==v3.1.13) (6.0.4)
Requirement already satisfied: async-timeout<5.0,>=4.0.0a3 in /usr/local/lib/python3.11/site-packages (from aiohttp<4.0,>=3.7->Python-MyQ==v3.1.13) (4.0.2)
Requirement already satisfied: yarl<2.0,>=1.0 in /usr/local/lib/python3.11/site-packages (from aiohttp<4.0,>=3.7->Python-MyQ==v3.1.13) (1.9.2)
Requirement already satisfied: frozenlist>=1.1.1 in /usr/local/lib/python3.11/site-packages (from aiohttp<4.0,>=3.7->Python-MyQ==v3.1.13) (1.4.0)
Requirement already satisfied: aiosignal>=1.1.2 in /usr/local/lib/python3.11/site-packages (from aiohttp<4.0,>=3.7->Python-MyQ==v3.1.13) (1.3.1)
Requirement already satisfied: soupsieve>1.2 in /usr/local/lib/python3.11/site-packages (from beautifulsoup4<5.0.0,>=4.9.3->Python-MyQ==v3.1.13) (2.4.1)
Requirement already satisfied: idna>=2.0 in /usr/local/lib/python3.11/site-packages (from yarl<2.0,>=1.0->aiohttp<4.0,>=3.7->Python-MyQ==v3.1.13) (3.4)
Installing collected packages: Python-MyQ
Successfully installed Python-MyQ-3.1.13
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

[notice] A new release of pip is available: 23.1.2 -> 23.2.1
[notice] To update, run: pip install --upgrade pip
homeassistant:/config#

Got 429 error.... awaiting cool-down period to end... It worked!!! Thank you!!!

Edit 1: next, day. I upgraded from HA Core 2023.8.3 to 2023.10.2
The official update works for me ;-) Bump Python-MyQ to v3.1.13 (@justinlindh - #101852)

[joshhoff408]

Has anyone tried setting up the integration again from scratch? After this whole thing started, I deleted the integration. Now, when I try to set it up, I receive the following after entering the username/password: ERROR (MainThread) [pymyq.api] Authentication failed: Error requesting data from https://partner-identity.myq-cloud.com/connect/token: 401 - Unauthorized I've reset my password twice and it works fine in the app. This is with the v3.1.13 of Python-MyQ with the fix.

I've got the same issue. Did the below and can't login:

I'm running: Home Assistant 2023.10.1 Supervisor 2023.10.0 Operating System 10.5 Frontend 20231005.0 - latest

In "Advanced SSH & Web Terminal":

docker exec -it homeassistant /bin/bash
cd /config
pip install Python-MyQ==v3.1.13

Then rebooted Home Assistant.

Same issue here. Installed the 3.1.13 fix successfully and restarted, but still getting the 401 error.

[joshhoff408]

Has anyone tried setting up the integration again from scratch? After this whole thing started, I deleted the integration. Now, when I try to set it up, I receive the following after entering the username/password: ERROR (MainThread) [pymyq.api] Authentication failed: Error requesting data from https://partner-identity.myq-cloud.com/connect/token: 401 - Unauthorized I've reset my password twice and it works fine in the app. This is with the v3.1.13 of Python-MyQ with the fix.

I've got the same issue. Did the below and can't login: I'm running: Home Assistant 2023.10.1 Supervisor 2023.10.0 Operating System 10.5 Frontend 20231005.0 - latest In "Advanced SSH & Web Terminal":

docker exec -it homeassistant /bin/bash
cd /config
pip install Python-MyQ==v3.1.13

Then rebooted Home Assistant.

Same issue here. Installed the 3.1.13 fix successfully and restarted, but still getting the 401 error.

So the "pip install" command alone didn't do it for me, but when I went back and did the manual update (below), it flipped from 401 errors to 429, so just waiting out the throttle now. Thanks!!

docker exec -it homeassistant /bin/bash cd /config wget https://github.com/justinlindh/Python-MyQ/archive/refs/heads/fix-403-forbidden.zip unzip -o -j fix-403-forbidden.zip -d /usr/local/lib/python3.11/site-packages/pymyq

[thiagobruch]

I attempted both methods:

1st: pip install Python-MyQ==v3.1.13

2nd: wget https://github.com/justinlindh/Python-MyQ/archive/refs/heads/fix-403-forbidden.zip unzip -o -j fix-403-forbidden.zip -d /usr/local/lib/python3.11/site-packages/pymyq

Received the 401 error. Tried to delete the entry in HA and add again, however, I cannot authenticate anymore. I logged out and logged back in in the Android App without issue. And still, I cannot authenticate with MyQ in HA anymore.

Anybody having the same issue?

[shanelord01]

I attempted both methods:

1st: pip install Python-MyQ==v3.1.13

2nd: wget https://github.com/justinlindh/Python-MyQ/archive/refs/heads/fix-403-forbidden.zip unzip -o -j fix-403-forbidden.zip -d /usr/local/lib/python3.11/site-packages/pymyq

Received the 401 error. Tried to delete the entry in HA and add again, however, I cannot authenticate anymore. I logged out and logged back in in the Android App without issue. And still, I cannot authenticate with MyQ in HA anymore.

Anybody having the same issue?

I did the same. I can't get past the login for the integration now - "Failed to connect"

Logger: pymyq.api
Source: components/myq/config_flow.py:37
First occurred: 1:58:09 PM (3 occurrences)
Last logged: 2:01:30 PM

Authentication failed: Error requesting data from https://partner-identity.myq-cloud.com/connect/token: 401 - Unauthorized

[ironjaw72]

I had to do the following. Just doing pip install without the docker command did install files but didn't work. I am running HA as a virtual machine in VirtualBox

within advanced terminal: docker exec -it homeassistant /bin/bash pip install Python-MyQ==v3.1.13 exit

then restart Home Assistant

[izarkhin]

I attempted both methods:

1st: pip install Python-MyQ==v3.1.13

2nd: wget https://github.com/justinlindh/Python-MyQ/archive/refs/heads/fix-403-forbidden.zip unzip -o -j fix-403-forbidden.zip -d /usr/local/lib/python3.11/site-packages/pymyq

Received the 401 error. Tried to delete the entry in HA and add again, however, I cannot authenticate anymore. I logged out and logged back in in the Android App without issue. And still, I cannot authenticate with MyQ in HA anymore.

Anybody having the same issue?

Same here. Tried both pip and manual install, rebooted HA, still getting the 401 when trying to set up MyQ integration.

[x046866x]

I have not read every entry here, so apologies if this was attempted, but I had to reset my password even for the MyQ app. Dunno if you tried that... Or if it will help.

I hope to apply sooner of the fix attempts later this morning.

Get BlueMail for Androidhttps://bluemail.me On Oct 12, 2023, at 2:49 AM, izarkhin @.**@.>> wrote:

I attempted both methods:

1st: pip install Python-MyQ==v3.1.13

2nd: wget https://github.com/justinlindh/Python-MyQ/archive/refs/heads/fix-403-forbidden.zip unzip -o -j fix-403-forbidden.zip -d /usr/local/lib/python3.11/site-packages/pymyq

Received the 401 error. Tried to delete the entry in HA and add again, however, I cannot authenticate anymore. I logged out and logged back in in the Android App without issue. And still, I cannot authenticate with MyQ in HA anymore.

Anybody having the same issue?

Same here. Tried both pip and manual install, rebooted HA, still getting the 401 when trying to set up MyQ integration.

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/101763#issuecomment-1759017065, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABZNQC5ADNP4WWCSDRP3ZJ3X66HI3ANCNFSM6AAAAAA52SFHWA. You are receiving this because you commented.Message ID: @.***>

[olivier1091]

Bonjour; I have as well the same issue: I've tried to install (pip install Python-MyQ==v3.1.13) Restrated HA ent tried to reconfigure MyQ integration, no sucess, 401 error

Logger: pymyq.api Source: components/myq/config_flow.py:37 First occurred: 09:45:29 (2 occurrences) Last logged: 09:51:52

Authentication failed: Error requesting data from https://partner-identity.myq-cloud.com/connect/token: 401 - Unauthorized

As a dumy test, I've tried to connect to https://partner-identity.myq-cloud.com I get there a menu proposing "to secure page" --> https://partner-identity.myq-cloud.com/Account/LoginWithEmail?returnUrl=%2FHome%2FSecure My user name and password works fine on this page so the account is valid. From Chrome, accesing ttps://partner-identity.myq-cloud.com/connect/token give an error {"error":"invalid_request"}

[jeeftor]

pip install Python-MyQ

Open terminal and you can run:

docker exec -it homeassistant pip install -U Python-MyQ

[Neu-Bob]

running ha from docker, followed "docker exec -it homeassistant pip install -U Python-MyQ" .. rebooted, 401

[jeeftor]

I'm guessing this is maybe part of the issue - the repo needs a new maintainer ...

https://github.com/Python-MyQ/Python-MyQ/issues/15

[calisro]

HAOS instructions. If you have a different install, you probably don't need the 'docker exec -it homeassistant' portion.

docker exec -it homeassistant pip install -U Python-MyQ
docker exec -it homeassistant rm -rf /config/pymyq
docker exec -it homeassistant wget https://github.com/justinlindh/Python-MyQ/archive/refs/heads/fix-403-forbidden.zip 
docker exec -it homeassistant unzip -o -j fix-403-forbidden.zip -d /config/pymyq 

Then Restart home assistant and wait an hour.

Note: After you upgrade HA to 10.3 or so (which should contain the fixes), you'll need to remove that pymyq folder.

docker exec -it homeassistant rm -rf /config/pymyq 

[Neu-Bob]

HAOS instructions. If you have a different install, you probably don't need the 'docker exec -it homeassistant' portion.

docker exec -it homeassistant pip install -U Python-MyQ
docker exec -it homeassistant rm -rf /config/pymyq
docker exec -it homeassistant wget https://github.com/justinlindh/Python-MyQ/archive/refs/heads/fix-403-forbidden.zip 
docker exec -it homeassistant unzip -o -j fix-403-forbidden.zip -d /config/pymyq 

Then Restart home assistant and wait an hour.

Note: After you upgrade HA to 10.3 or so (which should contain the fixes), you'll need to remove that pymyq folder.

docker exec -it homeassistant rm -rf /config/pymyq 

Bang... that worked... thanks

[Lash-L]

@home-assistant close

[rlyons20]

i just read back, and if i'm following, is our integration requesting an access token every time? why aren't we requesting a refresh token?

[Lash-L]

Hello everyone - I am closing this issue as it has been resolved with #101852 and will be included in 2023.10.2 #101871 I would highly recommend not doing any kind of manual solutions - and instead just wait for 10.2 to come out which will probably be later today.

I won't ask for this thread to be locked, but please restrain from commenting so others can see this

[izarkhin]

For some reason, I can't update to 2023.10.2. When I go to System -> Updates -> check for updates, it doesn't find any. I ran ha core update --version 2023.10.2 --backup from Advanced SSH and rebooted HA. The process was completed successfully, but the version is still Home Assistant 2023.10.1 Supervisor 2023.10.0 Operating System 10.5 Frontend 20231005.0 - latest

What am I doing wrong?!

[x046866x]

For some reason, I can't update to 2023.10.2. When I go to System -> Updates -> check for updates, it doesn't find any. I ran ha core update --version 2023.10.2 --backup from Advanced SSH and rebooted HA. The process was completed successfully, but the version is still Home Assistant 2023.10.1 Supervisor 2023.10.0 Operating System 10.5 Frontend 20231005.0 - latest

What am I doing wrong?!

I believe this will be part of 10.2... Not released yet.... Hopefully later today.

[ethank]

So if we had the manual patch, its wait an hour after removing it and restarting?

[atruest]

Stop responding to this message! It’s now closed.On Oct 12, 2023, at 12:19 PM, Ethan Kaplan @.***> wrote: So if we had the manual patch, its wait an hour after removing it and restarting?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[mattgahs]

With 181 comments, it's obvious lots of people are tracking this particular thread for a solution. I don't think it's fair to Close an issue just because a PR was approved and then to tell everyone "just wait for 10.2". It would be good to know that 10.2 actually fixes the issue for most people. Lots of folks are watching this thread and waiting for dopes like me to update right away and provide feedback if updating to 10.2 works.

It does.

Watchtower saw the HA 10.2 update come down and upgraded my HA container about 30 minutes ago. Once HA came back up as 10.2, the MyQ cover entity was still offline, and the HA logs showed a 429 error (cooldown required). I disabled the MyQ integration for about 30 minutes, and reactivated it just now. After a minute, my MyQ entities came back online.

Some folks might need a little bit of assistance in getting their systems functional again, and I would hope this community can help them out - i'm here to help as best I can. Eventually, everyone's gear will work again and this thread will go quiet.

[Lash-L]

I don't think it's fair to Close an issue just because a PR was approved and then to tell everyone "just wait for 10.2"

Hence why I closed it and didn't lock it :)

Github issues are meant to mark an issue that needs development time attributed to it - it gets closed once the code that fixed it is merged in. This lets us know that no one needs to work on this issue anymore as a fix should be on the way.

If there continues to be an issue - then either A) a new issue should be created (as there is a new foundation of changes and the underyling problem has likely changed) or B) The old issue should be reopened

Github is not a perfect issue tracker, It exist more so for the developers than it does for end users and troubleshooting, that is just how github was designed.

But again, that's why I just closed it, why it was not locked. People can still troubleshoot here, but need to be mindful that there are dozens of people who get an email everytime they post.

[jonnylangefeld]

+1 to what @Lash-L said. It's okay to close an issue with a PR that addresses this issue, even if the code of that PR isn't released yet. It's actually a common thing to put Fix #<issue number> into a PR description and Github auto-closes the issue once the PR is merged. One can still comment on a closed issue or open a new one to address newly introduced regressions in the new PR.

We should all rather thank @Lash-L as he's fixing issues for 100s of users for a service that he doesn't even use himself.

That being said, I can't wait for a resolution as all our garage automations aren't working anymore 🙈

[x046866x]

I second the thanks to @Lash-L . This is an excellent example of a very active community solving a problem collaboratively and quickly!

Thanks everybody!

[ratsputin]

Also extending thanks to @Lash-L!

Having said that, I just upgraded to homeassistant-2023.10.2 and am still seeing the behavior mentioned when I readd the MyQ integration:

Oct 12 14:04:33 ha hass[52039]: 2023-10-12 14:04:33.943 ERROR (MainThread) [pymyq.api] Authentication failed: Error requesting data from https://partner-identity.myq-cloud.com/connect/token: 401 - Unauthorized

(venv) homeassistant@ha:~$ pip show Python-MyQ
Name: python-myq
Version: 3.1.13
Summary: Python package for controlling MyQ-Enabled Garage Door.
Home-page: https://github.com/Python-MyQ/Python-MyQ
Author: Lash-L
Author-email: lukelashley99@gmail.com
License: MIT
Location: /srv/homeassistant/venv/lib/python3.11/site-packages
Requires: aiohttp, beautifulsoup4, pkce
Required-by:
(venv) homeassistant@ha:~$

This is using the same username/password that works in the application on iOS.

[NukeThemTillTheyGlow]

Also extending thanks to @Lash-L!

Having said that, I just upgraded to homeassistant-2023.10.2 and am still seeing the behavior mentioned when I readd the MyQ integration:

Oct 12 14:04:33 ha hass[52039]: 2023-10-12 14:04:33.943 ERROR (MainThread) [pymyq.api] Authentication failed: Error requesting data from https://partner-identity.myq-cloud.com/connect/token: 401 - Unauthorized

(venv) homeassistant@ha:~$ pip show Python-MyQ
Name: python-myq
Version: 3.1.13
Summary: Python package for controlling MyQ-Enabled Garage Door.
Home-page: https://github.com/Python-MyQ/Python-MyQ
Author: Lash-L
Author-email: lukelashley99@gmail.com
License: MIT
Location: /srv/homeassistant/venv/lib/python3.11/site-packages
Requires: aiohttp, beautifulsoup4, pkce
Required-by:
(venv) homeassistant@ha:~$

This is using the same username/password that works in the application on iOS.

Similar, but different outcome after applying the update (10.2) about 30 min ago. Getting error error 403 -Forbidden. I disabled the MyQ integration for about 20 min after the update, then turned on debug, go these errors, and just disabled again.

What should I do?

2023-10-12 15:36:26.192 DEBUG (MainThread) [pymyq.request] Attempt 5 request failed with exception : 403 - Forbidden 2023-10-12 15:36:26.192 DEBUG (MainThread) [pymyq.api] Error requesting data from https://partner-identity.myq-cloud.com/Account/LoginWithEmail?returnUrl=/connect/authorize/callback?client_id%3DIOS_CGI_MYQ%26code_challenge%3DiCU-TypJHrhZt6R6jH5VY_YINM_FlXGH3FgeMVMe4ts%26code_challenge_method%3DS256%26redirect_uri%3Dcom.myqops%253A%252F%252Fios%26response_type%3Dcode%26scope%3DMyQ_Residential%2520offline_access: 403 - Forbidden 2023-10-12 15:36:26.193 ERROR (MainThread) [pymyq.api] Authentication failed: Error requesting data from https://partner-identity.myq-cloud.com/Account/LoginWithEmail?returnUrl=/connect/authorize/callback?client_id%3DIOS_CGI_MYQ%26code_challenge%3DiCU-TypJHrhZt6R6jH5VY_YINM_FlXGH3FgeMVMe4ts%26code_challenge_method%3DS256%26redirect_uri%3Dcom.myqops%253A%252F%252Fios%26response_type%3Dcode%26scope%3DMyQ_Residential%2520offline_access: 403 - Forbidden

[hitnrun30]

Want to thank you all for fixing this

[nk3750]

DIsable the plugin for a minute or 2, and then restart HA if it doesn't work for you.

[NukeThemTillTheyGlow]

I disabled, rebooted, enabled and no luck. Now debugging doesn't show up as an option. And I was prompted to restart HA after disabling again to complete the process. Not sure what's going on.

[matthewrosner]

Still getting the 403. Deleted integration and can't add back. Running 10.2

[seanharding]

10.2 worked for me. I had disabled (but not removed) the integration when the problem started. Upgraded to 10.2, re-enabled the integration, and it immediately worked.

[mstberto]

For those of you stating that it is not working, please make sure you have also deleted the previous patch if it was installed.

[drothenberger]

@NukeThemTillTheyGlow and @matthewrosner, I recommend you start a new GitHub issue for not being able to get the integration running after installation.

[bbailey2828]

I ran: pip3 uninstall pymyq in Home Assistant terminal

• Restart HA

• Installed the patch

• Waited for 403 timeout

• Upgraded to 10.2

• Installed integration

And now it works again.

@matthewrosner

[bbailey2828]

I ran: pip3 uninstall pymyq in Home Assistant terminal

• Restart HA

• Installed the patch

• Waited for 403 timeout

• Upgraded to 10.2

• Installed integration

And now it works again.

@matthewrosner

I'm not sure if the patch is still necessary, somebody else may be able to confirm. These were just my actions and it worked for me.

[NukeThemTillTheyGlow]

@NukeThemTillTheyGlow and @matthewrosner, I recommend you start a new GitHub issue for not being able to get the integration running after installation.

Submitted: https://github.com/home-assistant/core/issues/101912

[insideoud]

For those of you stating that it is not working, please make sure you have also deleted the previous patch if it was installed.

how exactly?

[drothenberger]

For those of you stating that it is not working, please make sure you have also deleted the previous patch if it was installed.

how exactly?

See https://github.com/home-assistant/core/issues/101912#issuecomment-1760525902

[ThatTallGuy21]

10.2 worked for me. I had disabled (but not removed) the integration when the problem started. Upgraded to 10.2, re-enabled the integration, and it immediately worked.

I still had the integration enabled but failing and updated to 2023.10.2 and it's still failing. Tried disabling/enabling the integration after core update and it still failed.