-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
Myq down again #36643
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
Comments
@nikiyao please make sure to fill out the issue template that gets presented when you create a new issue. Also you may want to update your error message and remove identifiable information too. |
myq documentation |
Hmm I didn't see an issue template this time although I have seen it before |
Are you on HA 0.110.5 and later too? because this exact error was fixed there. |
@dshokouhi I'm on 0.111.0 this just started within the past hour though |
@dshokouhi did my best to copy the template from elsewhere |
Same issue, updated to 0.111.0. Was working with 0.110.5.
|
I literally applied this fix several hours ago, only for it to break again during a reset a few moments ago. |
Same, updated to 0.111.0 and it broke again. Worked earlier today but broke within the last few hours. |
It seems that the Works manually:
Throws SSL error (curl: (56) OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 104):
I tried reverting the EDIT:
And it's working again in HA as well. |
Was the fix cherry picked for 0.110.5 and not added to 0.111.0? |
+1 - fresh install, worked 4 hours ago, just stopped working. |
0.110.5 stopped working Traceback (most recent call last): |
I can confirm that the following user-agent that I found on a Homebridge MyQ plugin also works.
Might be useful to include this as part of the configuration. Can we have an override in the configuration for user-agent. Maybe something like this (YAML):
|
No it’s there, I think myq broke us again. |
Which file needs to be edited to fix? I've gone into..
I've had a look in |
api.py |
I don't seem to have that file
edit: I removed the integration to re-install to try and fix, would that be why? |
@Kanga-Who I have the same content you listed. No api.py |
Need to look here: |
Perfect. Can confirm the fix.
|
Fix worked for me as well on 111.0. Hope this isn’t a new cat and mouse game. |
67E6
Just upgraded to 111.0 from 110.5 and this fix is working for me as well. |
Fix is working on 0.110.7 as well. |
Worked for me on 111.0 too. Thanks. |
Anyone working on a pull request for this issue? |
Would anyone mind doing a step by step breakdown of how to apply this fix? |
@nikiyao : cd /usr/local/lib/python3.7/site-packages/pymyq |
PR is here |
Does anyone have reason to believe MyQ is intentionally targeting HomeAssistant with this user-agent issue? |
This integration uses an undocumented and unsupported API so constantly breaking should be expected. |
They’re very stingy with their API. Does anyone know of any custom firmware or hacks to remove the cloud completely? Short of adding a relay in between the button and opener and adding a tilt sensor. Any way to spoof the chamberlain servers to control locally, etc. |
I believe they are trying to break integrations not using their approved integrations. They have always used a pay to play model, even with IFTTT, which I think is the wrong approach in today's age of IoT. I get it that there are expenses in running a cloud infrastructure, and a garage door opener is a one time purchase. Trying to reverse engineer the door opener to try and get it to connect to your system directly won't scale. I'm just down the street from their corporate office in Oakbrook -- One of these days I may stop in and see if I can talk to someone in software/business development and maybe some good may come out of it. We'll see.... |
Thanks to devinslick for posting the exact commands for the newbie's like me. I made the change as described step-by-step to api.py. One question, once the change is made to the file, what command do I need to use to save the edits and close the file back to the command prompt? I tried CTRL-V but my HA instance would no longer boot up so I am starting over with the program from scratch - not a huge loss, I am still experimenting with the program. Thanks, Glenn |
Hit Escape. Then colon, then w, then q |
I cannot install the package because of the aforementioned error. Pymyq is not located in /usr/local/lib/python3.7/site-packages/ because I can't install. The fix above seems to be there for people who had previous successful install. Any suggestions for those of us who cannot install it? |
@ifixrjs , Are you on 0.111.1? |
The fix is in 0.111.1, update and problem solved. |
Yes I am on 0.111.0. |
anyone else having this issue again..in 0.111.4? |
I am. I haven't confirmed whether the code is the problem again but my garage doors appear 'unavailable' in the overview screen meaning they are greyed out. The myq app works so I know it isn't a problem with the doors. Very frustrating. |
@romaneleven11 yes. It’s a new issue and should be fixed by 0.112.0 |
Yes, offline again today with 0.111.4. API must have changed again. |
PR to fix it is linked here #37100 |
Uh oh!
There was an error while loading. Please reload this page.
The problem
MyQ shows unavailable again, cannot setup integration
Environment
• Home Assistant Core release with the issue: 0.111.0
• Last working Home Assistant Core release (if known): 0.111.0
• Operating environment (Home Assistant/Supervised/Docker/venv): HA
• Integration causing this issue: MyQ
• Link to integration documentation on our website:
Problem-relevant configuration.yaml
Config FLow
Traceback/Error logs
The text was updated successfully, but these errors were encountered: