ditto… not working
Me too.
I wonder, do not API manufacturers have a desire to make their stuff backward compatible? I’d understand if it was a private API, which only they control. But if you’re making it public, then you’re being dopey to just go and change it with no notice to other integrators or the public.
Interesting thing for me was I was getting those errors for a day or so, at least, before the lovelace card broke. And, interestingly, the iOS app didn’t change, and still works.
Ooh…here’s something interesting: The app has the following notice when you go to help -> support, it says “We are working on improving your online experience. Portions of our site will be down for scheduled maintenance on Saturday October 19th 2019 through Sunday October 20th, 2019. We appologize for any inconvenience.”
So, maybe the app is (will be) broken too! 
Cheers,
Ambi
Me too! Hope it comes back soon without to much work!
HA is not a partner of MyQ. Someone reverse engineered the API to make it work. The current hack uses api v4, the app does and has used v5 for a while now. They have sunset the v4 api now which causes this issue. So we need to update our hacked version to use v5. This is just part of using an unofficial api.
This is the current github issue: https://github.com/home-assistant/home-assistant/issues/27762
Please, help take a look at this if you have any insight.
1 Like
We need to add a new alert in the home-assistant website https://alerts.home-assistant.io/
As of Sunday 10/20/2019 4:45 pm, the alert is not there.
Update:
I have created an alert request here: https://github.com/home-assistant/alerts.home-assistant.io/pull/30
It is failing checks for some reason.
1 Like
This is now fixed in 0.100.3 https://www.home-assistant.io/blog/2019/10/10/release-100/#release-01003---october-21
2 Likes
The problem persists on 0.100.3
No for me. It was broken before, updated and it works. Look to make sure it didn’t create a new instance. It created a cover.garage_door_2 for me.
3 Likes
Works for me now too. It created the same as Michael listed above - a new cover entity.
1 Like
Thanks this saved me a lot of troubleshooting
1 Like
Ditto. Thanks!
Neither cover entity is being created in my case i.e.(cover.garage_door or cover.garage_door2).
Have rebooted HA several times to no avail (no cover domain/entity is appearing) in States.
Tue Oct 22 2019 12:49:14 GMT-0500 (Central Daylight Time)
There was an error while logging in: 12:49:02.447722 Client Error while requesting data from api/v4/User/Validate: 400, message=‘Bad Request’, url='https://myqexternal.myqdevice.com/api/v4/User/Validate
Connection lost. Reconnecting…
Any suggestions…
Did you update HA to 100.3?
From the error it appears you have not updated.
Check you version.
DeadEnd
Running 0.100.3 the issue persists. Any other suggestions?
Home Assistant
0.100.3
Path to configuration.yaml: /config
Developed by a bunch of awesome people.
Published under the Apache 2.0 license
Source: server — frontend-ui
Built using Python 3, Polymer, Icons by Google and MaterialDesignIcons.com.
Frontend version: 20191002.2 - latest
They changed their API from V4 to V5, no one’s is working right now
They fixed it, everyone’s working again. Did you read this thread? It talks about how they fixed it.
Yes, @wellsi posted a link advising that HA had been updated to 0.100.3 and has the fix implemented. The issue is apparently related to their API being modified.
The issue I have having followed Ian’s suggestion with the HA update, I’m still getting the error in my logs referring to API rejecting the GET request (my previous post).
Any help would be appreciated, thank you!!
The “/v4” in your error clearly indicates your installation has not been upgraded. If it were, HA would have updated the pymyq module to 2.0.0 which supports the V5 api. try restarting or rebooting. If you have access to your python environment supporting your HA installation, make sure you have pymyq 2.0.0 (HA should automatically bump it)
$ pip list |grep pymyq
pymyq 2.0.0