Fix bluetooth integration matching with service_data_uuids and service_uuids (#75687)

* Fix bluetooth integration with service_data and service_uuids

We would only dispatch a new flow when the address was seen for
the first time or the manufacturer_data appeared in a followup
advertisement. Its also possible for the service_data and
service_uuids to appear in a followup advertisement so we
need to track these as well

* improve logging to avoid overly large messages

* improve logging to avoid overly large messages

* adjust

* adjsut

* split

* coverage

* coverage

* coverage

* coverage

* fix matcher

* more coverage

* more coverage

* more coverage

* revert switchbot changes and move to seperate PR
This commit is contained in:
J. Nick Koston
2022-07-24 16:39:53 -05:00
committed by GitHub
parent d890598da7
commit bbb9443b00
5 changed files with 398 additions and 103 deletions

View File

@@ -194,6 +194,7 @@ MANIFEST_SCHEMA = vol.Schema(
vol.Schema(
{
vol.Optional("service_uuid"): vol.All(str, verify_lowercase),
vol.Optional("service_data_uuid"): vol.All(str, verify_lowercase),
vol.Optional("local_name"): vol.All(str),
vol.Optional("manufacturer_id"): int,
vol.Optional("manufacturer_data_start"): [int],