Yeah, mine will beep and flash for about 10 seconds before the door starts closing. Safety reasons. First time I experienced it I almost shit myself. haha
Wow, that’s insane, good to know its supposed to do that though. I was freaking out, thought I somehow triggered my alarm system or something. Was like OMG CLOSE IT WHATS HAPPENING
So I just got an email from MyQ support indicating I was using an “older” version of the smartphone app that would no longer be compatible after 10/31. Since my mobile devices are all up-to-date, I suspect this email is referring to the home-assistant script…
Anyone else get an email like this?
I have not gotten any emails yet. looks like we are using the app id from their API… I will keep an eye out.
http://docs.unofficialliftmastermyq.apiary.io/#introduction/constant-values
Getting “Unable to find platform cover.myq”. Any ideas? I have HA installed via docker and i exec’d into docker and created the custom_components/cover folder and placed the myq.py file there. So the path to it is “/usr/src/app/homeassistant/custom_components/cover”. “/usr/src/app/homeassistant” is home to the normal “components” folder.
Thanks
UPDATE: Figured it out. Basically needed to map the volume for docker to get the file correctly as adding it while exec’d in doesn’t work. Added “-v /home/user/home-assistant/custom_components:/usr/src/app/homeassistant/custom_components” to my docker run command. Then created the “cover” folder and added the myq.py file inside it, then restarted the container.
Got the same e-mail , any work arounds ?
Is it still working for you?
Mine still is, but the cutoff from the email was 10/31, so we’be got time yet
Looks like they may of pulled the trigger early, I rebooted Home Assistant this morning and it is hanging on boot with this:
Oct 20 11:48:23 server-ha hass[1143]: INFO:homeassistant.loader:Loaded cover.myq from custom_components.cover.myq
Oct 20 11:48:23 server-ha hass[1143]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): myqexternal.myqdevice.com
Oct 20 11:48:23 server-ha hass[1143]: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): myqexternal.myqdevice.com
Edit:
I edited the Myq.py and replaced the chamberlin APP_ID with this one from the smartthings app and it started working:
NWknvuBd7LoFHfXmKNMBcgajXtZEgKUh4V7WNzMidrpUUluDpVYVZx+xT4PCM5Kx
1 Like
From out of the blue I got this message 
“ERROR:homeassistant.components.cover:Error while setting up platform myq”
Any ideas ?
Just researching that. Mine did it as well
What could happen >? that new App ID is for what brand ???
It was mentioned that it is Chamberlain but no luck for me.
I have a chamberlain and it looks like mine is not working as well. I wonder if it goes through my wink hub will solve the problem.
i got it working by adding a user-agent to the http header.
Yep adding the user-agent worked for me as well. based on what I have read it seems like Chamberlain will stop at nothing to prevent third-party support.
Where at do I put user agent?
user agent ?
Can you provide more detail as to where you added a user agent? maybe a screenshot of the portion of the config (and which file) you modified to get up and running again?
All,
In the myq.py I added the following:
“headers={
‘User-Agent’: ‘Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.47 Safari/537.36’
}”
to all lines that had the requests.get or requests.put function. For example the first instance of requests.put is the following and I added the headers to it
login = requests.get(
'https://{host_uri}/{login_endpoint}'.format(
host_uri=self.brand[HOST_URI],
login_endpoint=self.LOGIN_ENDPOINT),
params=params,
headers={
'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.47 Safari/537.36'
})
I added it in 4 places. Also be sure the comma before “headers” is added.
Hope that helps!
1 Like