ZeroConf always loads

Hello, running on a raspberry pi 3 and found recently that mDNS has been causing a large amount of traffic on my network, causing entities to go offline (mainly wemo, but harmony and a dlink camera too).

I moved all my google home device to a separate network, and then started to disable all I could in HA. I removed default_config, and added in the items I needed, ensuring not to include ssdp and zeroconf.

I turned off discovery in Wemo and turned off homekit.

The traffic is much much better, but with Wireshark I still see my pi broadcasting and responding to mDNS items, so something is still running.

Checking the Developer tool -> Info page I see that zeroconf is still loaded. I then checked the logs and sure enough it is still seen loading up. Turned on “debug” logs and see right off the bat that zeroconf is in the list:

2020-04-14 23:26:43 DEBUG (MainThread) [homeassistant.bootstrap] Setting up {'python_script', 'ios', 'config', 'sensor', 'script', 'emulated_hue', 'amcrest', 'myq', 'webhook', 'frontend', 'switch', 'harmony', 'zha', 'map', 'rachio', 'zeroconf', 'envisalink', 'binary_sensor', 'api', 'scene', 'device_automation', 'plex', 'nest', 'http', 'zone', 'zwave', 'sun', 'updater', 'group', 'onboarding', 'history', 'shell_command', 'system_health', 'neato', 'ffmpeg', 'websocket_api', 'lovelace', 'device_tracker', 'ecobee', 'wemo'}

Any ideas how to not get it to load? or what component is causing it to be added to the list?

Thank you!

I am now thinking that one of my other components is reliant on zeroconf, but when doing so all the normal zeroconf items run, not just for that one plugin.

Perhaps that makes sense.