From e72a156c8d8aab750c51c344f4171834c55bdc38 Mon Sep 17 00:00:00 2001 From: David Radcliffe Date: Mon, 12 Apr 2021 04:17:34 -0400 Subject: [PATCH] note case requirements of zeroconf config (#884) --- docs/creating_integration_manifest.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/creating_integration_manifest.md b/docs/creating_integration_manifest.md index 942ff6ad..b9adf8e4 100644 --- a/docs/creating_integration_manifest.md +++ b/docs/creating_integration_manifest.md @@ -142,6 +142,8 @@ Certain zeroconf types are very generic (i.e., `_printer._tcp.local.`, `_axis-vi } ``` +Note that the `name` and `manufacturer` filters should be all lowercase and the `macaddress` filter should be all uppercase. + ## SSDP If your integration supports discovery via [SSDP](https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol), you can add the type to your manifest. If the user has the `ssdp` integration loaded, it will load the `ssdp` step of your integration's config flow when it is discovered. We support SSDP discovery by the SSDP ST, USN, EXT, and Server headers (header names in lowercase), as well as data in [UPnP device description](https://openconnectivity.org/developer/specifications/upnp-resources/upnp/basic-device-v1-0/). 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 SSDP/UPnP data. It's up to your config flow to filter out duplicates.