From 82175819c3eb3e11bbcd0066227cbfc51d4d78fc Mon Sep 17 00:00:00 2001 From: Joostlek Date: Thu, 19 Dec 2024 15:20:19 +0100 Subject: [PATCH 1/2] Update unique-config-entry rule --- .../core/integration-quality-scale/rules/unique-config-entry.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/core/integration-quality-scale/rules/unique-config-entry.md b/docs/core/integration-quality-scale/rules/unique-config-entry.md index 25a0c624690..860a4351e67 100644 --- a/docs/core/integration-quality-scale/rules/unique-config-entry.md +++ b/docs/core/integration-quality-scale/rules/unique-config-entry.md @@ -17,6 +17,8 @@ This can lead to duplicated devices and entities with unique identifiers collidi Any discovery flow must also ensure that a config entry is uniquely identifiable, as otherwise, it would discover devices already set up. To prevent this, we need to ensure that the user can only set up a device or service once. +Trying to set up a device or service that is already set up should be prevented by the integration. +This should be handled by the reconfiguration flow, in where we can be more consistent with what gets updated. ## Example implementation From 9abb0602cabbd5a6b38e5ef906a0dc06d18a0c5d Mon Sep 17 00:00:00 2001 From: Joost Lekkerkerker Date: Thu, 19 Dec 2024 16:28:05 +0100 Subject: [PATCH 2/2] Update docs/core/integration-quality-scale/rules/unique-config-entry.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Abílio Costa --- .../core/integration-quality-scale/rules/unique-config-entry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core/integration-quality-scale/rules/unique-config-entry.md b/docs/core/integration-quality-scale/rules/unique-config-entry.md index 860a4351e67..fc532acc902 100644 --- a/docs/core/integration-quality-scale/rules/unique-config-entry.md +++ b/docs/core/integration-quality-scale/rules/unique-config-entry.md @@ -18,7 +18,7 @@ Any discovery flow must also ensure that a config entry is uniquely identifiable To prevent this, we need to ensure that the user can only set up a device or service once. Trying to set up a device or service that is already set up should be prevented by the integration. -This should be handled by the reconfiguration flow, in where we can be more consistent with what gets updated. +If an update to the configuration is required, it should be handled by the reconfiguration flow instead, as it allows us to be more consistent with what gets updated. ## Example implementation