[APP][Cloud & Pro] SwitchBot (Release 2.0.96, Test 2.0.101)

Feel free to provide corrections for any texts as I have to rely on AI.

I have asked SwitchBot to fix the webhook as it only sends locked for both latched and locked at the moment. I have also found that webhook events can be very slow at times to the point where it can completely miss the unlock state.

I have also submitted a PR for the Dutch translations, maybe you missed it?

I am not able to log in to my SwitchBot account through the app settings in Homey pro? Any clue what the problem might be? I want to add my AI Hub, Hub Mini, lock ultra Max and Vision Pro.

I have published a new test version that fixes the Developer Token login method.

It seems there is an issue with the OAuth2 login at the moment, so the old token method is a workaround until SwitchBot can fix it.

Hi @Haadeess,

I hope you don’t mind me asking here. I saw your September posts about the SwitchBot Lock Pro Matter Enabled / Smart Lock Pro WiFi and thought you might be able to help.

I’m considering the same lock (W8102001) for Home Assistant, particularly for integration with an alarm system.

I found its official Matter certification from July 2025, which shows that user management was not supported at that time, although LockOperation events were declared.

Since you already own the lock, I was wondering:

  1. Which firmware version are you currently using?

  2. Are you using it through Matter directly, or through the SwitchBot integration?

  3. Have you noticed whether it reports how the door was unlocked (keypad, fingerprint, NFC, or manually)?

I’m particularly interested in whether newer firmware provides more detailed Matter events.

No need to run any additional tests — any information from your experience would already be very helpful.

Thanks for sharing your experience

V0.8

I use it directly through the SwitchBot API.

It doesn’t report that, just that it was unlocked / locked.

The lock doesn’t have any user management, but are you referring to the keypad?

Hi,

Of course, happy to share my experience! Thanks for reaching out.

Firmware:
The last firmware version I explicitly confirmed on my SwitchBot Lock Pro was V1.5-2.2.

Integration:
I’m using the lock through Matter with Homey, rather than Home Assistant. I also use the official SwitchBot app for configuration and diagnostics, together with the Keypad Vision Pro.

Through Matter, Homey currently exposes information such as:

  • Locked / unlocked status

  • Door open / closed status

  • Door fault status

  • Battery level

Unlock method / Matter events:
Unfortunately, I haven’t seen any information through Matter that identifies how the door was unlocked.

For example, I cannot currently distinguish between fingerprint, keypad, palm vein recognition, or manual unlocking based on the Matter information available in Homey.

That doesn’t necessarily mean the Lock Pro doesn’t generate more detailed Matter events internally. It may also depend on what the Matter controller exposes.

I therefore can’t confirm whether newer firmware provides additional LockOperation event details in Home Assistant.

One additional observation that may be relevant for your alarm system:

I’ve experienced intermittent problems with the Lock Pro’s built-in magnetic door sensor. Sometimes it remains stuck reporting “Open” even though the door is physically closed. This can happen while Bluetooth communication is still working normally.

I’m currently investigating this with SwitchBot support.

Because of this, I’ve installed an additional independent SONOFF door contact sensor in Homey and use it to cross-check the door status.

For an alarm system, I would personally recommend using a separate, reliable door contact sensor rather than relying exclusively on the Lock Pro’s built-in door detection.

Overall, Matter works for basic lock-state integration in my setup, but I wouldn’t currently rely on it to identify the exact unlocking method without further confirmation.

I hope this helps!

Best regards,
Haadeess

Hello all,

since last night I have a problem with the communication between the Homey Switchbot app and my devices. I sitched tot the latest test version (2.0.99) Here a latest log after another restart:

2026-11-15T07:37:13.623Z
!!! Authentication state at startup: legacy API token=present, secret=present, OAuth2 session=available.

  • 2026-11-15T07:37:19.874Z
    !!! Invalid response: Rate Limited (615 API calls)

  • 2026-11-15T07:37:20.094Z
    !!! HTTPS Error: 429:

  • 2026-11-15T07:37:20.097Z
    !!! Temperature getHubDeviceValues: HTTPS Error:

  • 2026-11-15T07:37:21.532Z
    !!! HTTPS Error: 429:

  • 2026-11-15T07:37:21.536Z
    !!! Temperature getHubDeviceValues: HTTPS Error:

  • 2026-11-15T07:37:23.379Z
    !!! HTTPS Error: 429:

  • 2026-11-15T07:37:23.382Z
    !!! Temperature getHubDeviceValues: HTTPS Error:

  • 2026-11-15T07:37:23.414Z
    !!! HTTPS Error: 429:

  • etc etc

    All devices are working OK, when I use them with the Cloud Switchbot app.

    I haven’t changed anything, so no new devices, no new flows. I have now installed the .99 test version and filled in the Token and key, butt this didn’t do the trick.

    I have restarted Homey, restarted the Switchbot app, used the repair funtion, switched of the switchbot app for 40 minutes and than activated it again, re-installed the switchbot app (did not remove the app by the way) nothing worked.

  • I have all the latest updates, versions, firmware.

    The setting I have works for a few years now, so what has changed so suddenly?

This one is the smoking gun. It could just be that SwitchBot resets its count at a different time or the server is having a bad day. Restarting Homey and repairing will just make the problem worse as those actions require a burst of extra API connections.

Have you connected your SwitchBot account to any other systems as the API limit is per account (not including the SwitchBot mobile app).

Hi Adrian, thx for your swift response! Appreciate it!

To answer your question: I did not do anything with my Switchbot account at all. That’s the point. I logged in again via the repair option, that;'s all. Last night 22.12, the Hubs I have reported being offline.

The Switchbot temp devices still report in Homey. It’s the Hubs that don’t respond.

Is that in the SwitchBot Mobile app?

The SwitchBot Mobile app will connect to all your devices via BLE if it can, so it will by-pass the hubs. So, if the hubs are offline then the Homey app won’t get any changes from the devices as they are required for the cloud (hub) connection.

They were indeed reported offline in the mobile app. However, when I couldn’t operate the devices in Homey, I switched tot the mobile app and luckily the hubs worked. I use them to operate devices for heating. The are not offline anymore.

I have checked and if the hubs were offline that could cause the quota to be used at 3 time the rate as the app sees that as an error and retries 3 times per call (6 time per curtain as it also does a status update). Maybe that could have caused the problem.

I have published a new test version (2.0.101) that treats an offline response as valid so it doesn’t retry it.

Hi Adrian, it works!

Thx a lot!