Why can’t I see which ESP32 device is being used as a proxy on my Bluetooth devices somewhere?
Nice if one could see that device XXX is connected to proxy ABC_XYZ. Or in the best case, draw a “map” that shows how the individual units are connected.
The BLE proxy mystery…
Would definitely like such a function! +1
1 Like
You can see the entity-id of the proxy as an attribute in the device-tracker entity of your BT device.
Did I misunderstand?
How? I only see distance and “at home”
Those are the entities. It’s in the attributes - of both of those entities.
Source is a MAC address - which means it was detected by the USB stick.
Source is a not a MAC address, its the proxy in my bedroom.
2 Likes
For my BThome temperature sensors this is different I guess. No attributes to view in those sensors.
Isn’t this only for iBeacon devices?
For my Xiaomi plant sensors, I can’t see devices or attributes at all… 
So if you click on Temperature, are there no attributes in the popup?
Signal strength entity?
Same for all entities - no attributes.
Yeah, it appears such functionality is not universal for BLE devices, even though it probably should be.
Home Assistant allows for a concept of one device being accessible via another (via_device), intended for static topology. For example, a product provided via a hub that also shows up as a device should indicate the hub in via_device of its device record. I don’t actually know what this looks like in the UI, since I don’t have any devices that do this.
I’m not sure if that is especially appropriate for Bluetooth proxies though, as the devices may move around and thus change which device they are connected via. It at the very least has the limitation that I don’t think you can automate based on device record attributes like that.