Bluetooth Proxy: Allow per-proxy blacklist of BLE device addresses to suppress forwarded advertisements #3533
Unanswered
bdngywjxkt-prog
asked this question in
Component enhancements
Replies: 1 comment
-
|
🏷️ I've automatically added the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Component name
bluetooth_proxy
Link to component documentation on our website
https://esphome.io/components/bluetooth_proxy/
Describe the enhancement
Today, ESPHome Bluetooth Proxies forward all received BLE advertisements to Home Assistant,
which then decides which proxy to use based on RSSI and other heuristics.
In setups with multiple Bluetooth proxies and overlapping coverage, this can lead to
unreliable behavior: a BLE device may associate with a distant proxy instead of a nearby one,
causing unstable presence detection or delayed updates.
Proposed enhancement
Add an optional per-proxy blacklist of BLE device addresses.
If a device is listed in the blacklist of a given proxy, that proxy simply does not forward
advertisements from that device.
This keeps the system simple and deterministic:
Example YAML configuration
Use cases
Multi-room presence detection
In homes with several Bluetooth proxies, presence sensors (e.g. SwitchBot devices or BLE beacons)
may randomly associate with a farther proxy. Blacklisting allows excluding those devices on distant
proxies while keeping redundancy on nearby ones.
Large installations with many proxies
In environments with 4–10 Bluetooth proxies, deterministic routing of BLE advertisements improves
reliability and predictability.
Improved performance and efficiency
Suppressing unwanted advertisements at the proxy level reduces Bluetooth traffic forwarded over Wi-Fi
and processed by Home Assistant.
Explicit configuration instead of heuristics
Users who know their physical layout can define clear rules instead of relying on fluctuating RSSI-based
heuristics.
Anything else?
I have a working prototype and can provide a PR if desired.
Beta Was this translation helpful? Give feedback.
All reactions