From 489a90d7385755b342f2e82ea2df899d4fab89a9 Mon Sep 17 00:00:00 2001 From: ellnic Date: Tue, 19 Sep 2023 11:55:48 +0100 Subject: [PATCH] Update bluetooth to include a section on selecting how to integrate Bluetooth first (#28944) Co-authored-by: J. Nick Koston --- source/_integrations/bluetooth.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/bluetooth.markdown b/source/_integrations/bluetooth.markdown index ccad2ca27bc5..22c823ddb4b2 100644 --- a/source/_integrations/bluetooth.markdown +++ b/source/_integrations/bluetooth.markdown @@ -19,6 +19,12 @@ The Bluetooth integration will detect nearby Bluetooth devices. Discovered devic {% include integrations/config_flow.md %} +## Before you begin + +In many cases, a better approach than a directly connected adapter or card is to use a Bluetooth proxy using an ESP32 since Linux kernel updates have previously broken Bluetooth functionality and Bluetooth driver support Linux generally falls behind other operating systems for newer adapters. A Bluetooth proxy is particularly interesting to users who virtualize their instance, where the USB pass-through may cause additional problems. More information is available in the Remote Adapters section below or by visiting ESPhome's [Bluetooth proxy page](https://esphome.github.io/bluetooth-proxies/). + +Suppose a Bluetooth proxy is not a good fit for your use case. Consider using the Home Assistant Operating System when using a local adapter because it includes Bluetooth patches for issues unsolved in other operating systems. + ## Configuration While this integration is part of [`default_config:`](/integrations/default_config/) to enable automatic discovery of the Bluetooth Adapter, it will only be enabled by setting up the configuration flow, or manually adding it to your `configuration.yaml`.