Update shelly docs to make it clear that active Bluetooth connections cannot be proxied (#38761)

This commit is contained in:
J. Nick Koston 2025-04-26 10:14:09 -10:00 committed by GitHub
parent 78ceca8a85
commit 6d74644b1e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -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 devices 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 %}