Z-Wave JS Firmware Update Causes Duplicate Entity IDs

[matthewcbyington]

The problem

Hi there,

I’m using Z-Wave JS and have 30 devices connected.

Around 10 of those devices are Aeotec’s ZWA023 smart plugs.

This past week, there was a firmware update that Z-Wave JS reported, from 1.3.1 to 1.3.2.

I executed the update on all the devices.

I noticed that all of the sensor entity IDs (voltage, watts, amps, etc) were duplicated. The existing entity ID (e.g. christmas_tree_electric_consumption_a) showed as UNAVAILABLE and a new entity ID christmas_tree_electric_consumption_a_2 was created for each one.

This messed up all of my automations.

I was able to mass-delete the old entity IDs via the GUI (nice to have the new filter options).

But now I’m left with around 100 incorrect entity IDs, suffixed with “_2”.

a) Anyone else have this issue? b) What’s the fastest way for me to fix it without having to painfully update each one? c) Anything I could do better to avoid this?

Cheers. Matt

What version of Home Assistant Core has the issue?

2024.7.2

What was the last working version of Home Assistant Core?

2024.7.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Z-Wave JS

Link to integration documentation on our website

No response

Diagnostics information

config_entry-zwave_js-0ef36ac2e64dbd6d7ba3396b8da2d94d.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[davidlsparks]

Seeing the same thing here. Seem to start after the latest Zwave JS UI update: 3.8.5

Driver version: 12.12.4 Server version: 1.36.0

[p3nguin53]

This is my 1st comment on an existing Issue so please let me know if I should also be posting about my Rename error messages somewhere else. (Edited to note that I found existing issue # 114559 for the migrate error and community advice for the rename error)

I experienced the same problem as above when updating my ZWA023 smart plug firmware. The UNAVAILABLE entities also affected my dashboard.

I successfully deleted the Unavailable entities and renamed the _2 entities to remove the _2 which fixed the dashboard. But then I found the following 2 error messages in the log:

Logger: homeassistant.components.recorder.table_managers.statistics_meta Source: components/recorder/table_managers/statistics_meta.py:312 integration: Recorder (documentation, issues) First occurred: 3:02:46 PM (4 occurrences) Last logged: 3:05:49 PM

Cannot rename statistic_id sensor.workshop_plug_1_electric_consumption_a_2 to sensor.workshop_plug_1_electric_consumption_a because the new statistic_id is already in use Cannot rename statistic_id sensor.workshop_plug_1_electric_consumption_kwh_2 to sensor.workshop_plug_1_electric_consumption_kwh because the new statistic_id is already in use Cannot rename statistic_id sensor.workshop_plug_1_electric_consumption_v_2 to sensor.workshop_plug_1_electric_consumption_v because the new statistic_id is already in use Cannot rename statistic_id sensor.workshop_plug_1_electric_consumption_w_2 to sensor.workshop_plug_1_electric_consumption_w because the new statistic_id is already in use

Logger: homeassistant.components.recorder.entity_registry Source: components/recorder/entity_registry.py:76 integration: Recorder (documentation, issues) First occurred: July 10, 2024 at 2:47:59 PM (25 occurrences) Last logged: 3:06:36 PM

Cannot migrate history for entity_id sensor.workshop_plug_1_electric_consumption_a_2 to sensor.workshop_plug_1_electric_consumption_a because the new entity_id is already in use Cannot migrate history for entity_id sensor.workshop_plug_1_electric_consumption_kwh_2 to sensor.workshop_plug_1_electric_consumption_kwh because the new entity_id is already in use Cannot migrate history for entity_id sensor.workshop_plug_1_electric_consumption_v_2 to sensor.workshop_plug_1_electric_consumption_v because the new entity_id is already in use Cannot migrate history for entity_id sensor.workshop_plug_1_electric_consumption_w_2 to sensor.workshop_plug_1_electric_consumption_w because the new entity_id is already in use Cannot migrate history for entity_id switch.workshop_plug_1_2 to switch.workshop_plug_1 because the new entity_id is already in use

Running Home Assistant Core OS 2024.6.4 Z-Wave JS 0.6.2

[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. - `@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)}}

---

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

[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.

[davidlsparks]

I am no longer seeing this issue.