In z2m - "Update Home Assistant entity ID" stoped working😟

Hi all,

I have a setup with 2 z2m add-on installs

  • a sonooff, usbstick v3
  • a SMLIGHT SLZB-06, rj45 connected

I installed the SMLIGHT SLZB-06 because i wanted to move to a rj45 connected setup because my sonoff is getting quite unstabel.

the SMLIGHT is SUPER stable (11 months) - it never drops connections and is just easy to work with.

Problem:
I have slowly been migrating my 60+ entities from sonoff to SML a few at a time - when I had the time - THIS HAS BEEN WORKING WELL.

Now suttenly when i remove an entity from sonoff (force remove + block rejoin) - connects it to SML, renames it to the original name in z2m incl the “Update Home Assistant entity ID” tickmark - the entity is no longer updated in HA. It does get the new z2m name as friendly name, but the entity (light.0x680…) does not change (see image below.

image

This did not use to be the case - maybe there is some update to home assistant or z2m where I have missed this in the release notes (i looked).

If anybody has a workaround i would higly appriciate it.

I use the ‘old’ entity name in a lot of places - buttons, templates, automations etc.

regards

Rename to the friendly name with a _ added, then rename again to the driendly name. Both times with “Update Home Assistant entity ID” tickmark

I have it sometimes too, and this helps.

THanks for reaching out - I already did this - but now im gonna do it again :smirk:

hold on

Edit:

just tried again - looks like HA Updates the friendly name - even without the tickmark. tested a few times back and forth with the tickmark incl restarts. The entity name stayes the same :unamused: - only the friendly name changes

I think this was introduced in 2025.7.0.

Supposedly fixed (I think in 7.2): Fix entity_id should be based on object_id the first time an entity is added by jbouwh · Pull Request #148484 · home-assistant/core.

If you’re on 7.0 - 7.2, upgrade and test.

I’m not on 7.x yet, so no idea if the fix works.

ur the best - went from 7.1–> 7.3 and problem solved😏.

i normally go though these release notes, but i could not see anything this time.

thanks for the assistance.

/