Yep, see my post above about the webhook issues. Waiting to see if SwitchBot will fix it, but I am loosing confidence in them now.
They seem to be spending all their time releasing new products and not fixing issues with existing ones and it looks like their servers are struggling under the load. If they would only add a local interface to their hubs, it would at least solve the later.
If anyone wants to take over the SwitchBot app then let me know as I feel totally helpless at the moment.
Do you mean the Homey Bridge popup that is shown when adding a driver with the connectivity set to ble? You can avoid that by pairing the device via Developer Tools
Oh wow, it works 
@SmartHomePrimer so that is the work around. Add the device via the Developer Tools.
I must be doing something wrong. I can see the ESP32 in Homey, and I can see my contact sensors in the ESP32 web page, but when I try to add a BLE contact sensor, it returns âNo new devices have been foundâ.
Oops, that was a strange bug in the app. I have published a new test version now and I can find my contact sensor in SHS.
Excellent! Thank you so much, and thanks to @smarthomesven for pointing out the method for pairing without integrated Homey BLE.
It all works perfectly, and incredibly simple versus the BLE to MQTT implementation Iâve been using on Home Assistant.
Dear @Adrian_Rockall ,
Any (progress) information or maybe even ETA about supporting the Switchbot Plug Mini (EU) throug BLE please 
?
Thank you.
I see that the latest update made my devices to work, because I can see in Insights it started to update data since Feb 9 from 8:00 am. 
finally after so many months! Thanks
I have had a go at creating a driver but no luck unfortunately. All attempts to control it fail. I think it is using an encrypted command now for security.
Maybe this helps :
In Home assitant it was discovered and I could pair it with :
âAdding encrypted SwitchBot devices
Some types of the SwitchBot devices are encrypted for improved security. More types and models will be added as encrypted devices in the future.
An encrypted SwitchBot device can be set up in Home Assistant in two different ways. You can enter the key ID and encryption key yourself, or Home Assistant can import them from your SwitchBot account.
Using this option you can provide your SwitchBot account login credentials and Home Assistant will import the appropriate encryption key from your account.â
Source : SwitchBot Bluetooth - Home Assistant
and their github code for HA :
I noticed the option to obtain an encryption key, but as SwitchBot arenât being helpful at the moment, I am not enthusiastic about spending hours trying to work it out for myself.
Since Christmas I have attended the funerals of my father in law, mother in law and auntie, plus I still have two more in the near future, so I am not feeling great. Maybe I will feel better later and up for the challenge.
Sorry for your loss(es) and stressing you more about this. Was just a question and a try to help with some information.
Take care.
Best wishes!
@Adrian_Rockall
Really appreciate this code. I have had great reliability from it. I actually just modified a driver on another smart home hub to use your ESP32 bridge and thatâs working great thanks to the foundation you built! 
I wonder if you would consider a minor modifcation to the ESP32 code. A former integration where I was using an ESP32 D1 mini (which works with your code too by the way), had the ability to turn on the Blue LED on the D1 Mini when it connected to WiFi. This is a great help to quickly be able to glance at the board to see if it has dropped the WiFi connection.
I see that the [ESP32 ESP-32S Development Board 2.4 GHz Dual Core WLAN WiFi + Bluetooth 2-In-1 Microcontroller ESP-WROOM-32 Chip CP2102] that you recommended and I have been using as well, has two LEDs on the board so it should be possible. In fact, I think there are a number of ESP32 boards out there with full RGB LEDs.
Yes, thatâs true. My ESP32C6 also has an RGB LED.
I think I looked into using the LEDâs on my board, but found they were unavailable, however I will check again.
Hi, Iâm using a Lock Ultra F0 with Keypad Vision on Homey. For what Iâve seen and read, Keypad cannot be added as a single device in Homey, it can only interact through the Lock. Maybe it could be implemented, so users can manage unlock types?
For example, since Keypads are usually placed outside doors, managing the âIF unlock by [keypad] via [type=fingerprint, face, code, NFC]â case can be useful to me to turn on entrance lights in the evening using unlock event, because thatâs what I do when I come back home, which is different from the âIF unlock by [button press]â case that I use when I go out.
Or maybe is it an easier way to manage going out and coming back home with the Lock Ultra?
Unfortunately, that information is not available to Homey, so just a general unlock notification is all we can have.
Since a few days my homey reports sometimes my doors/-windows are still open although they are closed. I use Both the cloud & BKE setup of the (same) contact sensor in a sensor group (through the group app) to assure that nothing is left open when I leave the house and the cloud based might be malfunctioning. Worked fine for almost Iâve installed them in Homey until now. By the way : Any suggestions/solutions to boost the BLE signal and or range ? In 1% of events the BLE version isnât the same as the cloud version within 3 minutes. Takes sometimes much too longer to report a state change/ an event.
I saw just now the one of the latest updates of the app had changed something to the BLE contact sensors.
Just wondering if this could be the cause of my latest issues. 
I donât think that will cause an issue as it was just the âTypeâ that I changed from âCâ to âdâ and that should only affect the discovery when adding new devices. Once they are added the matching is done by the MAC address and the type is not used. I hadnât notice the issue as my ESP32 modules were correct and overriding Homey.
The only solution is to use an ESP32 and run my code on it. Homeyâs BLE requires polling and I canât do that faster than once every 30 seconds, plus the BLE reception is not great on some Homeyâs so the data will often be missing. My ESP32 code is constantly listening for BLE data and pushes updates to Homey straight away, so the delay is generally about 1 to 2 seconds. Plus the ESP 32 BLE is much more sensitive and has about 5 times the range of the best Homey I have.
Which ESP32 code and how to implement it and use it with Homey.
I have very little knowledge/ experience with ESP devices because of the usage of them as Bluetooth proxy âs and voice control devices for Home assistant. But this is very simple.
And which appâs do I need for Homey for ESP32 ?
I would like to use it too but would really need a how-to with a step by step detailed description including screenshots to get it right.
I still have one of these as spare , meant for Bluetooth proxy.
