Z-Wave JS entities renamed/reset

[TarheelGrad1998]

trafficstars

The problem

I have renamed some of the Z-Wave sensor entities to make them easier to remember and work with. Now on at least 3 occasions, these entities have been reset to their original name and properties as they would be upon import. This causes automations to fail because they are referencing, for example, binary_sensor.basement_door and not the default like binary_sensor.basement_door_window_is_open. All 3 cases where this has happened are with Ecolink DWZWAVE25 sensors, but this may be a coincidence. The last time this happened I also noticed that the icon and show as values were reset as well. I am running 2023.2 but I know this has happened before I updated to this version as well

What version of Home Assistant Core has the issue?

2023.2.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Z-Wave JS

Link to integration documentation on our website

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

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 @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zwave_js 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 zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[kpine]

Probably a duplicate of #80398. If that's the case, we will need extensive debug info to diagnose.

1. Driver debug logs, capturing the time window of the incident
2. HA integration debug logs
3. Before and after device diagnostic data

See comment https://github.com/home-assistant/core/issues/80398#issuecomment-1327018758 for points 2 and 3.

If you are using the Z-Wave JS add-on, you'll have to switch to Z-Wave JS UI to capture driver logs. The official add-on does not provide any way to get historical driver logs. ZUI will capture 7 days of downloadable log files which would hopefully capture the time of the incident. Be sure to set Debug level.

https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs

One theory is related to querying for manufacturer info, which is performed during HA startup (I believe at most once per day). If you want to proactively monitor driver logs, you can try watching for changes to the manufacturer information, for example:

2022-11-26T01:11:14.724Z CNTRLR   [Node 105] [~] [Manufacturer Specific] manufacturerId: 3854 => 63 [Endpoint 0]
                                  4
2022-11-26T01:11:14.739Z CNTRLR   [Node 105] [~] [Manufacturer Specific] productType: 257 => 257    [Endpoint 0]
2022-11-26T01:11:14.748Z CNTRLR   [Node 105] [~] [Manufacturer Specific] productId: 54 => 54        [Endpoint 0]

[TarheelGrad1998]

I've attached what I can get, hopefully this is helpful.

Of course I do not have before and after. The last time I noticed it happen was for binary_sensor.david_chair. I noticed it Friday (3/10) so I suspect it happened 3/9 or 3/10 but it's hard to say for sure.

I'll keep an eye out and will report more if it happens again.

zwave js debug.txt diagnostics.txt integration diagnostics.txt

[TarheelGrad1998]

This happened to me again yesterday. This time it clearly happened after a HA restart, and I noticed it right away as the sensor is used to alter display on my dashboard, and I had just verified all my entities were properly named after the last issue. This time it was a Zooz ZSE41 sensor, so at least it's not the brand of sensor. But it was only that sensor entity that got renamed.

[TarheelGrad1998]

So I rebooted prepping to upgrade to 2023.3 and it renamed this same entity again (binary_sensor.becca_door => binary_sensor.becca_bed_door_window_is_open or something like that). So I fixed that entity, and downloaded the device log (attached).
device_diag_good.txt

Then I proceeded to enable the Zwave JS log and upgrade HA and...now it did not rename this, nor any other entity as far as I can tell. Maybe I got lucky and it's fixed in the latest Zwave JS and HA. We shall see.

[johanschelin]

Yes this is a duplicate and should perhaps be continued in #80398 ?

[MartinHjelmare]

Duplicate of https://github.com/home-assistant/core/issues/80398