jeans/developers.home-assistant
jeans/developers.home-assistant
1
0
Fork 0
mirror of https://github.com/home-assistant/developers.home-assistant.git synced 2025-07-14 04:46:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update "configuration.yaml" URL on "Entity Registry and disabling ent… (#531)

Browse Source
This commit is contained in:
Jeff Rescignano 2020-05-17 13:46:53 -04:00 committed by GitHub
parent bbfe408f18
commit 63a4fba052
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/entity_registry_disabled_by.md
View File

@ -35,6 +35,6 @@ If `disable_new_entities` is set to `True` and `entity_registry_enabled_default`
Some integrations will want to offer options to the user to control which entities are being added to Home Assistant. For example, the Unifi integration offers options to enable/disable wireless and wired clients. Some integrations will want to offer options to the user to control which entities are being added to Home Assistant. For example, the Unifi integration offers options to enable/disable wireless and wired clients.
Integrations can offer options to users either via [configuration.yaml](configuration_yaml_index) or using an [Options Flow](config_entries_options_flow_handler.md). Integrations can offer options to users either via [configuration.yaml](/docs/configuration_yaml_index) or using an [Options Flow](config_entries_options_flow_handler.md).
If this option is offered by integrations, you should not leverage the disabled_by property in the entity registry. Instead, if entities are disabled via a config options flow, remove them from the device and entity registry. If this option is offered by integrations, you should not leverage the disabled_by property in the entity registry. Instead, if entities are disabled via a config options flow, remove them from the device and entity registry.