MyQ API Change

1

Noticed the MyQ is showing unknown status of my garage doors. When I try to reinstall integrations, I get an error.
Looks to be the same as older threads.

Device is up via app and through google.

2

same here they must have changed something and they have to update it

3

If you run a search on that topic, you’ll find that others have noticed this too:
Search results for ‘myq not working’ - Home Assistant Community (home-assistant.io)
Take-home:
1)It’s being worked on. The API was changed.
2)Running a search before posting will prevent multiple posts on the same topic.

1 Like
4

What do you mean multiple, I haven’t seen more than 20 or 30 saying the exact same thing.

1 Like
5

Wasn’t sure if it was an HA version or MyQ issue.

Apologies for making a new topic. :frowning:

6

Liz: No problem really.
In truth, it’s a MyQ issue. They blocked the User Agent the previously working version was using.
GlennHA:
For some values of the term :slight_smile:

7

This has been fixed, and will likely be released in a new update. See PR: Bump pyMyQ to version 2.0.12 by ehendrix23 ¡ Pull Request #44328 ¡ home-assistant/core (github.com)

8

Thanks. Updating the default user corrected the issue.

Many thanks!

9

How did you do that? I hadn’t hadn’t figure out how yet and figured I’d have to wait for the update.

10

Followed a previous post with recent issue:
I run dockers via venter ova deployment.

Basically changed one line, restarted HA, started working.

2 Likes
12

Well, I got SSH working, but the directory structure is a bit different as I’m running HA on Virtual Box. I haven’t yet found the python directory.
Seeing as this is a recurring problem, I wish they’d just put the User Agent in as a “configure” or “option” link in the integration.

13

There are so many flavors of HA.

I used putty, ran the commands, and edited the file within the link I sent earlier.

You have to enter the first command to get switched over to the docker container.

I’m not a coder and just followed the commands so my assistance will be limited.

1 Like
14

Sussed it. I had to read further on in your link to find a few things. For one, I needed the Community version of SSH and not the Official one. The Community one allows you to turn off protected mode and gives you access to the whole tree. Then I needed to refresh my memory on VI commands. (It’s been a while.)
Bottom line: I got it done. Thanks for the information you provided. It was enough for me to go the rest of the way.

1 Like
15

Thanks for posting this info, Liz. Had the same problem with MyQ on my Pi install and the link you provided got me working. Happy holidays!

16

Worked for me too. THANKS!!

Of course, it took me 2 tries because I can’t read:

1st time: * Changed to DEFAULT_USER_AGENT = “pymyq” <—WRONG
2nd time: * Changed to DEFAULT_USER_AGENT = “pymq” <-- just like the post says.

LOL

…and on the issue of creating a new thread. Absolutely the correct thing to do. Prior threads were defunct. This is clearly a new issue. Well done and thank you.

1 Like