Friendly names switch to names and back

[supaeasy]

The problem

I am running ESPHome 2024.3.1. I have several Athom Smart Plugs V2. I adopted them via ESPhome and gave them friendly names. This worked very fine for several weeks. However since two or three days 20234.3.3 friendly names are not being used for all the devices, not all the time.

The problem was spreading: One or two days ago I noticed that one plug was suddenly showing name instead of friendly name, others followed without action from my side. Out of 11 Plugs right now 2 are showing friendly names (e.g. in the energy dashboard or in badges) and the others are shown with their name (e.g. athom.smart-plug-v2-8af69d). I didnt't change any configuration or naming settings. Everything displays correctly in ESPHome, friendly names are being shown in a large font at the top of the card, Names below that. All of the devices are configured 100% the same. The two devices that are still presented with their friendly name are neither the oldest nor the most recently added ones. What comes to mind is that I didn't give the devices static IPs. Is naming bound to IPs at initial configuration? Restarting ESPHome does not help. Restarting Home Assistant resolved this for now.

What version of Home Assistant Core has the issue?

core-2024.4.0

What was the last working version of Home Assistant Core?

core-2024.3.2

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

esphome

Link to integration documentation on our website

https://www.home-assistant.io/integrations/esphome/

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

[home-assistant[bot]]

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)}}

[supaeasy]

I have been monitoring this. IP addresses didn't change even though they are not static. My DHCP seems to have some sort of «soft» reservation so even when leases renew they stay the same. But what is also temporarily fixing this issue is to restart the plug in question. So this is weird.

[supaeasy]

Fixed IPs didn't solve it at all.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.