search

hjdhjd / homebridge-myq

:car: myQ Liftmaster and Chamberlain Plugin for Homebridge https://github.com/nfarina/homebridge
Other
568 stars 43 forks source link

API Login Failures #1117

Closed dashdriverdan closed 9 months ago

dashdriverdan commented 9 months ago

Describe The Problem: Since about 1700 UTC yesterday Homebridge-myq has been unable to log in, producing a variety of errors. HomeAssistant's MyQ implementation failed almost simultaneously.

https://github.com/home-assistant/core/issues/101763

To Reproduce: Alternatively: wait, or restart Homebridge.

Logs: [myQ] myQ API error: Invalid myQ credentials given: Check your username and password. If they are correct, the myQ API may be experiencing temporary issues. [myQ] myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests.

Homebridge Configuration:

"platforms": [
        {
            "name": "myQ",
            "platform": "myQ",
            "email": "redacted@redacted",
            "password": "redacted"
        }
    ]

Screenshots:

Environment:

dreagleeyes commented 9 months ago

I am seeing this also

hjdhjd commented 9 months ago

Yep I’m seeing it too…that said: while I am sure this is well intentioned: please do not open these issues related to API failures. As documentation they will happen on occasion…sometimes for hours or a day or so. If there’s a long-standing persistent problem that’s lasting several days at a time, then feel free to.

I use this plugin daily as well…I see the issues too. When there’s something that’s addressable from my end versus the myQ API end, I will.

Thanks.

shadowpuck99 commented 9 months ago

i realize the documentation around API failures - but, given the issues MyQ has been having lately in Home Assistant - it seemed reasonable to open this issue. Is it possible for the MyQ app to work perfectly fine and the API to not work? Wouldn't that point to something that might need to be changed in the integration?

I realize this is now closed - but, it's a legit question I have about this. Thank you for any time/assistance/feedback.

haywiremk commented 9 months ago

i realize the documentation around API failures - but, given the issues MyQ has been having lately in Home Assistant - it seemed reasonable to open this issue. Is it possible for the MyQ app to work perfectly fine and the API to not work? Wouldn't that point to something that might need to be changed in the integration?

I realize this is now closed - but, it's a legit question I have about this. Thank you for any time/assistance/feedback.

Agreed. Both HomeKit and Home Assistant MyQ are dead while the MyQ app using the API is working. This is clearly something that will need addresses as MyQ is clearly changing the API and it is blocking anything but the official application. Not sure why this was closed.

For Home Assistant the issue is here and they are actively working on a fix vs closing tickets.: https://github.com/home-assistant/core/issues/101763

Time to look for other options and toss the MyQ in the trash.

hjdhjd commented 9 months ago

There is no evidence that myQ has changed the API - please don’t come on the forums that I manage and curate and make declarative statements without meaningful technical evidence beyond “this works and that doesn’t”. That isn’t what is happening here, and this type of speculation, while I’m sure well-intentioned, is unhelpful and creates more confusion.

The issues here - for a number of years now - have been largely infrastructure-based, not API-based. To an end user the issues may be a distinction without a difference, but they matter. 😄

haywiremk commented 9 months ago

There is no evidence that myQ has changed the API - please don’t come on the forums that I manage and curate and make declarative statements without meaningful technical evidence beyond “this works and that doesn’t”. That isn’t what is happening here, and this type of speculation, while I’m sure well-intentioned, is unhelpful and creates more confusion.

https://github.com/Python-MyQ/Python-MyQ/pull/22

There is a fix for this issue and they have applied it to the HA code. There are clear changes going on to the MyQ API. Not try to hijack but there is a pretty consistent API issue across all platforms and code that is being updated elsewhere.

hjdhjd commented 9 months ago

That’s not an API issue, it’s a suspected new OAuth forwarding gateway issue/quirk that may or may not be the underlying culprit. I’ll also remind folks that a few weeks ago, when another round of issues came up, some suspected there may be a new user agent requirement in a very similar circumstance, also in the HA community, and ultimately, as it often tends to be the case, the issue is an underlying myQ infrastructure issue.

I know folks are well-intentioned here, but let’s see what some time brings. This isn’t my first rodeo with the API. 😄

github-actions[bot] commented 9 months ago

This issue is locked to prevent necroposting on closed issues. Please create a new issue for related support requests, bug reports, or feature suggestions.