Could you try deleting the device and adding it again. I had to change a custom capability name as I chose a built in one by mistake.
Thatâs what I did. I will check it out, at this very moment the data is updating. 
Hello Adrian Rockall,thanks for your great app!
Is there a way to use the buttons of the Switchbot hub 3 for trigger a flow or a device in Homey?
I donât think itâs possible otherwise i trust you already integrate this function in actions card but i try anywayâ
.Thanks
Yesterday, Switchbot rolled out firmware update v20.16.16 for Hub 3. Since then, my Look pro doors have been closing on their own every 5 minutes. This is so annoying that Iâve removed the batteries.
Homey is not responsible for this; it is definitely due to the Switchbot Hub. For once, Matter is not the cause either; the same error occurs via Bluetooth. Unplug the hub and everything is fine. Therefore, please refrain from updating. The bug has been reported to Switchbot.
I do not know whether other hubs have similar issues.
1 Like
There were/are several firmware updates also for devices available since a few days ago like for my Switchbot IR motion sensor. That I can say too.
Iâm still testing the ESP32-S3-zero as switchbitBLEHub. Testing it also with different WiFi settings in my Unifi network. So to be continuedâŚ
Anybody else some thoughts/experience/review that want share about the ESP32-S3-Zero ??
But why Iâm now writing is this : Apparently the Switchbot BLE Presence sensor âlightlevelâ value is different exposed to the Homey environment than the Switchbot (Hub/Cloud) Presence sensor âluminanceâ value.
Because the hub âluminanceâ value of a presence sensor can be used as trigger as âwhen the luminance is above âŚ.lx for âŚ. (Duration in seconds/minutes)â or âwhen the luminance is below âŚ.lx for âŚ. (Duration in seconds/minutes)â. The âlightlevelâ value of the same BLE presence sensor is not capable (yet??) to be ursd as such trigger above/below a certain threshold and for a certain duration.
The Switchbot Presence sensor hub values :
And its possible triggers including the luminance threshold values above/below for a certain duration:
And the same Switchbot BLE presence sensor:
And its possible triggers without the âlightlevelâ value threshold triggers above/below for a certain duration.
Because these specific triggers became mainly as standard available in one of Homeyâs Firmware updates for almost every device. Iâm thinking that Homey basically didnât somehow pickup the BLE lightlevel values as such usable/manageable and so doesnât offer these triggers.
Iâm honestly saying that nobody is to blame for this.
Just informing you and maybe 
and really maybe it could be improved , I âm explicit saying improved and not solved because its not a mistake in my honest opinion, in the future.
By the way I didnât check any other BLE value yet if they experiencing the same âdiscriminationâ like the lightlevel and luminance value for the normal (=IR) motion sensors. Or the BLE ââ hub temperature & humidity sensors. 
Addendum: I just took a look at the ânormalâ (=IR) SwitchBot motion sensors and it seems/appears these havenât these differences in triggers between the HUB and BLE versions as of lightlevel/luminance values (above or below for a certain duration).
The problem with the new Hub 3 firmware has been solved.
Simply delete the lock in the Switchbot app and re-register it. If you use the same name, you donât even have to fix the flows in Homey.
