I have/had a working Zwave setup in HA, basically 4 doors and a zwave stick.
After a recent update, i noticed two behaviors:
- all battery based zwave devices report as “dead” until the device (door) is opened
- when HA sends a command to a device (ie “open door”) then the devices reports as “unavailabe”
Zwave JS UI log shows a number of these lines when I manually operate the door.
2024-12-31T01:10:04.915Z CNTRLR [Node 009] in the process of replying to a NonceGet, won’t send another NonceR
When I use HA webUI to unlock a door i see:
2024-12-30 17:12:20.888 INFO Z-WAVE: [Node 009] Is now dead
2024-12-31T01:12:20.889Z CNTRLR [Node 009] The node is now dead.
2024-12-30 17:12:20.892 ERROR Z-WAVE-SERVER: The node did not acknowledge the command (ZW0204)
ZWaveError: The node did not acknowledge the command (ZW0204)
at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:6059:23)
at Driver.sendCommandInternal (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:6259:28)
at Driver.sendCommand (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:6377:29)
at Proxy.set (/opt/node_modules/@zwave-js/cc/src/cc/DoorLockCC.ts:542:20)
at Proxy.set (/opt/node_modules/@zwave-js/cc/src/cc/DoorLockCC._validateArgs.ts:10:30)
at Proxy. (/opt/node_modules/@zwave-js/cc/src/cc/DoorLockCC.ts:372:31)
at ZWaveNode2.setValue (/opt/node_modules/zwave-js/src/lib/node/Node.ts:665:39)
at NodeMessageHandler.handle (/opt/node_modules/@zwave-js/server/dist-esm/lib/node/message_handler.js:23:43)
at Client.receiveMessage (/opt/node_modules/@zwave-js/server/dist-esm/lib/server.js:133:100)
at WebSocket. (/opt/node_modules/@zwave-js/server/dist-esm/lib/server.js:54:45)
eport
HA Software details
- Core 2024.12.5
- Supervisor 2024.12.0
- Operating System 14.1
- Frontend 20241127.8
Zwave
- zwave-js-ui: 9.27.8
- zwave-js: 14.3.7
- device setup via /dev/ttyACM0
/dev/serial/by-id/usb-0658_0200-if00