[APP][Cloud & Pro] SwitchBot (Release 2.0.87, Test 2.0.93)

[Haadeess]

Hi Adrian and everyone,

I have been reading through the discussions here about the SwitchBot locks, Matter support and especially the Keypad Vision / Vision Pro, as I am currently considering buying the new SwitchBot Lock Pro Matter Enabled together with the Keypad Vision Pro.

Before ordering it, I would like to clarify what is currently possible with Homey and whether some additional integration might now be possible.

The device I mean is specifically the new Lock Pro Matter Enabled / Smart Lock Pro WiFi, not the older Lock Pro. It has Wi-Fi built in and supports Matter over Wi-Fi directly, without requiring a SwitchBot Hub.

1. Lock Pro Matter Enabled via Matter

Has anyone already tested this exact new model directly with Homey Pro via Matter over Wi-Fi?

I would particularly like to know whether Homey exposes all three actions separately:

• Lock

• Unlock

• Unlatch / Open Door

I saw the earlier discussion that Homey itself supports Lock, Unlock and Unlatch for Matter locks, so it would be very interesting to know what the new SwitchBot actually exposes to Homey.

For European doors the distinction is very important: “unlock” should only unlock the deadbolt, while “unlatch/open” should also pull back the latch so that the door can actually be opened.

2. The new SwitchBot API looks more interesting now

I also noticed that the current official SwitchBot OpenAPI documentation contains a dedicated device type for the new Smart Lock Pro WiFi.

It now exposes status information such as:

• battery

• lockState

• doorState

• calibration state

• onlineStatus

and it officially supports these commands:

• lock

• unlock

• nightLatchUnlock

• deadbolt

nightLatchUnlock is explicitly described by SwitchBot as the EU night-latch unlock command.

Would it therefore be possible to add the new Smart Lock Pro WiFi / Lock Pro Matter Enabled as a supported device in the Homey SwitchBot app?

A hybrid setup could potentially be very useful:

Matter for reliable local basic control and status, while the SwitchBot app/API could provide additional functions that Matter does not expose.

3. Keypad Vision Pro – has the API situation changed?

I also found the discussion from January where you explained that the cloud API did not provide useful information for the Keypad Vision Pro and BLE was encrypted.

However, the current SwitchBot OpenAPI documentation now officially lists Keypad Vision Pro as a supported device.

It currently exposes, among other things:

• keyList

• createKey

• deleteKey

• permanent passcodes

• temporary passcodes

• one-time passcodes

• emergency passcodes

Could this make at least partial Vision Pro support possible in the Homey app now?

For example:

• Create a PIN from a Homey Flow

• Create a temporary guest PIN

• Create a one-time PIN

• Delete a PIN

• Possibly expose the existing PIN list

That alone would already be a very useful addition.

4. The feature I would really like: WHO unlocked the door and HOW

The ideal Homey trigger would be something like:

When the door is unlocked via Keypad Vision Pro →

• User: John

• Method: fingerprint / face / palm vein / PIN / NFC

This would allow automations such as:

• Disable the alarm when an authorised family member enters

• Differentiate entering through the outdoor keypad from unlocking from inside

• Presence detection per person

• Personalised notifications

• Turn on entrance lights only when someone enters from outside

I saw that essentially the same request has already been made here.

Unfortunately, as far as I can see, the current public SwitchBot API still does not expose an unlock event containing the user/key ID and authentication method, even though this information exists in the SwitchBot access log.

There is also a long-standing SwitchBot API request for exactly this functionality, including fingerprint/passcode/NFC identity, and another more recent request for the same information.

So I assume this part is still blocked by SwitchBot rather than Homey.

Do you know whether anything has changed internally, or whether SwitchBot has indicated that these keypad usage/access-log events may become available through the API?

5. Reliability / Matter versus Cloud

I also noticed the reports in this thread about delayed or missing SwitchBot webhooks, incorrect LOCKED/UNLOCKED/LATCHED events and occasional login/token problems.

That makes me think the best architecture for a door lock may actually be:

Matter over Wi-Fi → local Lock / Unlock / Unlatch

plus

SwitchBot Homey app/OpenAPI → advanced SwitchBot-specific functionality

rather than relying entirely on the cloud integration.

Would you consider that a sensible setup, or could having the same lock connected through Matter and the SwitchBot app simultaneously create problems?

I am very interested in this combination and will probably buy the Lock Pro Matter Enabled + Keypad Vision Pro. If support for the new model is something you would consider adding, I would also be happy to test it, provide device information, logs or API responses if that helps development.

Thanks for all the work you have already put into the SwitchBot Homey app.

[Daderu]

Changed the log settings, and will monitor it.

[JBV]

Hello !

I can confirm what appears to be exactly the same issue on another Homey Pro Early 2019.

I have 8 existing SwitchBot temperature/humidity BLE sensors. They all stopped updating at exactly the same time and are now frozen on their last values.

I tested both 2.0.87 and 2.0.90 TEST, including a full Homey power cycle, with no change.

The SwitchBot Statistics page reports No BLE devices registered, and the SwitchBot pairing wizard doesn’t discover the sensors.

However, Homey Developer Tools → BLE does receive them. For example, one sensor shows:

Address: d0:c8:41:46:27:82
RSSI: -67
Service Data: [{"uuid":"fd3d","data":"7700c7"}]
Manufacturer Data: 6909d0c8414627829a0206992e00

So this seems to confirm the same behaviour: Homey Early 2019 receives the BLE advertisement and its service/manufacturer data, but the SwitchBot app no longer processes it.

I would also be happy to test 2.0.82 without removing/re-pairing my existing devices if there is a safe way to downgrade (is it a good idea ?)

Thank you !

Report ID: 12719a50-ca56-4ece-af5b-f4fed9a87e0e

JB

[Sander_van_Acker]

Hi JBV and Adrian (and others),

I have exactly the same issues as JBV (see earlier post).

I installed v2.0.90 as requested.

There is an interesting change now: under Configure → Driver Support, all four of my SwitchBot temperature/humidity sensors are shown in green as already added to Homey and supported.

However, none of the four sensors provide any data in Homey. Temperature, humidity, battery and RSSI remain empty. All four sensors still work correctly in the official SwitchBot app.

I restarted the SwitchBot app after installing v2.0.90, but this made no difference.

There is one thing that may be particularly relevant:

Under the BLE statistics section it says:

“No BLE devices registered.”

So v2.0.90 appears to recognise all four existing devices and their drivers, but apparently no BLE devices are being registered by the app.

This seems especially interesting because, as mentioned before, Homey Developer Tools → BLE does detect the SwitchBot sensor and receives its BLE advertisement, for example:

RSSI: -67
Service Data: [{"uuid":"fd3d","data":"778064"}]
Manufacturer Data: 6909eb6b05464b28420a028c5c00

So the Homey Pro (Early 2019) itself can see the BLE advertisement, but the SwitchBot app reports that no BLE devices are registered.

Could this explain why none of the sensor values are being updated?

@Adrian: Please let me know if you would like me to send another diagnostic report or app log while running v2.0.90.

Thanks to everyone helping!

[Adrian_Rockall]

I have published a new test version that will hopefully fix some of the BLE issues. The is now an option in the App settings page under the BLE section to disable the new BLE Advertisement feature of Homey as that seems it can make lots of reports with missing service data and cause issue with polling. So, If you have problems, try switching that option off and then restart the app.

The app also now keeps a cache of BLE devices that is refreshed at start up and then once per minute. The Add device procedure then uses that cache instead of a snapshot of that point in time, so devices that are not always visible should be picked up more reliably.

[JBV]

2.0.91 seems to have fixed the BLE issue on Homey Pro Early 2019.

After updating to 2.0.91, all 8 of my SwitchBot BLE temperature/humidity sensors started reporting values again.

They had all stopped updating simultaneously, and neither restarting the app, rebooting/power-cycling Homey, nor updating to 2.0.90 TEST had fixed the issue.

I’ll keep monitoring them to make sure the updates remain stable, but so far 2.0.91 appears to have resolved the problem.

Thanks for the quick fix and your work on this!

[Sander_van_Acker]

Same here: all four Switchbot BLE sensors are working now! Thanks for your help Adrian!

[WeWillSee]

Since recent I constantly get following errors on my SwitchBot devices

Not sure what it means

Trying to get logs but it keeps timing out so can’t see logs.
Already tried to reauthenticate successfully to SwitchBot aswell as restarting app but keep getting this error. How can I solve this?

[Adrian_Rockall]

That error is a DNS lookup error. You could try restarting the app and if that fails try restarting Homey.

[Haadeess]

Hi Adrian,

I now have the SwitchBot Lock Pro Matter Enabled / Smart Lock Pro WiFi and the Keypad Vision Pro.

Could these two devices be added to the Homey SwitchBot app?

For the lock, the most useful functions would be:

• Lock
• Unlock
• Night Latch Unlock / Unlatch
• Door/lock state
• Jammed state
• Battery
• Online/offline

Especially for European doors, Unlock and Night Latch Unlock should stay separate.

For the Vision Pro, useful support would be:

• Battery/status
• Create/delete PINs
• Temporary/one-time PINs

If SwitchBot exposes it later, triggers for fingerprint / face / palm vein / PIN / NFC and user identity would be great too.

I can help test both devices and provide logs or device/API information if needed.

My setup: Lock Pro Matter Enabled + Keypad Vision Pro + Homey Pro.

[Adrian_Rockall]

Can you make sure you have the latest test version (2.0.91) installed and then open the app settings page. Selected the Driver Support tab and at the bottom where it has Unsupported devices, click on there and then OK the message box. That will send me just the information in need to add the support rather than me guessing the device type (the API document is not always correct).
Support might already be in that version as I have been adding support for new bits.

[Haadeess]

Thanks a lot for the quick response as well.

I’ve installed the latest test version and have now sent the Driver Support / Unsupported devices information.

Hopefully that gives you everything you need for the Lock Pro Matter Enabled and Keypad Vision Pro.

[Adrian_Rockall]

@Haadeess

SwitchBot Lock Pro Matter Enabled

I have pushed a new test version that supports the lock.
Unfortunately, there is not much I can do with the Vison Pro. the API doesn’t support battery level and Homey doesn’t really have any way to enter PIN’s etc.

[Haadeess]

Hi Adrian,

thank you very much again for the quick help and support.

Unfortunately, Homey still doesn’t find any new SwitchBot device.

Could this be because I don’t have a SwitchBot Hub? I specifically bought the Lock Pro Matter Enabled because I wanted to avoid adding another bridge/hub in the house.

I’ll try integrating the lock via Matter now.

Do you know which functions I would be missing when using Matter compared with the SwitchBot Homey app?

Thanks again for your help

[Adrian_Rockall]

I’m guessing as the device has WiFi it shouldn’t need a hub and it appears in your account as it was reported as an unsupported device.
If you look at the supported drivers tam again, is it still in the unsupported list?

[Haadeess]

Hi Adrian,

yes, it has changed now. The Lock Pro Matter Enabled (HUB) is shown under “Supported, but not added to Homey”.

However, when I try to add/pair it through the SwitchBot app in Homey, Homey still says “No new devices found” and nothing is listed for pairing.

So it looks like the driver now recognizes the device type, but the device still isn’t being offered during the actual pairing process.

I’ve attached screenshots showing both states.

Thanks again for looking into this.

[Adrian_Rockall]

And you are using this driver?

[Haadeess]

Yes, of course.

[Adrian_Rockall]

I think I found it. As we discussed, the Lock Pro WIFI doesn’t need a hub, but I forgot to tell the driver that.
I have published a new test version (2.0.93)

[Haadeess]

Hi Adrian,

good news: I can now successfully add the Lock Pro Matter Enabled to Homey.

Unfortunately, none of the commands seem to work yet. Lock, Unlock and the other controls do not trigger any action on the lock.

Also, no door/lock state updates are being received in Homey. The device is added and visible, but the status does not change when I manually lock/unlock the door or open/close it.

So at the moment it looks like both commands and state reporting are not working yet.

I’m happy to send diagnostics/logs or run any specific tests you need.

Thanks again for the quick support!