Do Z-Wave Devices get randomly named incorrectly after rebooting for anyone else?

About 50% of the time when I reboot either HA (usually due to updates) or the ZWaveJS UI add-on, one of my devices comes back with the wrong name & entity values.

For example, I might have a light called Master Bath Light, with the entity being light.master_bath_light_level (which I renamed due to legacy naming). When I reboot, it might get converted to Master_bathroom_light with the entity being light.master_bathroom_light. (I realize that my name set inside ZWaveJS UI is different, but it can happen if it’s the same name with underscores.)

This is just an example, I have 46 lights & switches, and another 20 Z-Wave entities beyond this. When I reboot, it’s usually just one random light or other sensor that comes back with the wrong name, a changed entity, and no associated area.

It’s an easy fix, so I usually just check for missing entities after a reboot, but I wonder if something is wrong that causes this.

I just updated to the latest HomeAssistant 2022.12.6, running on HaOS 9.3 on an RPi4, with an HUSBZB-1 USB stick. ZWaveJS UI is the latest release, 1.4.0.

Yes. Noticed this too but I’m still in the migration phase so haven’t really dug into it. Every now and then a device would change back to its default name when it was added or just become a “node_xx” entity and I have to figure out which one it is.

It hasn’t happened in the last week though. So I’m hoping something was fixed.

Sadly, it just happened again today. I know I just upgraded to 2022.12.6, I think my last ZWaveJS-UI update was a little while ago.

It’s not the same node each time, either. I’ve definitely caught at least 3 different switches, and one door sensor so far.

I don’t use addon but use docker version and this has never been issue.

Device and entity name should only change if removed and readded to zwavejs or HA.

Removal from zwavejs may result in new device name which will cause new HA entity to be created

Removal of entity from HA may cause it to be readded as a new device and entity, i forget if it is device or entity removal that cause this but it is possible.

I expect something else is causing this and simple reboot is not actual cause.

Did you reinterview device? Maybe you have some network issue and reinterview but poor network condition prevent communication. Later the interview completed and full name come through and HA add that. This problem not normal result either.

This is what I was thinking maybe happened. They didn’t fully get added and after the reboot or at the next wake up they finished reporting in and it updated. I usually notice that they are missing configuration parameters and stuff and do a full reinterview and get them cleaned up. But this would make sense.

Happens for me when during renaming there’s an error for the recorder because of older data and it’s queued for restoring the name it seems.

If you want to try to help diagnose the issue:
https://github.com/home-assistant/core/issues/80398#issuecomment-1327018758

My theory is that the the firmware update checks that happen at most once a day are causing the issue.