API error about homebridge-myq HOT 18 CLOSED

JFYI, pasting from a Reddit post, but someone contacted myQ and they said this:

"For the safety of our MYQ Customers we did disable the use of our MYQ app with non-authorized third party apps that do not have a partnership with us to be controlling our app."

Super helpful thanks. 😄

Will be working through this...stay tuned.

from homebridge-myq.

Looks like @nathangoodman submitted a pull request to address this: hjdhjd/myq#419.

from homebridge-myq.

v3.4.2 should do the trick for folks. Cheers.

from homebridge-myq.

For reference, this topic was raised (and apparently will soon be resolved) on HomeAssistant GitHub: home-assistant/core#101763

from homebridge-myq.

Does the fix that they discussed in the HA issue also work as a fix/update for the home bridge side of the myq plugin? Or what would we have to do to update our side with that fix?

from homebridge-myq.

from homebridge-myq.

I am seeing the same issue here. I moved away from the HA Plugin because it was becoming to unreliable and saw many suggestions to use the Homebridge MyQ plugin, so I spun HB back up and loaded the plugin - it was working for a couple of weeks until now. Any insight to resolving this would be much appreciated. Thanks!

from homebridge-myq.

Later in the post they discuss that the fix you listed stopped working. They seem to have fixed it and would apply the fix to a HA plugin, but how do we fix this on the homebridge side? I may be misunderstanding as well, I can tinker in a lot of code but what they are discussing seems slightly above my head...

from homebridge-myq.

Before moving back to the HB MyQ plugin I was doing some of these fixes/patches that were posted, but they would last maybe a few days up to a week then would fail again. When I started to do more digging it seemed like the HB MyQ Plugin was more reliable than the HA plugin - anyway, I guess Chamberlain really wants to shut these plugins down. What I don't get is they cancelled/discontinued the MyQ Homekit Bridge, so there really is no reliable/feasible way of getting their devices working in Homekit now, so why not let these plugins continue to function rather than continually break them?

from homebridge-myq.

JFYI, pasting from a Reddit post, but someone contacted myQ and they said this:

"For the safety of our MYQ Customers we did disable the use of our MYQ app with non-authorized third party apps that do not have a partnership with us to be controlling our app."

from homebridge-myq.

JFYI, pasting from a Reddit post, but someone contacted myQ and they said this:
"For the safety of our MYQ Customers we did disable the use of our MYQ app with non-authorized third party apps that do not have a partnership with us to be controlling our app."

Super helpful thanks. 😄

Will be working through this...stay tuned.

Here's the link:
https://www.reddit.com/r/homebridge/comments/175iig3/myq_login_failures/

from homebridge-myq.

In the mean time is there a way to turn off the authentication attempts short of disabling the plugin? All of the failed api attempts are making it harder for their app to authenticate inside my network.

from homebridge-myq.

Disable the child bridge, if that's how you've configured it, in the Homebridge webUI, or disable the plugin in the Homebridge webUI. That's it.

from homebridge-myq.

Thanks @hjdhjd. v3.4.2 did the trick for now, but I'm wondering for how long if they are starting to crack down on API access. They've discontinued their Homekit bridge, so what is the future plan? Anybody know if they are adding Matter support, so we can control myQ more natively from Homekit?

from homebridge-myq.

Still happens for me on v3.4.2... getting 429 errors. Do I need to disable the plugin for awhile?

from homebridge-myq.

Still happens for me on v3.4.2... getting 429 errors. Do I need to disable the plugin for awhile?

Mine did then when I was doing some testing. You may need to disable it for a while as it may have failed too many times. Mine did connect back up with the update, but then again it had been disabled for 12 hours. I don’t know how long you would need to but that’s just my experience.

TL;DR: Yes.

from homebridge-myq.

Still happens for me on v3.4.2... getting 429 errors. Do I need to disable the plugin for awhile?

Did you restart Homebridge after updating the plugin? I don't know how long mine was hammering the API, because I only noticed that something was wrong when my garage door didn't open around noon. After finding this issue I updated to v3.4.2 and restarted Homebridge and then it immediately connected and things have been fine since then.

from homebridge-myq.

You’ll need to wait 60-90 minutes if you’re seeing those errors. As I said on the Discord: myQ has significantly increased the penalty for not strictly complying with how they want you to communicate with the API. The result is a lockout for an hour or so…it’s made troubleshooting and evolving in this shifting landscape more challenging. Be patient. Wait. It will be fine in a bit. You can disable the plugin for an hour or so if it’s bugging you.

Locking this issue to avoid further necroposting.

from homebridge-myq.