WTH: Why are we not able to disable specific automatic discovery classes?

I have several Airbnb properties that all have one or more Roku devices installed. These devices have guest mode that causes the device to be discovered after the the system auto-formats itself after each guest. Each time it comes up on the network it gets detected as a brand new Homekit device. I ignore them, to clear the discovery, but I have this ever growing set of ignored discovered devices and it’s annoying to see everytime guests leave!

I would love to be able to disable discovery of specific integrations and not all of them. Preferably this would be a list of enable/disable toggles in the GUI so that we don’t have to modify the YAML and reload/restart to get it to take effect

Why not just disable discovery for the time being? These are pre-set up airbnb’s, you should really need discovery anyways.

take over default_config and do not use these

(unless you need bluetooth, that one’s discovery and bluetooth usage is combined into 1 integration)

For my full properties, sure. But I also Airbnb extra rooms in my primary residence. I’m constantly tinkering with my home HA so I wouldn’t want auto-discovery completely disabled there! Basically, I would really like a way to fine tune the auto-discovery system.

1 Like

That’s part of the problem. You have to take over the default_config and then specifically add everything back that you may need. This should be something that is tuneable via the GUI. That’s really what I’m wanting I guess.

Yah for sure, but just remember auto discovery usually only saves you 1 or 2 clicks.

The dev team will likely never add tuning of default_config, they don’t even allow exclusion for it. It’s been attempted a few times and they are very against it for some reason.

allowing adjustments for ssdp, zeroconf, dhcp hasn’t been brought up as from what I remember. That might be an option going forward

Of course, here I am now trying to disable this one one of my properties and finding out that you can’t do a !include default_config.yaml on a bare line as anything else in the configurage.yaml then throws and error. It’s apparently only valid as something following a yaml key :frowning:

New WTH! :smiley:

try

<<: !include default_config.yaml

Likely won’t work but maybe it will.

Nope, that just causes even more errors.

1 Like