Is there a way to disable Discovery?
My WEMO light switch seems to only show up once in a while so I would prefer to do everything through MQTT and SmartThings. I dont see how to ignore it in the discovery components section.
ih8gates
(Scott Reston)
April 24, 2017, 6:20pm
2
Comment out âdiscoveryâ in your configuration.yaml
# discovery:
1 Like
Wow, way too easy, thanks for the reply (and quick too)!
I did that and saved but it does not stop auto discovery.
francisp
(Francis)
April 10, 2023, 3:43am
5
See the notes on discovery
Depends on what you donât want to be discovered
Comment out default_config, and add back what you need :
Could someone just tell me using quotes what I need to add to the config to get discovery to stop? Iâm not a coder, so I donât know what you guys are talking about. I tried putting a hashtag in front of the word âdiscoveryâ but that didnât do anything. I keep getting notified about random devices being detected and I just want it to stop.
francisp
(Francis)
April 15, 2023, 7:10am
7
This is my configuration.yaml, but you might have different needs :
# Configure a default setup of Home Assistant (frontend, api, etc)
#default_config:
# Individual options represented by default_config
automation: !include automations.yaml
automation manual: !include_dir_merge_list automations
template split: !include_dir_merge_list template
#cloud:
config:
counter:
dhcp:
energy:
frontend:
history:
image_upload:
input_boolean: !include input_boolean.yaml
input_datetime:
input_number: !include input_number.yaml
input_select:
input_text:
input_button:
logbook:
#map:
media_source:
#mobile_app:
my:
person:
scene: !include scenes.yaml
script: !include scripts.yaml
#ssdp:
stream:
sun:
system_health:
#tag:
timer: !include timer.yaml
#updater:
#usb:
#webhook:
#zeroconf:
zone:
#includes not in default_config
python_script:
group: !include groups.yaml
sensor: !include sensor.yaml
binary_sensor: !include binary_sensor.yaml
switch: !include switch.yaml
light: !include light.yaml
notify: !include notify.yaml
mqtt: !include mqtt.yaml
I think not to have anything discovered, these are the important ones :
#ssdp:
#zeroconf:
# Loads default set of integrations. Do not remove.
default_config:
# Load frontend themes from the themes folder
frontend:
themes: !include_dir_merge_named themes
# Text to speech
tts:
- platform: google_translate
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
#discovery
Does it matter if I put a hashtag in front of âdiscoveryâ? Maybe that was why It wasnât working. Maybe I should just disable notifications all together while Iâm at it.
francisp
(Francis)
April 23, 2023, 5:15am
9
Spook has a service homeassistant.ignore_all_discovered
How do I install that? The instructions are terrible and are filled with jokes that make it impossible for a serious minded person to interpret. I tried clicking on the install link but then it says I need something called âhacsâ which upon clicking that link it says the page does not exist. Is there an easy way to just turn off ALL notifications? I donât want any notifications or fancy balloon icons to distract me. All I need this app to do is to open and close a garage door, nothing more and nothing less.
ffreitas
(ffreitas)
December 18, 2023, 5:23am
11
Hey there! Iâm having a bit of trouble trying to prevent an auto-discovery from happening on my network. Iâve been using this extension, but unfortunately, I havenât had much luck with it.
Do you have any suggestions on how to run and prevent that integration?
mgutt
April 13, 2024, 3:55pm
12
How do I obtain the current representation of âdefault_configâ?
mgutt
April 13, 2024, 3:57pm
14
This does not explain the lines like âautomation: !include automations.yamlâ or similar.
francisp
(Francis)
April 13, 2024, 3:59pm
15
There are not part of default_config:
mgutt
April 13, 2024, 4:13pm
16
Ok, so the most recent list is this:
{
"domain": "default_config",
"name": "Default Config",
"codeowners": ["@home-assistant/core"],
"dependencies": [
"assist_pipeline",
"bluetooth",
"cloud",
"conversation",
"dhcp",
"energy",
"history",
"homeassistant_alerts",
"logbook",
"map",
"media_source",
"mobile_app",
"my",
"ssdp",
"stream",
This file has been truncated. show original
Sadly this idea was declined:
home-assistant:dev â daneget:dev
opened 10:55PM - 16 Dec 21 UTC
## Proposed change
The default_config integration enables a set of default inte⊠grations. Each integration in this set can still be configured by the user by simply adding it after default_config. For example:
default_config:
automation:
# override config here
So while it's still possible to change configuration for each default integration, it's currently not possible to disable any of the default integrations.
This could be useful, for example I'm having an issue with the dhcp integration in Docker. I don't need it. But to disable it now, I must remove the default_config integration and keep track of all the default integrations myself. I've done this in the past, and it resulted in me missing out on a lot of new features in new Home Assistant releases. đ
I'm creating this PR to get some feedback. I'll add docs & tests if you like my suggestion!
## Type of change
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
- Original pr in which is based this one: Add exclude option to default_config #57871
- This PR fixes or closes issue: fixes DHCP discovery spamming DNS PTR requests in Docker #57378
- This PR is related to issue: DHCP discovery spamming DNS PTR requests in Docker #57378
- Link to documentation pull request:
## Checklist
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [x] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [x] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [x] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [x] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
- [x] No score or internal
- [ ] đ„ Silver
- [ ] đ„ Gold
- [ ] đ Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
1 Like
axelgs
(axel)
October 3, 2025, 7:07am
17
Find Spook in HACS and install
Find Spook in the regular integration section and install
Now you can go to Developer tools â Services and run homeassistant.ignore_all_discovered.
This ignores all currently discovered entities and integrations, but it does not stop home assistant looking for new ones.