core-ssh:~# docker exec -it homeassistant /bin/bash
-bash: docker: command not found
core-ssh:~#
#sadtrombone
1 Like
Thanks for your explanation! Can you be more explicit regarding the directory path to the appropriate manifest.json file, assuming a hassio installation?
Thanks again!
Update: I had a go at the suggestion by @bachya and 
No adverse errors seen on HA restart. Thank you all!!
1 Like
Iām not sure if my way was āokayā or a āterrible ideaā but I got it working on hassio.
The link above is much easier than the way I went, but I sshāed into my ubuntu server, used āfind / -name pymyqā to find the name of the right docker container. I navigated to the /var/lib/docker/overlay2 container, and into the pymyq library and made this change to the api.py file and it started working.
I didnt mess with the manifest file.
thatās what i did as wellā¦ iām using a venv install though. but no problems so far
1 Like
I did the same just now and working again. Should work assuming the next upgrade has this change otherwise it will get overwritten and need to be hacked again.
1 Like
Yep. This fix works for me as well. Thank you.
1 Like
This fixed mine also.
0.101.1 incorporates all the latest fixes. Itās published on the website just not in pypi yet. should be there tonight or tomorrow.
Hi There,
Another way to do this is to add a custom component.
Using the same github source you mentioned, you download the code and then I used Cloud9 IDE, itās a component you can add to HA in the add-on-store.
If you donāt have the Custom_components folder, create that first then drop in the contents of the pymyq, restart HA and it loads the custom component and works perfectly. After the change is implemented in a future general build of HA, I move the component to the āPrevious Custom Componentsā folder.
Hope if helps, I know I like finding ways to do things differently. 
Thanks, this fixed it. Went to the Entity Registry, searched for ācoverā and found one that was unavailable. Deleted that one, and renamed the _2 to the name used throughout my HASS instance and all is now good!
Yes but this works for HA and not Hassio, right?
Since mine is in a docker container, the custom component isnāt in my HA folder, so I use VSCode which can access my whole server.
It should work in hassio. Youāll need to add a custom_components directory.
So is anyone else having problems? It appears that myq is not connecting to my Gate or Garage Controller anymore as of 11/16/19?
Iām using the smart garage hub and itās working fine.
HA and MyQ are connecting and operating properly in my system today.
Thanks @HeffeD, I rebooted HA and all of a sudden itās working againā¦ itās the most finicky of all the integrations I have with HA.
Iām thinking since I need it to work consistently, Iām going to just connect MyQ to Google Assistant, and change my expose for covers in Google Assistant to false. That way it will stay in HA, and I can use it there, but when I ask Google to open the Gate or the Garage it should just work every time without issue.
Anyone considered that?
Yes, you could do that. But youāll miss out on the ability to automate your MyQ covers.
As long as they havenāt changed the API again, mine always works. Iāve never had it just drop connection to HA requiring a restart/reboot to fix it. Is your WiFi signal solid in your garage and (Iām assuming) outside for the gate?
Apparently the sanctioned integration between Chamberland and Google requires a subscription at $1 a month and canāt open/close the gates or garage doors. Iāll check all my configuration again thank you for the help.
The subscription is currently free. Their partners page say you can open garage doors with Google Assistant. If it can open those, I donāt know why it wouldnāt also open gates.
I got the free one, but not sure when they would start charging for something that arguably should be free. But to clarify my last post, you cannot āOPENā a Chamberland Garage or Gate opener. Google can tell you itās open, it can tell you itās closed, it can close it, but no opening.
There are a couple threads of people frustrated about finding out the same thing
https://support.google.com/googlenest/thread/15631501?hl=en
By using the HA integration you create a pin and every time I ask Google with HA, it asks me for the pin, then it opens the covers, but with the Chamberland to Google direct integration you can only close, which totally sucks.
Unless you see somewhere else that this was resolved, I ran into the same issue as the people in the above mentioned thread.
Figured I would share that here, always good to put as much knowledge into these threads as possible 