Making a SwitchBot Bot working with HA with BLE and No cloud

Hi there,
I have a switchbot bot currently working in HA through the cloud integration and a Switchbot Minihub. It sometimes get stuck.

More recently I introduced a network of BLE proxies all around the property and I would like to use the bluetooth integration instead. The BLE proxies mesh is actually well working with other BLE devices.

So,

  • I have a shelly with BLE PROXY enabled in ACTIVE SCAN in one meter distance from the bot.
  • I can read in the announcements section of the BT integration the BLE mac of the Bot, as part of the many announcement

But,

  • Integration doesn’t find it , either if I log in with the switchbot account or not.

I cannot understand if the problem is “making it advertise in the right moment”. And if so, how to do it.
As well I cannot understand if the problem is about the BLE encryption. In such a case, I didn’t find where to extract the key, and neither where to paste it, but I was hoping the integration may make this for me when I give it my credentials.
Another thing I cannot find is how to put the bot in pairing mode, if this is needed, as it’s already working with the cloud integration.

Do someone managed to connect the Switchbot bot through the BT integration? What to do? Any advice will be more than welcome!

Thanks in advance!

I have a bunch of switchbot blind controllers that use Bluetooth, and all I did was set them up in the Switchbot app and then go to Home Assistant and setup the Switchbot bluetooth integration. After that they were all sitting there waiting to be added. I’ve never had the minihub in the mix at all.

If these are bluetooth native devices, you should probably confirm they are supported by the Switchbot bluetooth integration.

After that, I’d suggest try removing them from the minihub (or reset them) and then set them up again in the Switchbot app.

I ran through this closed issue on the SwitchBot integration

It appears the issue is caused not by the switchbot (that is indeed supported) and neither from the integration. Issue sounds to be in the nature of my BLE proxies mesh, created by Shelly devices.
One plausible explaination is that the Shelly BT proxy is not able to support the two ways communication with the speed and latency that are needed in order for the integration to “pair” with the bot.

Thus, so far, no way to get what I want.

Well, at least that explains it. I have all ESPHome bluetooth proxies in my setup, which is probably why I haven’t run into this problem.