Yeah, I dont know. It’s why I wrote “I suspect”. Just trying to eliminate possibilities.
Bermuda itself doesn’t do anything “beyond” Home Assistant, so it won’t affect the work that the proxy has to do.
I’d be surprised if the Hue bulbs adverts are causing an issue either, advert traffic is tiny by wifi standards, and the proxy is going to prioritise an outbound connection over advert gathering anyway.
Your esphome yaml however may have some effect. If you have modified the window and interval timings in the yaml (or by using my external_component then you could try changing that back to the defaults for a single proxy. Other things to check are:
- Make sure you’re using esp-idf, not arduino.
- Make sure you have flashed the proxy via usb/serial at least once since ~ 2024-06
- Look for other components in your config that might cost the proxy a lot of cpu time or memory (web server, non-ledc pwm, neopixels, displays, templates or local ble components etc)
Even though it’s not really a Bermuda issue, feel free to post your yaml here and I can just check that there’s nothing that stands out as being likely to cause an issue, but otherwise I think you’d need to pursue troubleshoot from the switchbot side of things, at least to start with.
In the bluetooth integration, it will show you how many “slots” your proxies are using as well, if those are getting maxed out that might be causing issues, if each proxy is trying to connect out to multiple devices etc.
1 Like
Thanks for this. You made me realise there were some settings in Bluetooth. I just turned off “passive scanning”, and it’s now instaneous. Appreciate it.
1 Like
Great! This might be something worth adding to the documentation if you’re feeling particularly motivated 
I’m trying to move from Espresense to Bermuda in my camper and am having a problem limiting the scanner radius.
I have one scanner (not a big camper) and currently, it tracks devices as home at a really long distance. I have my radius set down to 4m, but it’s still showing home at 30+ meters. What am I doing wrong here?
Is it possible to filter on the number of clients connected to a proxy? I only want to turn off the basement lights when no clients are connected. Can’t seem to find this in the thread, or I’m using wrong keyword.
Not directly I think. But you might create a template sensor to count the devices which are in an area:
{{ states.sensor
| selectattr('state', 'match', 'Dachboden')
| list
| count
}}
It will output the number of BLE devices which are located in the area “Dachboden”.
2 Likes
This is effectively the same thing as what they asked because of how Bermuda operates. It potentially be flappy but should work.
1 Like
Thanks!
I’ll give it a try. For my area ‘Buiten’ it now outputs 2, while i’m pretty sure it is only 1. I’ll try and experiment a bit with it.
You can filter the output in your template. Trap what’s your on state and off state and boil down to a true false binary sensor.
1 Like