myQ Authentication Issues, OAuth, 429

[networkneil]

Describe The Problem:
Updated to the latest version the the plugin. homebridge-myq v3.4.2 . Same issue on homebridge-myq v3.4.1

To Reproduce:
Update to latest version, restart the Homebridge.

Logs:

[10/12/2023, 4:34:11 PM] [myQ] myQ API: Unable to access the OAuth authorization endpoint.
[10/12/2023, 4:36:11 PM] [myQ] myQ API: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. Retrying the API call.
[10/12/2023, 4:36:11 PM] [myQ] myQ API: Switching to myQ cloud region: east.
[10/12/2023, 4:36:11 PM] [myQ] myQ API: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. Retrying the API call.
[10/12/2023, 4:36:11 PM] [myQ] myQ API: Switching to myQ cloud region: west.
[10/12/2023, 4:36:11 PM] [myQ] myQ API: Temporary myQ API server-side issues encountered: 429 - Too Many Requests. Retrying the API call.
[10/12/2023, 4:36:11 PM] [myQ] myQ API: Switching to myQ cloud region: auto.

Homebridge Configuration:

    {
        "email": "REDACTED",
        "password": "REDACTED",
        "name": "myQ",
        "options": [
            "Enable.Opener.OccupancySensor",
            "Enable.Opener.OccupancySensor.Duration.300",
            "Enable.Opener.BatteryInfo"
        ],
        "refreshInterval": 12,
        "activeRefreshInterval": 3,
        "activeRefreshDuration": 300,
        "debug": true,
        "_bridge": {
            "username": "REDACTED",
            "port": 53898
        },
        "platform": "myQ"
    },

Screenshots:

Environment:

• Homebridge Version: v1.6.1
• Node Version: v18.18.1
• Homebridge-myQ Plugin Version: homebridge-myq v3.4.2
• Apple Device and iOS / macOS / iPadOS / tvOS Version: iPhone15ProMax-iOS17.0.3
• Operating System and OS Version: orangepi5-Ubuntu Jammy Jellyfish (22.04.2 LTS)

[nyjklein]

Same "429" error here even after trying the latest update today.

[hjdhjd]

TL;DR: You’ll need to wait 60-90 minutes, they’ll clear up. Enjoy.

More context: it seems myQ is really trying hard to meaningfully cutoff access for third party apps that are trying to emulate the actual app itself. One way they’re making it more painful is that if you try to authenticate without being “just so”….and you don’t look exactly like the official myQ app in some esoteric ways…they’ve taken the understandable (if you wanted to prevent this type of thing) step of enforcing a lockout pretty quickly. That’s what these 429 errors are. After 2-4 attempts without looking exactly like the real-deal app, it locks you out for 60-90 minutes. It made updating this plugin and the API I maintain all the more fun because each time I wasn’t perfect…well, I was in the penalty box a lot. 😄

Hope the context helps.

[hjdhjd]

Locking this to avoid the million “+1s”…