ok, but it’s possible to show the icon status also for the lock ultra?
If you update to the test version, it will be on there.
Here is the latest update: the lock installed via Matter, as well as the hub, are operational again.
I am now once again receiving the information correctly from both lock states (locked and unlocked).
Why it stopped working for a week, I have no idea. Maybe Homey did something, since they are the ones managing Matter.
However, in your SwitchBot application, I can confirm that these two states are still not reporting any information. So I believe there is indeed an issue on your side.
I don’t know if you are able to install the lock using Matter on your end and check how the information from both states is reported, in order to adapt your application accordingly.
Please let me know if you find something that I can test on my side.
And by the way, using Matter makes the information update instantly, which is very appreciable.
i’ve the 2.0.61 beta version, but I don’t see the lock
@dudu_95 I think SwitchBot are having issues with the Lock at the moment. I removed the lock from my account and added it again and now I can only control it over BLE. If I switch off BLE on my phone I can’t control it, even via the SwitchBot mobile app and I am not getting any notifications at all. SwitchBot informed me a couple of weeks ago that they were updating the encryption for many devices, including the lock. Maybe my hubs and lock are out of sync now.
@Giovanni4312 Do you have a hub? Have you added the lock to your SwitchBot account?
The same thing happened to me yesterday: I no longer had remote access through the application.
I unplugged the hub for 2 minutes, then plugged it back in, and everything returned to normal.
Yes, I have a Switchbot hub3 and I imported the devices. It’s strange because the Lock Pro 31 is not connected to the hub, but I only use it with Bluetooth and it has the lock icon. The Lock Ultra 94 is connected to the hub and does not show the lock icon.
The icon should appear if you have version 2.0.61 installed and that has just gone live.
OK, I might have found the problem. Can you try the new test version
@dudu_95 Could you also try the new test version to see if it fixes the Flow card issue?
1 Like
With the test version, both cards now send the information immediately, but there is a bug.
When I unlock the door, I receive the door unlocked status, then one second later door locked, even though it is still unlocked.
When I lock the door, I do not receive any information.
So only the unlocked card works.
On Matter, both cards work very well.
I guess that is progress 
Could you enable the webhook level in the log and then operate the lock as normal.
I have found that the lock is no longer sending the latched state via the webhook and I have my lock set to return to the latched state after 15 seconds so that my door stays shut. Basically my door automatically locks when it is shut, so the SwitchBot lock has to release the lock to open the door. It then has a double lock position that puts the deadbolts across and I have it set to put the lock into that state at night or when everyone has left the house.
Now, the lock appears, but when you unlock it, it stays closed. For example, on Smarthings it becomes open. Can the same thing be done?
Here is what happens when, first, I unlock the lock, and then, in a second step, I lock it.
What happens in the logs is really strange: it starts with locked, then unlocked, and then several locked entries afterwards.
@Giovanni4312 and @dudu_95 I think you both are experiencing the same issue with the Lock reported false locked message.
The padlock does open when the lock is unlocked.
Unfortunately, this only happens with SwitchBot. With Matter, there is no issue. We might need to ask Homey how they coded their two cards to see what’s going wrong.
It’s not the cards, it’s the notifications. The app uses webhooks, and they are all messed up on the SwitchBot end. Previously, the Lock would send LOCKED followed by UNLOCKED and would only send LATCHED or LOCKED when it returned. As you can see from your log, it is now sending a rouge LOCKED about 1/2 a second after the unlocked, and I never see the LATCHED anymore.
The Mater interface is a local connection controlled directly from the hub, so it doesn’t rely on those webhooks.
ATM, my contact at SwitchBot has gone silent, even with Athom giving the a nudge.
@Adrian_Rockall Thank you for creating the ESP32 software. I’m hoping to move away from the hard coded ESP32 setup I have on Home Assistant for my SwitchBot contact sensors, but I’m having an issue connecting them with Homey SHS. I do not own a Homey Bridge and have no intention of adding one. There are enough controllers in my home already.
Is it currently possible to use the ESP32 boards without owning a Homey Bridge? I saw the BLE device when I selected “Get Hub Devices” once, but when I tried to add one of contact sensors, it said no devices found. Now each time I press the “Get Hub Devices” button, it returns Invalid Token, and when I now try to add a contact sensor as BLE type, it asks for a Homey Bridge. I don’t own a SwitchBot Matter hub and don’t intend to add one, so I was hopeful these ESP32 boards would work as sudo hubs.
The log does show that my ESP32 was found at one point, and all of the nearby contact sensors also appeared in the log. I can also see them in the ESP32 web page.
I’ve tried the following:
- Rebooting the ESP32
- Re-writing the bin file incase it didn’t image properly the first time
- Moving to the stable version of the SwitchBot Homey app and then back to the test version when the stable version didn’t offer any improvement.
Please let me know if what I’m trying to do is currently impossible, or if there are logs I can share that will be helpful.
The following log shows a SwitchBot hub, but that is in fact the IP address of the ESP32
* 2026-02-08T09:40:20.460Z
* server got: SwitchBot BLE Hub! 28:5e:07:a5:05:28 from 192.168.0.34:1234
Hmm, that’s an interesting conundrum. The ESP32 uses the LAN to communicate with Homey, so in theory it could work. But I tried to make it seamless for Homey Pro users by hooking into the BLE drivers, that way it just backs up Homey and devices are added in the normal way.
As Homey SHS only supports BLE via a bridge it requires that to add BLE based drivers.
I will have to ponder on how I can allow for this situation.
1 Like
This may be due to Homey platform/UI limitations, but I’m noticing an issue with the visual lock state.
When the lock is unlocked and the latch remains open, SmartThings clearly shows an open padlock icon. In the Homey app, instead, the padlock briefly opens and immediately closes again, so there’s almost no visual indication that the latch is actually open at that moment.
This makes it hard to understand the real lock state at a glance.
