-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
myq now requires a user agent #39
myq now requires a user agent #39
Conversation
Confirm this fixes today's issue for me - thanks! |
I updated via pip and I'm still having the same issue as before. Any ideas?
|
There hasn’t been a new release yet so the change has to be patched in manually at this time |
I apologize for the stupidity of this, but I am new to Hassio. What's the best way to manually patch this? Thanks in advance. |
I should also mention I am running this from a pi. |
Just pushed new version (2.0.3) to pypi. Will someone be able to update Home Assistant for new version? |
Thanks @ehendrix23 PR is here home-assistant/core#36469 |
Just confirming that this fix is working perfectly. Thanks so much @bdraco ! @NickNothom - I also found that after installing the update via pip install pymyq==2.0.3 and restarting HA, that it didn't work. This is because HA's myq current requirements forces it to use the 2.0.2 version, so the update gets replaced during the restart. If you can't wait for the next HA release, then probably the easiest means to obtain the fix is to navigate to /usr/src/homeassistant/homeassistant/components/myq and edit the manifest.json file to change the version requirements from 2.0.2 to 2.0.3, then restart. That will pull the updated pymyq code automatically. (Home Assistant users will need to ssh, then run docker exec -t -i homeassistant /bin/bash in order to access the normally inaccessible HA python code). |
Fixes #38