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-10 19:06:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add blog post for config_entry unique_id collision warning (#2467)

Browse Source 
* Add blog post for config_entry unique_id collision warning

* Update and rename 2024-11-22-config-flow-unique-id to 2024-11-22-config-flow-unique-id.md

* Update 2024-11-22-config-flow-unique-id.md

* Rename 2024-11-22-config-flow-unique-id.md to 2024-12-19-config-flow-unique-id.md

* Adjust date

* Rename 2025-01-16-config-flow-unique-id.md to 2025-03-01-config-flow-unique-id.md
This commit is contained in:
epenet 2025-03-01 12:09:59 +01:00 committed by GitHub
parent 8e2c3c4e7b
commit 6c29010778
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
blog/2025-03-01-config-flow-unique-id.md Normal file
View File

@ -0,0 +1,15 @@
---
author: epenet
authorURL: https://github.com/epenet
title: "New checks for config flow unique ID"
---
### Summary of changes
When a config flow creates an entry with a colliding unique ID, the old entry is currently automatically removed and replaced with the new config entry.
This can lead to unexpected behavior, and integrations should be adjusted to instead abort the flow.
In case of manual flows, integrations should implement options, reauth, reconfigure to allow the user to change settings.
In case of non user visible flows, the integration should optionally update the existing entry before aborting.
More details can be found in the [config flow](/docs/config_entries_config_flow_handler#unique-id-requirements) documentation.