Device YAML Overwrite when creating device with same name #5345
Comments
|
I just got burned by this myself. There really ought to be at least a warning that you're about to overwrite an existing config! |
|
Saw someone comment this happened to them and thought they just didn't read a prompt, but nope, this overwrites with no warning what-so-ever, and this definitely needs to be addressed. |
|
Just had this happen, was surprised to see that it did this with no warning. At the very least I'd have expected it to move the existing yaml to the trash, but no. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem
Creating a new device of a certain name overwrites any existing device with that name without any warning.
It seems that at very least, this action should be warned against as it can lead to loss of existing data.
Same as #4491
Which version of ESPHome has the issue?
2023.12.5
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
Core 2024.1.2
What platform are you using?
ESP8266
Board
No response
Component causing the issue
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: