I have seen a search-parameters.y*ml file popping up in the ST version of LAN drivers. I don’t see it documented, but it looks like there may now be some platform support for discovery. Is this true? Does it also now handle conflicting drivers searching for the same devices? If this enables platform discovery, how do drivers register for events?
Sonos:
ssdp:
- searchTerm: "urn:smartspeaker-audio:service:SpeakerGroup:1"
Hue:
mdns:
- service: "_hue._tcp"
Bose:
ssdp:
- searchTerm: urn:schemas-upnp-org:device:MediaRenderer:1
Wemo:
ssdp:
- searchTerm: urn:Belkin:device:*
Samsung:
ssdp:
- searchTerm: urn:samsung.com:device:RemoteControlReceiver:1
The search parameter files have been added over the last couple of weeks but seem to be completely independent of the source of the drivers at the moment. I was wondering if they might be intended to control the automatic installation of the drivers, as having a shed load of drivers pre-installed is an obvious nonsense.
1 Like
I’m thinking it may be similar to the fingerprints but for LAN devices. One issue I had with Hue was that a user could install my driver, but scanning would produce devices for the ST version of the driver as well. I ended up re-writing my driver to get around it. I reported that issue to the ST team. Maybe this is their solution?
Hi @blueyetisoftware let me ask it the team 
1 Like