zwave-js keeps restarting. I don’t know what changed or what is causing it, so I was hoping posting logs here might help. It’s been working fine for a few months now.
My controller is the nabu casa one, the ZWA-2
I see a lot of stuff about node 17. How do I ID what node that is, and is that what is causing the issue maybe?
2025-12-07 21:09:43.781 CNTRLR » [Node 016] pinging the node...
2025-12-07 21:09:43.785 CNTRLR » [Node 012] pinging the node...
2025-12-07 21:09:43.793 CNTRLR [Node 002] The node is asleep.
2025-12-07 21:09:43.796 CNTRLR [Node 002] The node is ready to be used
2025-12-07 21:09:43.798 CNTRLR [Node 019] The node is asleep.
2025-12-07 21:09:43.799 CNTRLR [Node 019] The node is ready to be used
2025-12-07 21:09:43.801 CNTRLR [Node 008] The node is asleep.
2025-12-07 21:09:43.803 CNTRLR [Node 008] The node is ready to be used
2025-12-07 21:09:43.805 CNTRLR [Node 006] The node is asleep.
2025-12-07 21:09:43.806 CNTRLR [Node 006] The node is ready to be used
2025-12-07 21:09:43.808 CNTRLR [Node 022] The node is asleep.
2025-12-07 21:09:43.810 CNTRLR [Node 022] The node is ready to be used
2025-12-07 21:09:43.811 CNTRLR [Node 009] The node is asleep.
2025-12-07 21:09:43.813 CNTRLR [Node 009] The node is ready to be used
2025-12-07 21:09:43.814 CNTRLR [Node 020] The node is asleep.
2025-12-07 21:09:43.815 CNTRLR [Node 020] The node is ready to be used
2025-12-07 21:09:43.817 CNTRLR [Node 003] The node is asleep.
2025-12-07 21:09:43.818 CNTRLR [Node 003] The node is ready to be used
2025-12-07 21:09:43.820 CNTRLR [Node 025] The node is asleep.
2025-12-07 21:09:43.822 CNTRLR [Node 025] The node is ready to be used
2025-12-07 21:09:43.824 CNTRLR [Node 005] The node is asleep.
2025-12-07 21:09:43.825 CNTRLR [Node 005] The node is ready to be used
2025-12-07 21:09:43.826 CNTRLR [Node 007] The node is asleep.
2025-12-07 21:09:43.828 CNTRLR [Node 007] The node is ready to be used
2025-12-07 21:09:43.829 CNTRLR [Node 018] The node is asleep.
2025-12-07 21:09:43.830 CNTRLR [Node 018] The node is ready to be used
2025-12-07 21:09:43.833 CNTRLR [Node 021] The node is asleep.
2025-12-07 21:09:43.834 CNTRLR [Node 021] The node is ready to be used
21:09:43.843 SERVER ZwaveJS server listening on <all interfaces>:3000
2025-12-07 21:09:43.885 CNTRLR [Node 010] The node is alive.
2025-12-07 21:09:43.886 CNTRLR [Node 010] The node is ready to be used
2025-12-07 21:09:43.889 CNTRLR « [Node 010] ping successful
2025-12-07 21:09:43.917 CNTRLR [Node 027] The node is alive.
2025-12-07 21:09:43.918 CNTRLR [Node 027] The node is ready to be used
2025-12-07 21:09:43.920 CNTRLR « [Node 027] ping successful
2025-12-07 21:09:43.950 CNTRLR [Node 011] The node is alive.
2025-12-07 21:09:43.951 CNTRLR [Node 011] The node is ready to be used
2025-12-07 21:09:43.953 CNTRLR « [Node 011] ping successful
2025-12-07 21:09:43.982 CNTRLR [Node 017] The node is alive.
2025-12-07 21:09:43.983 CNTRLR [Node 017] The node is ready to be used
2025-12-07 21:09:43.985 CNTRLR « [Node 017] ping successful
2025-12-07 21:09:45.378 CNTRLR [Node 013] The node is alive.
2025-12-07 21:09:45.379 CNTRLR [Node 013] The node is ready to be used
2025-12-07 21:09:45.382 CNTRLR « [Node 013] ping successful
2025-12-07 21:09:46.610 CNTRLR [Node 015] The node is alive.
2025-12-07 21:09:46.611 CNTRLR [Node 015] The node is ready to be used
2025-12-07 21:09:46.613 CNTRLR « [Node 015] ping successful
2025-12-07 21:09:47.833 CNTRLR [Node 014] The node is alive.
2025-12-07 21:09:47.834 CNTRLR [Node 014] The node is ready to be used
2025-12-07 21:09:47.836 CNTRLR « [Node 014] ping successful
2025-12-07 21:09:49.052 CNTRLR [Node 016] The node is alive.
2025-12-07 21:09:49.053 CNTRLR [Node 016] The node is ready to be used
2025-12-07 21:09:49.059 CNTRLR « [Node 016] ping successful
2025-12-07 21:09:50.293 CNTRLR [Node 012] The node is alive.
2025-12-07 21:09:50.294 CNTRLR [Node 012] The node is ready to be used
2025-12-07 21:09:50.295 CNTRLR All nodes are ready to be used
2025-12-07 21:09:50.299 CNTRLR « [Node 012] ping successful
2025-12-07 21:10:33.178 DRIVER Dropping message with invalid payload
2025-12-07 21:10:34.967 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:11:03.033 DRIVER Dropping message with invalid payload
2025-12-07 21:11:04.788 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:11:35.148 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:11:35.167 DRIVER Dropping message with invalid payload
2025-12-07 21:12:14.743 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:12:14.791 DRIVER Dropping message with invalid payload
2025-12-07 21:12:16.977 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:12:48.925 CNTRLR « [Node 018] received wakeup notification
2025-12-07 21:12:48.927 CNTRLR [Node 018] The node is now awake.
2025-12-07 21:12:49.180 CNTRLR » [Node 018] Sending node back to sleep...
2025-12-07 21:12:49.733 CNTRLR [Node 018] The node is now asleep.
21:14:25.829 SERVER [ERROR] Z-Wave error
2025-12-07 21:15:02.901 DRIVER Dropping message with invalid payload
2025-12-07 21:15:04.702 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:15:04.747 DRIVER Dropping message with invalid payload
2025-12-07 21:15:35.421 DRIVER Dropping message with invalid payload
2025-12-07 21:15:39.795 DRIVER Dropping message with invalid payload
2025-12-07 21:15:39.911 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:16:35.553 DRIVER Dropping message with invalid payload
2025-12-07 21:16:40.041 DRIVER Dropping message with invalid payload
2025-12-07 21:16:40.157 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:09:43.399 CNTRLR [Node 025] Embedded device config loaded
2025-12-07 21:09:43.430 CNTRLR [Node 027] Embedded device config loaded
2025-12-07 21:09:43.469 CNTRLR [Node 001] Embedded device config loaded
2025-12-07 21:09:43.576 CNTRLR Interview completed
21:09:43.610 SERVER driver ready - starting server
2025-12-07 21:09:43.638 CNTRLR [Node 001] The node is alive.
2025-12-07 21:09:43.640 CNTRLR [Node 001] The node is ready to be used
2025-12-07 21:09:43.647 CNTRLR Interviewing nodes and/or determining their status: 10, 27, 11, 17, 13, 15, 14
, 16, 12, 2, 19, 8, 6, 22, 9, 20, 3, 25, 5, 7, 18, 21
2025-12-07 21:09:43.649 CNTRLR » [Node 010] pinging the node...
2025-12-07 21:09:43.753 CNTRLR » [Node 027] pinging the node...
2025-12-07 21:09:43.758 CNTRLR » [Node 011] pinging the node...
2025-12-07 21:09:43.764 CNTRLR » [Node 017] pinging the node...
2025-12-07 21:09:43.768 CNTRLR » [Node 013] pinging the node...
2025-12-07 21:09:43.772 CNTRLR » [Node 015] pinging the node...
2025-12-07 21:09:43.777 CNTRLR » [Node 014] pinging the node...
2025-12-07 21:09:43.781 CNTRLR » [Node 016] pinging the node...
2025-12-07 21:09:43.785 CNTRLR » [Node 012] pinging the node...
2025-12-07 21:09:43.793 CNTRLR [Node 002] The node is asleep.
2025-12-07 21:09:43.796 CNTRLR [Node 002] The node is ready to be used
2025-12-07 21:09:43.798 CNTRLR [Node 019] The node is asleep.
2025-12-07 21:09:43.799 CNTRLR [Node 019] The node is ready to be used
2025-12-07 21:09:43.801 CNTRLR [Node 008] The node is asleep.
2025-12-07 21:09:43.803 CNTRLR [Node 008] The node is ready to be used
2025-12-07 21:09:43.805 CNTRLR [Node 006] The node is asleep.
2025-12-07 21:09:43.806 CNTRLR [Node 006] The node is ready to be used
2025-12-07 21:09:43.808 CNTRLR [Node 022] The node is asleep.
2025-12-07 21:09:43.810 CNTRLR [Node 022] The node is ready to be used
2025-12-07 21:09:43.811 CNTRLR [Node 009] The node is asleep.
2025-12-07 21:09:43.813 CNTRLR [Node 009] The node is ready to be used
2025-12-07 21:09:43.814 CNTRLR [Node 020] The node is asleep.
2025-12-07 21:09:43.815 CNTRLR [Node 020] The node is ready to be used
2025-12-07 21:09:43.817 CNTRLR [Node 003] The node is asleep.
2025-12-07 21:09:43.818 CNTRLR [Node 003] The node is ready to be used
2025-12-07 21:09:43.820 CNTRLR [Node 025] The node is asleep.
2025-12-07 21:09:43.822 CNTRLR [Node 025] The node is ready to be used
2025-12-07 21:09:43.824 CNTRLR [Node 005] The node is asleep.
2025-12-07 21:09:43.825 CNTRLR [Node 005] The node is ready to be used
2025-12-07 21:09:43.826 CNTRLR [Node 007] The node is asleep.
2025-12-07 21:09:43.828 CNTRLR [Node 007] The node is ready to be used
2025-12-07 21:09:43.829 CNTRLR [Node 018] The node is asleep.
2025-12-07 21:09:43.830 CNTRLR [Node 018] The node is ready to be used
2025-12-07 21:09:43.833 CNTRLR [Node 021] The node is asleep.
2025-12-07 21:09:43.834 CNTRLR [Node 021] The node is ready to be used
21:09:43.843 SERVER ZwaveJS server listening on <all interfaces>:3000
2025-12-07 21:09:43.885 CNTRLR [Node 010] The node is alive.
2025-12-07 21:09:43.886 CNTRLR [Node 010] The node is ready to be used
2025-12-07 21:09:43.889 CNTRLR « [Node 010] ping successful
2025-12-07 21:09:43.917 CNTRLR [Node 027] The node is alive.
2025-12-07 21:09:43.918 CNTRLR [Node 027] The node is ready to be used
2025-12-07 21:09:43.920 CNTRLR « [Node 027] ping successful
2025-12-07 21:09:43.950 CNTRLR [Node 011] The node is alive.
2025-12-07 21:09:43.951 CNTRLR [Node 011] The node is ready to be used
2025-12-07 21:09:43.953 CNTRLR « [Node 011] ping successful
2025-12-07 21:09:43.982 CNTRLR [Node 017] The node is alive.
2025-12-07 21:09:43.983 CNTRLR [Node 017] The node is ready to be used
2025-12-07 21:09:43.985 CNTRLR « [Node 017] ping successful
2025-12-07 21:09:45.378 CNTRLR [Node 013] The node is alive.
2025-12-07 21:09:45.379 CNTRLR [Node 013] The node is ready to be used
2025-12-07 21:09:45.382 CNTRLR « [Node 013] ping successful
2025-12-07 21:09:46.610 CNTRLR [Node 015] The node is alive.
2025-12-07 21:09:46.611 CNTRLR [Node 015] The node is ready to be used
2025-12-07 21:09:46.613 CNTRLR « [Node 015] ping successful
2025-12-07 21:09:47.833 CNTRLR [Node 014] The node is alive.
2025-12-07 21:09:47.834 CNTRLR [Node 014] The node is ready to be used
2025-12-07 21:09:47.836 CNTRLR « [Node 014] ping successful
2025-12-07 21:09:49.052 CNTRLR [Node 016] The node is alive.
2025-12-07 21:09:49.053 CNTRLR [Node 016] The node is ready to be used
2025-12-07 21:09:49.059 CNTRLR « [Node 016] ping successful
2025-12-07 21:09:50.293 CNTRLR [Node 012] The node is alive.
2025-12-07 21:09:50.294 CNTRLR [Node 012] The node is ready to be used
2025-12-07 21:09:50.295 CNTRLR All nodes are ready to be used
2025-12-07 21:09:50.299 CNTRLR « [Node 012] ping successful
2025-12-07 21:10:33.178 DRIVER Dropping message with invalid payload
2025-12-07 21:10:34.967 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:11:03.033 DRIVER Dropping message with invalid payload
2025-12-07 21:11:04.788 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:11:35.148 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:11:35.167 DRIVER Dropping message with invalid payload
2025-12-07 21:12:14.743 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:12:14.791 DRIVER Dropping message with invalid payload
2025-12-07 21:12:16.977 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:12:48.925 CNTRLR « [Node 018] received wakeup notification
2025-12-07 21:12:48.927 CNTRLR [Node 018] The node is now awake.
2025-12-07 21:12:49.180 CNTRLR » [Node 018] Sending node back to sleep...
2025-12-07 21:12:49.733 CNTRLR [Node 018] The node is now asleep.
21:14:25.829 SERVER [ERROR] Z-Wave error
2025-12-07 21:15:02.901 DRIVER Dropping message with invalid payload
2025-12-07 21:15:04.702 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:15:04.747 DRIVER Dropping message with invalid payload
2025-12-07 21:15:35.421 DRIVER Dropping message with invalid payload
2025-12-07 21:15:39.795 DRIVER Dropping message with invalid payload
2025-12-07 21:15:39.911 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:16:35.553 DRIVER Dropping message with invalid payload
2025-12-07 21:16:40.041 DRIVER Dropping message with invalid payload
2025-12-07 21:16:40.157 CNTRLR « [Node 017] received S2 nonce without an active transaction, not sure what to d
o with it
2025-12-07 21:17:29.884 DRIVER Dropping message with invalid payload
2025-12-07 21:17:35.914 DRIVER Dropping message with invalid payload
2025-12-07 21:17:36.030 DRIVER Dropping message with invalid payload
2025-12-07 21:17:39.798 DRIVER Dropping message with invalid payload
2025-12-07 21:17:39.881 DRIVER Dropping message with invalid payload
2025-12-07 21:17:39.930 DRIVER Dropping message with invalid payload
2025-12-07 21:17:39.992 DRIVER Dropping message with invalid payload
2025-12-07 21:17:40.208 DRIVER Dropping message with invalid payload
2025-12-07 21:17:40.295 DRIVER Dropping message with invalid payload
2025-12-07 21:17:40.484 DRIVER Dropping message with invalid payload
2025-12-07 21:17:40.756 DRIVER Dropping message with invalid payload
2025-12-07 21:17:42.986 DRIVER Dropping message with invalid payload
2025-12-07 21:17:43.101 DRIVER Dropping message with invalid payload
2025-12-07 21:17:43.898 DRIVER Dropping message with invalid payload
2025-12-07 21:17:43.999 DRIVER Dropping message with invalid payload
2025-12-07 21:17:44.117 DRIVER Dropping message with invalid payload
2025-12-07 21:17:44.193 DRIVER Dropping message with invalid payload
ZWaveError: Security class for node 17 is not yet known! (ZW1402)
at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7116:23)
at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7312:28)
at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:7430:29)
at Proxy.sendReport (file:///usr/src/node_modules/@zwave-js/cc/src/cc/SupervisionCC.ts:98:20)
at reply (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5721:8)
at trySupervised (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5744:12)
at Driver.handleRequest (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5836:4)
at Driver.handleUnsolicitedMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5219:5)
[21:17:51] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/config.sh
[21:18:29] INFO: No 'network_key' detected, setting it to 's0_legacy_key' for backwards compatibility
[21:18:29] INFO: Flushing config to disk due to creation of new key(s)...
[21:18:30] INFO: RF region set to Automatic: Europe
[21:18:30] INFO: Setting RF region to (Europe)
[21:18:30] INFO: Soft-reset set to automatic
[21:18:30] INFO: Virtual Machine not detected, enabling soft-reset
cont-init: info: /etc/cont-init.d/config.sh exited 0
cont-init: info: running /etc/cont-init.d/structure.sh
cont-init: info: /etc/cont-init.d/structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun zwave_js (no readiness notification)
s6-rc: info: service legacy-services successfully started
[21:18:31] INFO: Using device: /dev/serial/by-id/usb-Nabu_Casa_ZWA-2_80B54EE5CBE8-if00
[21:18:31] INFO: Successfully send discovery information to Home Assistant.
2025-12-07 21:18:37.693 DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2025-12-07 21:18:37.708 DRIVER version 15.15.0
2025-12-07 21:18:37.710 DRIVER
2025-12-07 21:18:38.043 DRIVER Dropping message because the driver is not ready to handle it yet.
2025-12-07 21:18:38.061 DRIVER Dropping message because the driver is not ready to handle it yet.
2025-12-07 21:18:38.075 DRIVER Dropping message because the driver is not ready to handle it yet.
2025-12-07 21:18:38.089 DRIVER Dropping message because the driver is not ready to handle it yet.
2025-12-07 21:18:38.102 DRIVER Dropping message because the driver is not ready to handle it yet.
2025-12-07 21:18:38.114 DRIVER Dropping message because the driver is not ready to handle it yet.
2025-12-07 21:18:38.129 DRIVER Dropping message because the driver is not ready to handle it yet.
2025-12-07 21:18:38.141 DRIVER Dropping message because the driver is not ready to handle it yet.
2025-12-07 21:18:38.723 DRIVER Dropping message because the driver is not ready to handle it yet.
2025-12-07 21:18:39.043 CONFIG version 15.15.0
2025-12-07 21:18:40.185 DRIVER Dropping message because the driver is not ready to handle it yet.
2025-12-07 21:18:40.747 DRIVER Dropping message because the driver is not ready to handle it yet.
2025-12-07 21:18:41.014 CNTRLR querying Serial API capabilities...
2025-12-07 21:18:41.671 CNTRLR received API capabilities:
firmware version: 1.1
manufacturer ID: 0x0466
product type: 0x01
product ID: 0x01
supported functions:
· GetSerialApiInitData (0x02)
· SetApplicationNodeInformation (0x03)
· GetControllerCapabilities (0x05)
· SetSerialApiTimeouts (0x06)
· GetSerialApiCapabilities (0x07)
· SoftReset (0x08)
· GetProtocolVersion (0x09)
· SerialAPIStarted (0x0a)
· SerialAPISetup (0x0b)
· SetRFReceiveMode (0x10)
· SendNodeInformation (0x12)
· SendData (0x13)
· SendDataMulticast (0x14)