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.
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.
Hello Adrian, I tried to delete and re add it without any luck. I still get the same error.
Hi, has anyone managed to get the SwitchBot Bot (BLE) working with Homey Pro 2019?
Iâve successfully added it to Homey, and it reports the BLE signal regularly. Signal strength is good (â48 dB, currently placed about 10 cm from the hub).
However, when I try to control the bot, the command times out after 30 seconds. No PIN code is enabled.
After several failed attempts, I brought the device home from the cabin, where I have a Homey Pro 2023, and there it worked perfectly. Iâve now brought it back again, and once more it reports the signal correctly, but it still canât be controlled.
Any ideas or similar experiences?
Unfortunately, BLE signal varies a lot between Homeyâs. I had a very old Homey (I think it was a 2015 but itâs dead now) and that works very well and was what I used to initially develop the app. I then got a Homey 2019 and that was useless on BLE. Even when it was next to the old one, it couldnât control any of the devices that the old one could. My Homey 2023 was somewhere in between and could control devices in the same room, but wouldnât control devices in other rooms that the old one did.
Thatâs why I develop my own hub using an ESP32. One of those can cover most of my home, and I have two so my whole house is covered. Iâm not sure my old Homey would have reached some of the new devices ,so two ESP32 hubs is not surprising.
Hi, my SwitchBot Bot is placed about 10 cm from the Homey hub and reports a good signal.
So the signal strength itself should be fine.
The intended final placement for the SwitchBot Bot is around 50â100 cm from the Homey Pro 2019, as the equipment is mounted to the side.
Would you like me to share or have a look at the log data, or should we simply conclude that BLE on the Homey Pro 2019 doesnât work properly?
Please send the log. Make sure you select Detailed information in the log level, clear the log and then operate it. Give it a few seconds and then go back to the log screen and press Send Log.
Hi, Iâve now sent the detailed log.
Thanks in advance, and please let me know if you need any additional data.
I can see it managed to connect but then times out when getting the notification characteristic. I presume the firmware is up to date?
Apart from that I have no idea.
Yes, the firmware is V6.6, which I understand is the latest version.
You should remove your phone number from that post
Hi, since you couldnât see what might be causing the problem, I ended up giving up integrate direct to the Pro 2019. I got hold of an ESP32 and set it up with your BLE gateway solution. It connected right away and worked, so it managed to work around the issue 
Hi @Adrian_Rockall, I recently updated my ESP32 BLE Hub to v2.8 (from v2.7). Since then I am frequently (every few days) running into the issue that the hub is not relaying commands to my curtain driver (my only SwitchBot device).
I can reach the hub via the web interface and the log in the SwitchBot app on Homey does not record an error. It seems like the BLE functionality of the hub stops responding/has crashed. After I power cycle the ESP32 it starts communicating BLE commands again.
I saw in your GitHub repository that you committed one or more change(s) after the v2.8 binaries were created. Not sure whether those changes are related and would fix the issue. If so, could you kindly make availabe a new binary/OTA file?
I am not sure whether you are aware of this issue and if I can provide you with more info on how to address the issue. I the mean time, I assume I can downgrade to v2.7?
I will rebuild the OTA firmware this evening.
The update should fix the issue as I noticed the BLE stopped working after a while. Iâm not sure why it does it, but I monitor the number of updates per minute and now if it stops I reboot the ESP32. It does mean it could stop responding for up to a minute but should recover. Sadly, it seems the Arduino libraries are still a bit buggy.
The new OTA version should be in GitHub now
Thanks again for the quick follow-up!
