From ac71dfb53a36f96cf97038ea1d8e1212a57d1978 Mon Sep 17 00:00:00 2001 From: Mike O'Driscoll Date: Mon, 12 Feb 2024 07:20:00 -0500 Subject: [PATCH] Fix link to manifest.json in bluetooth docs. (#2077) --- docs/bluetooth.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/bluetooth.md b/docs/bluetooth.md index eea7f6d8..d61a726a 100644 --- a/docs/bluetooth.md +++ b/docs/bluetooth.md @@ -5,7 +5,7 @@ sidebar_label: "Building a Bluetooth Integration" ### Best practices for integration authors -- Integrations that need to use a Bluetooth adapter should add `bluetooth_adapters` in [`dependencies`](creating_integration_manifest#dependencies) in their [`manifest.json`](creating_integration_manifest). The [`manifest.json`](creating_integration_manifest) entry ensures that all supported remote adapters are connected before the integration tries to use them. +- Integrations that need to use a Bluetooth adapter should add `bluetooth_adapters` in [`dependencies`](creating_integration_manifest.md#dependencies) in their [`manifest.json`](creating_integration_manifest.md). The [`manifest.json`](creating_integration_manifest.md) entry ensures that all supported remote adapters are connected before the integration tries to use them. - Call the `bluetooth.async_get_scanner` API to get a `BleakScanner` instance and pass it to your library. The returned scanner avoids the overhead of running multiple scanners, which is significant. Additionally, the wrapped scanner will continue functioning if the user changes the Bluetooth adapter settings.