Why suddenly "Entity not available"

[KTA2222 (kta)]

Hello everyone,

I’ve been running my Home Assistant setup successfully for some time, but recently I encountered an issue:
I’m now receiving the error message “Entity not available”, and the corresponding value is no longer displayed in the dashboard.

After investigating, I checked the Edit Card section and noticed that the entity name shown there is different from the one I originally configured. It seems that the entity ID may have changed unexpectedly, which could explain why the value is no longer displayed.

Has anyone experienced something similar or have any insights into why this might happen?
I’ve attached some screenshots for reference.

Thanks in advance for your help!

[Didgeridrew]

There was some discussion about this regarding ESPHome devices in the 2025.5 Release Notes thread:

2025.5: Two Million Strong and Getting Better

This update screwed all my dashboards. As friendly_name now contains device_name !! So my dashboard went from: [441765452-eeb4dd23-0211-41ce-ba62-25400be99c55] to: [441765588-7dacc2e8-94a3-4662-a815-9f85d6cc7f8d] How to fix it??? Also see: device_name prefix added to friendly_name label in Prometheus metrics · Issue #144445 · home-assistant/core · GitHub Discord

You may want to take a look at:

HA 2025.5 ESPHome device names now on frontend

Here’s what I posted on discord. This will allow you to retain your entity names when upgrading to 2025.5 from any previous version. (only do this if you updated to 2025.5 already) Downgrade to 2025.4 Run this in template editor {%- for e in integration_entities('esphome') %} {{ e }}: friendly_name: "{{ state_attr(e, 'friendly_name') }}" {%- endfor %} Add results from template editor into to customize.yaml Add the following to configuration.yaml if you have never customized entitie…

[francisp (Francis)]

See if there is an entity with the same ID as the old one, but with _2 attached.

[KTA2222 (kta)]

I have 2 different esp32 than the rest (of 3). On these 2 different ESP32 I’ve got this issue.