hjdhjd / homebridge-myq

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

myQ API error: Forbidden API call. This error is typically due to an offline or unavailable myQ device. #1103

Closed TottiUno closed 10 months ago

TottiUno commented 10 months ago

Describe The Problem: myQ API error: Forbidden API call. This error is typically due to an offline or unavailable myQ device.

image

To Reproduce:

Logs:

Show the Homebridge logs here.
Remove any sensitive information.

Homebridge Configuration:

Show the relevant portion of your homebridge config.json here, if needed.
Remove any sensitive information.

Screenshots:

image

Environment:

TottiUno commented 10 months ago

Not able to login

zwoop commented 10 months ago

I'm seeing the same, and my login / password works fine in the MyQ app itself.

mweckmann commented 10 months ago

Same here. MYQ App works fine. I tried logging out and in with no success.

Log also shows: myQ API: Unable to access the OAuth authorization endpoint.

9zero8 commented 10 months ago

Same on my end. MYQ App works though.

razholio commented 10 months ago

Add me to the list. Auth verified.

Guy559 commented 10 months ago

Same. No longer working on Homebridge or Home Assistant. Receiving the following:

[9/8/2023, 6:49:13 PM] [myQ] myQ API error: Forbidden API call. This error is typically due to an offline or unavailable myQ device.

mdjhnson commented 10 months ago

I'm not sure if MyQ changed their cloud access. I can't access https://myq-cloud.com and there is a message about moving to mobile on https://www.mychamberlain.com/

image
schmdbrgr commented 10 months ago

Same issue.

phillipfoose commented 10 months ago

Same, I was on an older 2.3.x release and was seeing a separate error, and updating to latest and am seeing this now.

WheatGuy commented 10 months ago

Same for me.

shadowpuck99 commented 10 months ago

Same here. MyQ app works fine but doesn’t work in HomeKit. Same error.

btsubjectdata commented 10 months ago

I am getting this error too. [08/09/2023, 18:57:51] [homebridge-myq] myQ API error: Forbidden API call. This error is typically due to an offline or unavailable myQ device. [08/09/2023, 18:59:51] [homebridge-myq] myQ API error: Forbidden API call. This error is typically due to an offline or unavailable myQ device. [08/09/2023, 19:01:51] [homebridge-myq] myQ API error: Forbidden API call. This error is typically due to an offline or unavailable myQ device. [08/09/2023, 19:03:51] [homebridge-myq] myQ API error: Forbidden API call. This error is typically due to an offline or unavailable myQ device. [08/09/2023, 19:05:51] [homebridge-myq] myQ API error: Forbidden API call. This error is typically due to an offline or unavailable myQ device. [08/09/2023, 19:07:51] [homebridge-myq] myQ API error: Forbidden API call. This error is typically due to an offline or unavailable myQ device. [08/09/2023, 19:09:51] [homebridge-myq] myQ API error: Forbidden API call. This error is typically due to an offline or unavailable myQ device. [08/09/2023, 19:11:52] [homebridge-myq] myQ API error: Forbidden API call. This error is typically due to an offline or unavailable myQ device.

corey6058 commented 10 months ago

I can verify the same on my end. Same message in the logs about the API, but myQ app works perfectly fine.

mwilliams146 commented 10 months ago

Same here, same message in the logs about the API. MyQ App works just fine. Tried signing out and back in but no luck with authenticating again.

schmdbrgr commented 10 months ago

Specifying API region west or east seems to restore functionality. But causes issues with an endless spinning wheel for the settings dialog. Changing the setting back to the default “” via config file brings the API error back.

fraherjr90 commented 10 months ago

Getting the same. Reset password, nothing. MyQ app is working.

mdjhnson commented 10 months ago

Specifying API region west or east seems to restore functionality. But causes issues with an endless spinning wheel for the settings dialog. Changing the setting back to the default “” via config file brings the API error back.

Thanks @schmdbrgr. Setting the "myQ API Cloud Region" under "Advanced Settings" seems to have resolved my issues.

image
jdmtv001 commented 10 months ago

I can confirm I had the same issue until I made the change to east in the advanced settings. For now it is working as it should.

WheatGuy commented 10 months ago

Specifying API region west or east seems to restore functionality. But causes issues with an endless spinning wheel for the settings dialog. Changing the setting back to the default “” via config file brings the API error back.

Thanks @schmdbrgr. Setting the "myQ API Cloud Region" under "Advanced Settings" seems to have resolved my issues.

image

I set my region to west in the plugin settings as well. Working normal as usual now, no lag issues/spinning wheel.

corey6058 commented 10 months ago

Specifying the server location to east or west restored functionality for me. Thanks for the tip.

uurf commented 10 months ago

Specifying the server location to east or west restored functionality for me. Thanks for the tip.

same for me. I'm in Pittsburgh, so specifying east restored functionality.

hjdhjd commented 10 months ago

Please stop opening issues related to this. There are multiple other already closed issues on this topic.

To be clear for others who come across this: myQ API connectivity issues happen, and they are not issues with this plugin, but rather with the myQ API endpoints. Opening issues related to this topic will be summarily closed. I will provide no support for transient (and yes, these are all transient) API issues. All issues related to this topic will be closed. If you’d like to discuss in a community setting, you are welcome to use the Homebridge Discord.