Dead (unpingable) Z-Wave nodes names disappear in dashboard #156165
Description
The problem
Once a Z-wave node become unpingable, device name disappears from the dashboard. See first entry below
What version of Home Assistant Core has the issue?
2025.11.1
What was the last working version of Home Assistant Core?
N/A
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Z-Wave JS with Z-Wave JS UI add-on
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zwave_js/
Diagnostics information
I attached the diagnostics file for the device, which is a Zooz ZEN76 800LR, paired in LR mode with the ZWA2. This is an intermittent problem.
I originally filed the following issue at #132782 . I closed it because I could no longer reproduce it with my devices at the time.
Unfortunately, I'm seeing this again. I was unable to reopen the original issue, and thus am refiling it.
As mentioned in the description above, the entry shows blank in the dashboard when the device is offline.
When I click on it, I see :
This entity is no longer being provided by the zwave_js integration. If the entity is no longer in use, delete it in settings.
This screenshot shows it became unavailable at 13:06:43 . This corresponds to the time that I restarted the Z-Wave JS UI add-on after an upgrade. The specific device did not come back online after the restart.
The device info screen shows the following :
The last relevant entry for this device, in the Z-Wave JS log Node 259, is
2025-11-08 13:07:23.882 DRIVER » [Node 259] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x01
│ callback id: 64
└─[NoOperationCC]
2025-11-08 13:07:23.883 SERIAL » 0x010f00a90001010301000100000000401a (17 bytes)
2025-11-08 13:07:23.897 SERIAL « [ACK] (0x06)
2025-11-08 13:07:23.899 SERIAL « 0x010401a90152 (6 bytes)
2025-11-08 13:07:23.902 SERIAL » [ACK] (0x06)
2025-11-08 13:07:23.902 DRIVER « [RES] [SendDataBridge]
was sent: true
2025-11-08 13:07:24.000 SERIAL « 0x011d00a94001000a007f7f7f7f7f000301000000000403000009a47f7f7fa8 (31 bytes)
2025-11-08 13:07:24.001 SERIAL » [ACK] (0x06)
2025-11-08 13:07:24.002 DRIVER « [REQ] [SendDataBridge]
callback id: 64
transmit status: NoAck, took 100 ms
routing attempts: 3
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Direct
TX channel no.: 3
TX power: 9 dBm
measured noise floor: -92 dBm
2025-11-08 13:07:24.002 CNTRLR [Node 259] The node did not respond after 1 attempts, it is presumed dead
2025-11-08 13:07:24.002 CNTRLR [Node 259] The node is dead.
2025-11-08 13:07:24.003 CNTRLR [Node 259] ping failed: The node did not acknowledge the command (ZW0204)
I am also attaching today's full Z-Wave JS log up to the node going dead, so you can see previous entries.
I then manually pinged the node through Z-Wave JS UI. The first ping failed. But the second ping succeeded. Here are the log entries .
2025-11-08 15:11:56.691 CNTRLR » [Node 259] pinging the node...
2025-11-08 15:11:56.693 DRIVER one or more queues busy
2025-11-08 15:11:56.693 DRIVER » [Node 259] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x01
│ callback id: 252
└─[NoOperationCC]
2025-11-08 15:11:56.693 SERIAL » 0x010f00a90001010301000100000000fca6 (17 bytes)
2025-11-08 15:11:56.912 SERIAL « [ACK] (0x06)
2025-11-08 15:11:56.914 SERIAL « 0x010401a90152 (6 bytes)
2025-11-08 15:11:56.916 SERIAL » [ACK] (0x06)
2025-11-08 15:11:56.917 DRIVER « [RES] [SendDataBridge]
was sent: true
2025-11-08 15:11:56.988 SERIAL « 0x011d00a9fc010007007f7f7f7f7f00030100000000040300000ea37f7f7f19 (31 bytes)
2025-11-08 15:11:56.989 SERIAL » [ACK] (0x06)
2025-11-08 15:11:56.989 DRIVER « [REQ] [SendDataBridge]
callback id: 252
transmit status: NoAck, took 70 ms
routing attempts: 3
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Direct
TX channel no.: 3
TX power: 14 dBm
measured noise floor: -93 dBm
2025-11-08 15:11:56.990 CNTRLR [Node 259] The node did not respond after 1 attempts, it is presumed dead
2025-11-08 15:11:56.991 CNTRLR [Node 259] ping failed: The node did not acknowledge the command (ZW0204)
2025-11-08 15:11:56.991 DRIVER all queues idle
2025-11-08 15:11:59.006 CNTRLR » [Node 259] pinging the node...
2025-11-08 15:11:59.007 DRIVER one or more queues busy
2025-11-08 15:11:59.008 DRIVER » [Node 259] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x01
│ callback id: 253
└─[NoOperationCC]
2025-11-08 15:11:59.008 SERIAL » 0x010f00a90001010301000100000000fda7 (17 bytes)
2025-11-08 15:11:59.017 SERIAL « [ACK] (0x06)
2025-11-08 15:11:59.019 SERIAL « 0x010401a90152 (6 bytes)
2025-11-08 15:11:59.019 SERIAL » [ACK] (0x06)
2025-11-08 15:11:59.020 DRIVER « [RES] [SendDataBridge]
was sent: true
2025-11-08 15:11:59.034 SERIAL « 0x011d00a9fd00000100a77f7f7f7f03030100000000040100000ea30eae9881 (31 bytes)
2025-11-08 15:11:59.035 SERIAL » [ACK] (0x06)
2025-11-08 15:11:59.035 DRIVER « [REQ] [SendDataBridge]
callback id: 253
transmit status: OK, took 10 ms
routing attempts: 1
protocol & route speed: Z-Wave Long Range, 100 kbit/s
routing scheme: Direct
ACK RSSI: -89 dBm
ACK channel no.: 3
TX channel no.: 3
TX power: 14 dBm
measured noise floor: -93 dBm
ACK TX power by destination: 14 dBm
measured RSSI of ACK from destination: -82 dBm
measured noise floor by destination: -104 dBm
2025-11-08 15:11:59.036 CNTRLR [Node 259] The node is now alive.
2025-11-08 15:11:59.038 CNTRLR [Node 259] The node is ready to be used
2025-11-08 15:11:59.066 CNTRLR « [Node 259] ping successful
Once the node was alive, I went back to the dashboard, and the device reappeared.
On a separate note, this device goes dead relatively frequently. I have no idea what causes this. There are switches of the same model in nearby wall boxes - within 10ft - and those don't go dead. The switch was also replaced - it used to be a ZEN76 700 series, non-LR, and had major problems as well. It seems there is something location related with the signal. The wall box is about 2 inches from a granite countertop backsplash. But so are the other nearby switches - albeit on a different wall. Even switching from the ZST39 to the ZWA2, this problem did not go away, unfortunately.
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response