Configuration change (this will require users to update their yaml configuration files to keep working) Breaking change (fix or feature that would cause existing functionality to not work as expected) New feature (non-breaking change which adds functionality) Bugfix (non-breaking change which fixes an issue) This PR adds a convenient way to track the p … resence of iBeacon devices. What am I missing? I’ve googled for quite some time and I’ve come up empty handed except for suggestions to use another approach like room-assistant. The companion app ble function only seems to work as an ibeacon_uuid, and listing it as a service_uuid for ble_rssi only results in a NaN return…so no dice.

I can add a sensor for it using the ble_rssi platform…but unlike the ble_presence platform I can’t specify an ibeacon_uuid…only a service_uuid. My initial thought was to use the RSSI values I see in the log trace to filter readings (somehow, maybe set a minimum) but I can’t see how to get the RSSI. This is working and the sensor is on or off depending on the phone proximity…however…eventhough I move quite a long way away (I go upstairs) it can still be detected in the room downstairs. I’ve enabled the BLE beacon function and I’ve configured the esp32 to look for it as a binary sensor (ibeacon_uuid: ‘blah blah blah’). I’m running ESP Home on an ESP32 Dev Kit C, and the home assistant companion app on a Samsung S20.

Bt rssi