I posted the same over here: Anyone else having issues with MYQ? - #80 by Dorque
You need to modify a line in the api.py file:
from
DEFAULT_USER_AGENT = "myQ/14041 CFNetwork/1107.1 Darwin/19.0.0"
to
DEFAULT_USER_AGENT = "myQ/19569 CFNetwork/1107.1 Darwin/19.0.0"
I’m not seeing the file in the path provided, strange.
If you are using Docker, these instructions will help you:
If you’re not using Docker, I’m not sure where the file should be. Hoping someone chimes in to help.
Thanks for the update. I saw on github that there was another change to make as well to the file “pymyq/version.py.”
Change
version = ‘2.0.4’
to
version = ‘2.0.5’
Made both changes and restarted Home Assistant and all is working now
Rich, could you shed some light as to the full directory structure where the this particular ‘version.py’ file resides?
Thank you
I wouldn’t touch the version file. As this is just a pull request, the final state of version 2.0.5 may contain additional changes. Once the official 2.0.5 version is released, there is a chance your pymyq won’t update because it detects itself as already 2.0.5.
If this is the only change for version 2.0.5, then you will be fine, but I wouldn’t take the chance.
got it thanks!
Thanks for the explanation. Could be helpful. 
since few days I get the following error when trying to load Myq:
Error setting up entry me@mydomain for myq
Eveything was working well since many years. The Api stop from time to time but soon a fx is posted but this time it’s a different error.
Anybody have this. I’m on Hass.io Home Assistant 0.111.4
it’s an ongoing issue and if you search, you’ll find posts of others having the same issue and how to resolve it. requires updating a specific file or two for MyQ.
Yes the fix was done in HA 0.111.1, I’m on HA 0.111.4. It was working about a week ago.
there have been 2 or 3 additional fixes since then.
Back on track with HA 0.112. Thank you
Constant issues with this and its getting really annoying. Is this a HA issue or is MyQ causing it?
Anyway, was working with 0.112.3 update. I have an automation that alerts me when my garage isn’t closed while I’m sleeping and it went off 4 times last night bc the state went to unavailable. Logs say its a username and password issue, but it have triple checked it and even changed it and still same error. Am I alone or is this system having issues again already for others as well?
My two door operators went unavailable at different times last night between 1:00 and 2:20 EST. They’ve been online and working fine since then. 
MyQ changes their API which causes this integration to break. The API is an undocumented API so it is expected that errors will happen and things will break.
Is there another way to modify the password for MyQ? I am still getting an error that my username and password are incorrect. Because I got that error I changed my password to see if it would help and I updated it in my configuration.yamal. Even if I comment out the whole cover section and reboot I still get the same error. Makes me think this information is still stored somewhere and it’s trying to connect to it still. I know a lot of stuff has been moved to the UI over the last bunch on updates, but I can’t seem to see anywhere else to change this or to try to reset it.
the MyQ component recently moved to UI configuration. It should show up on the integrations page where you can change your username/password. You might have to just remove it and re-add the integration with a reboot or two in there.