That’s a possibility. They have been changing things a lot lately.
Mine was working 30mins prior to updating and immediately broken after the update. Rolling back to 0.110.7 now to test.
That’s a possibility. They have been changing things a lot lately.
Mine was working 30mins prior to updating and immediately broken after the update. Rolling back to 0.110.7 now to test.
I am on 0.109.6 with the patched pymyq file and am experiencing issues. Have not looked in my logs but it appears to be a MyQ issue. It worked this morning when I left for work.
I tried rolling back to me luck
I upgraded earlier today and it was still working. I suspect it is something on the myQ side of things that is causing the issue again. Works from the myQ app still so the service is up…
I’ve submitted a ticket to Chamberlain complaining about the constant API changes. Might be worth doing if you find the time.
Not sure they really care because it is not an open API.
I saw it broke again in 111.0, but is supposedly fixed in 111.1.
Can anyone confirm if it is working in the latest production (111.1 as I write this).
Here’s the github entry: https://github.com/home-assistant/core/issues/36643
Yes. Working in 111.1.
Broken again as of last evening, apparently (it has been speculated) they are playing with all the Home Assistant users, changing the UI every week for spite because we do not pay a subscription. Not sure if true, but definitely broken again.
A PR has been submitted, not sure when it will show up:
This is as annoying to me as it is to everyone else. But why in the world would they waste their time and money “playing” with Home Assistant users? If they didn’t want the HA integration to exist, all they would have to do is shut down the API.
They actually don’t want the HA integration to exist and they don’t have an official API. They were the only ones available when I bought mine so I’ve been stuck with them. Some HA users have already moved away from MyQ, which is something I’m also considering.
I’d love to move away but do not want to buy a new opener (two actually), and haven’t figured out a good way to tie in. I took apart the wall switch planning to just put a relay there, but unlike older doors you can’t just short the wires going to it, it’s some kind of digital signal. Intercepting the switch on the PCB didn’t look all that easy to do either, especially as I would like the switch to continue to work on the wall.
Suggestions welcomed as an alternative.
I’m having the same problem. What are people moving to?
I use nodered flow (instead of home assistant) but that integration is based upon the same principle of using the API by pretending to be the Chamberlain’s mobile app. It is now broken in node-RED as well.
Update: My previous Node-RED integration was using lower case for the “username” and “password”. This worked until 5/31/2020.
I saw that some mentioned this now needs to be first letter in upper case.
I modified my function node to the following:
/* old used lowercase
msg.payload = {
"username" : flow.get("myq.payload.username"),
"password" : flow.get("myq.payload.password")
}
*/
msg.payload = {
"Username" : flow.get("myq.payload.username"),
"Password" : flow.get("myq.payload.password")
}
msg.headers = {
ContentType : "application/json",
Accept : "application/json",
MyQApplicationId : "Vj8pQggXLhLy0WHahglCD4N1nAkkXQtGYpq2HrHD7H1nvmbT55KqtN6RSF4ILB/i",
Culture : "en"
}
return msg;
And it works again.
I ran the example code in the pymyq
repository (https://github.com/arraylabs/pymyq/blob/d552aca083c33539dca31a08f151984232f58e9f/example.py) and was able to easily connect to my garage door opener and open/close the door. So the pymyq
module still works against the MyQ API. Must be a problem with the MyQ Component in HA.