From 63a4fba052a40165af26cbd9cddd3f0295ca8ab8 Mon Sep 17 00:00:00 2001 From: Jeff Rescignano Date: Sun, 17 May 2020 13:46:53 -0400 Subject: [PATCH] =?UTF-8?q?Update=20"configuration.yaml"=20URL=20on=20"Ent?= =?UTF-8?q?ity=20Registry=20and=20disabling=20ent=E2=80=A6=20(#531)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/entity_registry_disabled_by.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/entity_registry_disabled_by.md b/docs/entity_registry_disabled_by.md index fb5def1f..58b68edf 100644 --- a/docs/entity_registry_disabled_by.md +++ b/docs/entity_registry_disabled_by.md @@ -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. -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.