This is really poor on their part. After about 2 years their product, chamerline, has gone downhill.
Not really. They have no responsibility to the OSS community and they have every right to change their protocol. Given that HomeBridge works still, looks like the HA integration doesn’t quite follow their spec anyway.
Having said that, still sucks. As long as they aren’t intentionally breaking the community I think it’s fine.
As I mentioned before, it appears that in the IoX-PG3 universe of Universal Devices their MyQ Nodeserver (integration) still works. Someone much smarter than I am should try to understand why.
1 Like
I just installed two ratgdo devices (soldered the d1 mini lite on myself as I had two extra here)…after some confusion on my part and quick support I had both online (using ESPhome). Not only is there zero latency, but the additional functionality is impressive…way nicer than cloud. You won’t be disappointed! Cheers.
MyQ started working again for no particular reason, absolutely made no changes to HA so likely something fubar on the provider side (intentional or otherwise)
Whoa, after fighting this for days and trying patch after patch only to end up just ordering a couple ratgdo and ESP8266 D1 mini, I just checked mine and sure enough 3 hours ago mine just started working and showing stable constant connection. I could only have a connection for about 20 minutes then I would get 429’d and have to disable the integration for an hour then it would reconnect.
I’m still going to keep the ratgdo when they come in because it’s 100% local and instantaneous control and also provides fine position control of my doors. This will prevent anymore future headaches with MyQ cloud service.
I am still getting the 403 error. I had applied the original fix which stopped working 5 days ago. I did go in and delete the folder the fix created. I saw yesterday that it had started working for people but it had not for me. I deleted the integration and reinstalled. Still no luck.
Anything else that I can try?
I really don’t know. The patch I’m using is the newer Python-MyQ and the “feature/timeout” branch from about 3 days ago. I had to install it using pip inside my HA Container, followed by a restart.
Can you send me the link for that? I am running HA OS baremetal. Should it still work for that?
The patch I’m using is linked further up in the thread MyQ 403 Auth Errors after 2023.9 - #29 by drothenberger
I don’t know HAOS, so someone else will need to chime in how to install the pymyq replacement.
As for the alternative local control ratgdo boards, that too is linked further up.
Same for me, it just started working again last night all of the sudden.
Can confirm that the integration started working for me this morning without doing anything as well.
When you said that you did nothing, does that mean that you didn’t try to patch any of the fixes since it stopped working a few days back?
My is now working but I had to apply the user agent patch.
which user patch?
This patch…
docker exec -it homeassistant bashcd /usr/local/lib/python3.11/site-packages/pymyq/cp request.py request_bup.pyvi request.py-
ito enter insert mode - Modify line 34
- Was
self._useragent = None - Is
self._useragent = str("anytexthere")
- Was
-
Esckey to exit insert mode -
:w+ enter to write the changes -
:x+ enter to exit VI - Restart Home Assistant
ok. thanks. I’m not on Docker so the first line throws an error. I will see what I can figure out
I had previously applied the original UA workaround for the 443 error but that was a few weeks ago. I didn’t reapply or make any changes after the most recent outage.
I had applied the original UA patch which worked then stopped after my upgrade of HA core. I re-appled the patch in the following way:
- Via the Samba addon navigate to the “Config” folder and deleted the folder “pymyq”
- Re-boot HA
- Download the new patch GitHub - Python-MyQ/Python-MyQ
- Unzip the contents
- Upload the “pymyq” to the “Config” folder in HA
- Re-boot HA
Above worked for me but who knows for how long
Shocking this is still down.