Discovery no longer optional?

Configuration
1

I don’t have discovery: anywhere in my config, yet I see log lines like:

2019-07-18 09:47:01 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=persistent_notification, service=create, service_data=title=New devices discovered, message=We have discovered new devices on your network. [Check it out](/config/integrations), notification_id=config_entry_discovery>

2

Did you see this in the 0.94 Release Notes:

3

Thanks! I did stumble across this, I guess I should have mentioned that. It’s not clear to me, can we opt-out of discovery? Can we whitelist to only allow discovery for some integrations? I’m trying to stop my notifications from being spammed about new devices being discovered, ones that I know I don’t want to add.

FWIW I’m not using the default_config: config option and I don’t have ssdp: or zeroconf: in my config.

4

Zeroconf is automatically added with some other components, I know ios was one so I would guess mobile_app is too and probably some others.

5

You probably have this in your configuraiton.yaml.

default_config:
Currently, that includes this list:

    "automation",
    "cloud",
    "config",
    "frontend",
    "history",
    "logbook",
    "map",
    "mobile_app",
    "person",
    "script",
    "ssdp",
    "sun",
    "system_health",
    "updater",
    "zeroconf"

From https://github.com/home-assistant/home-assistant/blob/be56851feb29c33a1ec7fd12e867a4d0cdfa9d65/homeassistant/components/default_config/manifest.json

6

I just edited my earlier reply to show the correct integration name. No I do not have default_config: anywhere.

7

Do you have UnPnP activated.

1 Like