MyQ stopped working - "Credentials are invalid"

Third party integrations
1

My MyQ integration has stopped working. The message I get when trying to use it is:

Failed to call service cover/open_cover. Opening of cover Garage Door failed with error: Credentials are invalid, update username/password to re-try authentication.

I couldn’t find how to edit the username or password, so I deleted the integration and re-added it, but no luck. I also changed my password in MyQ to make sure that I had the correct password, but it’s still not working.

2

Same issue here. Any resolution?

3

I’ve got nothing. Still hoping for some responses here.

4

Having the same issue. Stopped responding with same error, tried re-adding the integration with valid credentials, same issue.

5

Same issue here. I think it started failing right after the 2022.10.5 upgrade.

Log Details (ERROR)
Logger: pymyq.api
Source: components/myq/__init__.py:42
First occurred: 06:39:30 (23 occurrences)
Last logged: 07:19:45

Authentication failed: Error requesting data from https://partner-identity.myq-cloud.com/connect/authorize: Cannot connect to host partner-identity.myq-cloud.com:443 ssl:default [Try again]
6

More info: this problem resolved itself by ‘power cycling’ the VM HA is running in. A ‘system reboot’ and a ‘restart HA’ (from the HA GUI) did not resolve the problem, but a complete reboot of the VM did. It might have something to do with my custom hostname getting changed back to the default homeassistant.local by the 2022.10.5 upgrade, or perhaps that was just a coincidence. For me, all systems now appear to be back to normal and operational (except using the default homeassistant.local hostname).

7

Thanks. A system restart worked for me too.

8

Thanks this thread really helped me out. I got this same error coincidentally the day after “pairing” my Telsa Model 3, and then un-pairing after noticing the MyQ Tesla integration has a subscription.

While I may or may not get the subscription long term, I had assumed this “limbo” status I put myself in with my MyQ account was the root cause (“Created” my https://www.myqservices.com/ account associated with my main MyQ account, then removing the Tesla from this account without accepting the 30 day trial).

Instead, the simple reboot of my VM fixed it!