ESP Home Device Management Bug

[rsmanning]

The problem

Its rare I run into this but its always a pain. Normally its when replacing a device and attempting to use the same names or simply changing names to try and keep things organized. You can completely delete a device from ESP Devices and ESP Compiler area, create new and only paste in the config after "Captive Portal", manually flash the device. It shows in the compiler as online immediately even though there is still adaption to do. Then it works but attempts to OTA update or even adopt (depending on the exact procedure and name used), and it says OTA auth failed or issues with API key. Its REALLY annoying, its like the database has remnants of it and key associations it retains even when deleted from everywhere in the GUI. Normally to correct it I have to tweak the name in some less desirable way and add it fresh. Restarting HA after deleting it in the GUI before adding doesn't help the outcome.

What version of Home Assistant Core has the issue?

2024.12.5

What was the last working version of Home Assistant Core?

N/A

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ESPHome Builder

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[rsmanning]

I deleted the builder and ESP device instance of the device and recreated the device with a different name but everything after Captive Portal in the yaml is the same. It immediately detected it after manually flashing and booting as the old device name in discovered devices. I restarted HA services and it showed up as the new name discovered. Then I added it in again and now I can reflash via OTA. Please fix this.

[home-assistant]

Hey there @OttoWinter, @jesserockz, @kbx81, @bdraco, mind taking a look at this issue as it has been labeled with an integration (esphome) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of esphome can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign esphome Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

esphome documentation
esphome source
_{^{(message by IssueLinks)}}