From 10eb28d20dfa7a743c756a1efd8b10261a09a6c9 Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Mon, 18 Jul 2022 16:21:27 -0500 Subject: [PATCH] Change manufacturer_data_first_byte to manufacturer_data_start in bluetooth docs (#1403) Co-authored-by: Martin Hjelmare --- docs/creating_integration_manifest.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/creating_integration_manifest.md b/docs/creating_integration_manifest.md index 94f0d220..645d4317 100644 --- a/docs/creating_integration_manifest.md +++ b/docs/creating_integration_manifest.md @@ -160,7 +160,7 @@ Result (this is intended functionality for the near feature): ## Bluetooth -If your integration supports discovery via bluetooth, you can add a matcher to your manifest. If the user has the `bluetooth` integration loaded, it will load the `bluetooth` step of your integration's config flow when it is discovered. We support listening for Bluetooth discovery by matching on `local_name`, `service_uuid`, `manufacturer_id`, and `manufacturer_data_first_byte`. The manifest value is a list of matcher dictionaries, your integration is discovered if all items of any of the specified matchers are found in the Bluetooth data. It's up to your config flow to filter out duplicates. +If your integration supports discovery via bluetooth, you can add a matcher to your manifest. If the user has the `bluetooth` integration loaded, it will load the `bluetooth` step of your integration's config flow when it is discovered. We support listening for Bluetooth discovery by matching on `local_name`, `service_uuid`, `manufacturer_id`, and `manufacturer_data_start`. The `manufacturer_data_start` field expects a list of bytes encoded as integer values from 0-255. The manifest value is a list of matcher dictionaries, your integration is discovered if all items of any of the specified matchers are found in the Bluetooth data. It's up to your config flow to filter out duplicates. The following example will match Nespresso Prodigio machines: @@ -194,7 +194,7 @@ The following example will match HomeKit devices: "bluetooth": [ { "manufacturer_id": 76, - "manufacturer_data_first_byte": 6 + "manufacturer_data_start": [6] } ] }