jeans/developers.home-assistant
jeans/developers.home-assistant
1
0
Fork 0
mirror of https://github.com/home-assistant/developers.home-assistant.git synced 2025-07-23 09:16:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

note case requirements of zeroconf config (#884)

Browse Source
This commit is contained in:
David Radcliffe 2021-04-12 04:17:34 -04:00 committed by GitHub
parent 98e928e7bb
commit e72a156c8d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/creating_integration_manifest.md
View File

@ -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.