429 - Too Many Requests

[sir-captainmorgan21]

Describe The Problem: I noticed my commands from HomeKit to open/close the garage stopped working, so I checked my MyQ plugin and saw that there was an update available. I've updated it, and in the logs I see a constant output of the following error:

myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.

To Reproduce:

1. Install the plugin
2. Run it on a bridge
3. Observe logs

Logs:

myQ API error: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. This typically indicates a myQ API lockout for a 60-90 minute period before resuming API connectivity.

Homebridge Configuration:

{
    "platform": "myQ",
    "email": "email",
    "password": "password"
}

Screenshots: N/A

Environment:

• Homebridge Version: 1.6.0
• Node Version: 16.19.1
• Homebridge-myQ Plugin Version: 3.4.3
• Apple Device and iOS / macOS / iPadOS / tvOS Version: IPhone IOS 17
• Operating System and OS Version: Not sure what in relation to? Im using the Hoobs box

[Wheemer]

Thank you for reporting properly.

I am experiencing the exact same thing.

[cooperz]

I tried disabling the plugin overnight and just re-enabling this morning. It's still the same. They must have changed something again in the API / URL formatting.

[anderfrank]

I tried disabling the plugin overnight and just re-enabling this morning. It's still the same. They must have changed something again in the API / URL formatting.

Tried the same thing here, got same result.

[hjdhjd]

Thanks for the report. This has been asked and answered - I’ve got nothing further to provide here. If you have multiple myQ integrations, you might want to disable them all for a few hours given they may be locking themselves out as well. The plugin works for the majority of folks - but I recognize you might be having issues. There is nothing more to be said or done here. I will be locking this thread as well, but leaving it pinned for folks.

My advice:

Disable any/all myQ integrations whether it’s mine or any other for several hours if you’re having an issue. If you’re unsure: change your myQ password to definitively ensure you aren’t inadvertently generating them. Try again the next day with HBMQ (homebridge-myq) and see if things work.

Beyond that, there’s not much to do here - we do the best we can with the API we have. It’s unsatisfying, but that’s the way it is in myQ land.

Also, a more general note to others who come across this: understand that I am one person providing something out of my free time and supporting a community I love. Remarks about how “aggressive” the support template is, or how I choose to provide support for something everyone benefits from is impolite to say the least. Please respect how I choose to provide support. You’re not the one dealing with the support deluge requests for something everyone seems to feel an entitlement toward. 😄 Please have some empathy and respect.

This is not a forum for discussion, this is a specific support channel for specific issues. If you’d like to do that, the Discord myQ channel is the place to go…there’s a lot of good dialog, and we’re a reasonably active community.

[hjdhjd]

@BrendanGrant and @ryanlindsey - while well-intentioned, I am sure, I deleted your remarks because they will continue to cause confusion as to the nature of the myQ issues. I’ve stated these elsewhere, but once more:

1. This is not a rate limiting issue, in the traditional sense, though it may appear that way at a glance. Look at the links below for more context.
2. No, HBMQ does not poll once per second in a regular state and never has.
3. This isn’t about “staying off the radar”. This is an intentional move by myQ to further constrain access.

More context for the curious: https://github.com/hjdhjd/homebridge-myq/issues/1126#issuecomment-1763476073 https://github.com/hjdhjd/homebridge-myq/issues/1125#issuecomment-1763475185