From 6d74644b1e9acc8c9af3c33f1b5ede53fbca68b4 Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Sat, 26 Apr 2025 10:14:09 -1000 Subject: [PATCH] Update shelly docs to make it clear that active Bluetooth connections cannot be proxied (#38761) --- source/_integrations/shelly.markdown | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/source/_integrations/shelly.markdown b/source/_integrations/shelly.markdown index 81ea11b0597..68d18bba116 100644 --- a/source/_integrations/shelly.markdown +++ b/source/_integrations/shelly.markdown @@ -92,7 +92,13 @@ Integration is communicating directly with the device; cloud connection is not n ## Bluetooth Support -Shelly generation 2+ devices that are not battery-powered can act as a Bluetooth proxy for advertisements. Active or passive listening can be enabled in the options flow. +Shelly Gen 2 and newer devices (excluding battery-powered models) can act as Bluetooth proxies, forwarding advertisement data. You can enable either active or passive listening through the device’s options flow. + +{% tip %} +Shelly devices do **not** support proxying active (GATT) connections. +{% endtip %} + +For more details, see [Remote Adapters](/integrations/bluetooth/#remote-adapters-bluetooth-proxies) in the [Bluetooth integration](/integrations/bluetooth). {% include integrations/option_flow.md %}