Skip to content

Zwave JS - While using "Recreate entity IDs" found entity being changed that inherited name of an unrelated device #4782

Description

@alexruffell

Describe the issue you are experiencing

EDIT: I re-added an old Z-Wave open/close sensor to my network after it had been unused for several years.

While cleaning up its entity names, I used Recreate entity IDs and noticed that Home Assistant wanted to rename only one entity. The proposed entity ID referred to a completely unrelated device, Game Room Landing Light, rather than the device I was working on, Utility Room Freezer Door.

After investigating further, it appears that Recreate entity IDs is not the cause of the problem. The underlying issue is that one of the newly added door sensor's entities already had an incorrect default entity ID:

sensor.game_room_landing_light_rssi

This RSSI entity belongs to the Utility Room Freezer Door sensor, but its entity ID appears to have inherited the name of the unrelated Game Room Landing Light device.

Utility Room Freezer Door

Utility Room Freezer Door entities

Game Room Landing Light

Game Room Landing Light entities

Incorrect RSSI entity ID

RSSI entity with incorrect entity ID

It is possible that these two devices used the same Z-Wave node ID at different times, since the door sensor had been removed from the network for several years. I do not know whether node ID reuse is relevant to the issue.

I am fairly certain I have seen similar incorrect entity naming several times in the past, although I had not previously reported it.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which app are you reporting an issue with?

Z-Wave JS

What is the version of the app?

7.4.0

Steps to reproduce the issue

These are the steps I followed. I do not yet know which steps are necessary to reproduce the problem.

  1. Add or re-add a Z-Wave device.
  2. Rename some of its entities for consistency, for example changing "Battery level" to "Battery".
  3. Remove the area name from the device name. (my devices already include that, and using the new method introduces usability issues)
  4. Select Recreate entity IDs.
  5. Review the proposed entity ID changes.

In my case, the only proposed change was for the RSSI entity, and its existing entity ID contained the name of a completely unrelated Z-Wave device.

System Health information

System Information

version core-2026.8.2
installation_type Home Assistant OS
dev false
hassio true
docker true
container_arch amd64
user root
virtualenv false
python_version 3.14.6
os_name Linux
os_version 6.18.39-haos
arch x86_64
timezone America/Chicago
config_dir /config
Home Assistant Cloud
logged_in true
subscription_expiration 9 August 2027 at 19:00
relayer_connected true
relayer_region us-east-1
remote_enabled true
remote_connected true
remote_server us-east-1-2.ui.nabu.casa
alexa_enabled true
google_enabled true
cloud_ice_servers_enabled true
certificate_status ready
instance_id a6d947aebda7477fb701d7d792da3b0c
iot_state connected
iot_tries 0
certificate_expire_date 4 November 2026 at 22:20
certificate_fingerprint c8be6aeb064bc819373b46e75ec3e818d5a6a9e7
certificate_alternative_names undefined
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
HACS
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.5
Stage running
Available Repositories 3997
Downloaded Repositories 75
Home Assistant Supervisor
host_os Home Assistant OS 18.2
update_channel beta
supervisor_version supervisor-2026.07.5
agent_version 1.10.0
docker_version 29.6.2
disk_total 251.3 GB
disk_used 140.9 GB
nameservers 10.1.0.51, 10.1.0.50
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization kvm
board ova
supervisor_api ok
version_api ok
installed_addons openWakeWord (2.1.1), Node-RED (22.0.1), Home Assistant Google Drive Backup (0.112.1), Piper (2.3.2), Z-Wave JS UI (7.4.0), Whisper (3.5.1), InfluxDB (5.0.2), Glances (0.22.0), Grafana (12.1.0), SQLite Web (6.0.1), Advanced SSH & Web Terminal (24.0.1), ESPHome Device Builder (beta) (2026.8.0b3), ESPHome Device Builder (2026.7.4), Matter Server (9.2.0), Studio Code Server (6.0.1), Samba share (12.10.0), OpenThread Border Router (3.1.0), Music Assistant (2.9.13), Grocy (0.25.1)
Dashboards
dashboards 6
resources 49
views 57
mode storage
Network Configuration
adapters lo (disabled), enp6s18 (enabled, default, auto), docker0 (disabled), hassio (disabled), vethd87d3e6 (disabled), veth97e0cd2 (disabled), vethdae52f6 (disabled), vethbc199b1 (disabled), vethc960ca6 (disabled), veth6d952ae (disabled), vethe22d1c6 (disabled), veth0cdea14 (disabled), veth4bedc33 (disabled), veth5444e2a (disabled), wpan0 (disabled), veth1924d59 (disabled), veth42941a9 (disabled), vetha424f13 (disabled), vethfdaf50b (disabled), vethcfaa906 (disabled), vethd61b292 (disabled)
ipv4_addresses lo (127.0.0.1/8), enp6s18 (10.1.1.41/23), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), vethd87d3e6 (), veth97e0cd2 (), vethdae52f6 (), vethbc199b1 (), vethc960ca6 (), veth6d952ae (), vethe22d1c6 (), veth0cdea14 (), veth4bedc33 (), veth5444e2a (), wpan0 (), veth1924d59 (), veth42941a9 (), vetha424f13 (), vethfdaf50b (), vethcfaa906 (), vethd61b292 ()
ipv6_addresses lo (::1/128), enp6s18 (fd00:1:1:1:96f0:d86:b8a7:27f1/64, fe80::750b:dc8c:be09:57ba/64), docker0 (fde1:e81b:9459::1/64, fe80::94:afff:fe7d:4ae4/64), hassio (fd0c:ac1e:2100::1/48, fe80::a821:9bff:fe7d:fc82/64), vethd87d3e6 (fe80::6c4a:1ff:fe28:e3da/64), veth97e0cd2 (fe80::c8ef:56ff:fe52:dc11/64), vethdae52f6 (fe80::c82e:93ff:fec4:435f/64), vethbc199b1 (fe80::38b5:2fff:fedc:93b1/64), vethc960ca6 (fe80::7cfc:dcff:fea2:87c2/64), veth6d952ae (fe80::587d:caff:fe5b:b53/64), vethe22d1c6 (fe80::54d0:c1ff:fee9:7480/64), veth0cdea14 (fe80::44c9:3bff:feae:affb/64), veth4bedc33 (fe80::183b:78ff:fe73:59c3/64), veth5444e2a (fe80::c9c:2aff:fe89:a118/64), wpan0 (fd76:7efe:a92b:d31f:0:ff:fe00:fc11/64, fd36:a1a3:e7b8:1:c55:9f5b:6e45:47c8/64, fd76:7efe:a92b:d31f:0:ff:fe00:fc38/64, fd76:7efe:a92b:d31f:0:ff:fe00:fc10/64, fd76:7efe:a92b:d31f:0:ff:fe00:a800/64, fd76:7efe:a92b:d31f:c09c:7e26:9f01:fa97/64, fe80::204c:a330:2f27:7a14/64), veth1924d59 (fe80::38e0:5dff:fe38:2886/64), veth42941a9 (fe80::90bd:cfff:fec6:25d3/64), vetha424f13 (fe80::6489:daff:fe6d:ecd7/64), vethfdaf50b (fe80::2886:dfff:fef5:286b/64), vethcfaa906 (fe80::902c:daff:fe88:4efd/64), vethd61b292 (fe80::4ce6:34ff:fe92:d85e/64)
announce_addresses 10.1.1.41, fd00:1:1:1:96f0:d86:b8a7:27f1, fe80::750b:dc8c:be09:57ba
Recorder
oldest_recorder_run 4 August 2026 at 19:35
current_recorder_run 14 August 2026 at 17:04
estimated_db_size 4688.34 MiB
database_engine sqlite
database_version 3.53.2
Spotify
api_endpoint_reachable ok
Victor Smart-Kill
api_endpoint_reachable ok
WiiM
configured_devices 7
reachable_devices 3/3
multiroom_masters 0
multiroom_slaves 0
first_device_api OK (polling: 5.0s)
integration_version 2.0.0
pywiim_version 2.3.0
Xiaomi Miot
component_version 1.1.4
can_reach_server ok
can_reach_spec ok
logged_accounts 1
total_devices 1

Anything in the Supervisor logs that might be useful for us?

Anything in the app logs that might be useful for us?

Additional information

Expected behavior

Entities created for a newly added or re-added Z-Wave device should receive entity IDs based on that device's current name or identity and should not inherit names associated with unrelated devices that may previously have used the same node ID.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions