ZWave Crashes every Day - Gen7

fisch55 · April 17, 2023, 6:53am

My zwave now crashes every day…

Home Assistant 2023.4.4
Supervisor 2023.04.0
Operating System 10.0.rc4
Frontend 20230411.1 - latest

2023-04-16 22:10:20.879 INFO Z-WAVE: [Node 080] Is now asleep
2023-04-16T20:10:20.880Z CNTRLR   [Node 080] The node is now asleep.
2023-04-16T20:10:23.541Z CNTRLR   [Node 089] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2023-04-16T20:10:24.055Z CNTRLR   [Node 089] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2023-04-16T20:10:24.571Z CNTRLR   [Node 089] The node did not respond after 3 attempts, it is presumed dead
2023-04-16 22:10:24.571 INFO Z-WAVE: [Node 089] Is now dead
2023-04-16T20:10:24.571Z CNTRLR   [Node 089] The node is now dead.
2023-04-16 22:10:24.576 ERROR Z-WAVE-SERVER: Failed to send the command after 3 attempts (Status Fail) (ZW0202)
ZWaveError: Failed to send the command after 3 attempts (Status Fail) (ZW0202)
    at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:4182:23)
    at Driver.sendCommandInternal (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:4375:28)
    at Driver.sendSupervisedCommand (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:4420:27)
    at Driver.sendCommand (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:4477:30)
    at ThermostatSetpointCCAPI.set (/opt/node_modules/@zwave-js/cc/src/cc/ThermostatSetpointCC.ts:229:24)
    at Proxy.ThermostatSetpointCCAPI.<computed> (/opt/node_modules/@zwave-js/cc/src/cc/ThermostatSetpointCC.ts:148:29)
    at ZWaveNode.setValue (/opt/node_modules/zwave-js/src/lib/node/Node.ts:961:29)
    at NodeMessageHandler.handle (/opt/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:23:38)
    at Object.node (/opt/node_modules/@zwave-js/server/dist/lib/server.js:41:96)
    at Client.receiveMessage (/opt/node_modules/@zwave-js/server/dist/lib/server.js:106:99)
2023-04-16T20:10:24.588Z CNTRLR   [Node 129] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2023-04-16T20:10:24.829Z CNTRLR » [Node 003] pinging the node...
2023-04-16T20:10:24.850Z CNTRLR » [Node 059] pinging the node...
2023-04-16T20:10:25.103Z CNTRLR   [Node 129] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2023-04-16T20:10:25.618Z CNTRLR   [Node 129] The node did not respond after 3 attempts, it is presumed dead
2023-04-16 22:10:25.618 INFO Z-WAVE: [Node 129] Is now dead
2023-04-16T20:10:25.619Z CNTRLR   [Node 129] The node is now dead.
2023-04-16 22:10:25.623 ERROR Z-WAVE-SERVER: Failed to send the command after 3 attempts (Status Fail) (ZW0202)
ZWaveError: Failed to send the command after 3 attempts (Status Fail) (ZW0202)
    at Driver.sendMessage (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:4182:23)
    at Driver.sendCommandInternal (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:4375:28)
    at Driver.sendSupervisedCommand (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:4420:27)
    at Driver.sendCommand (/opt/node_modules/zwave-js/src/lib/driver/Driver.ts:4477:30)
    at ThermostatSetpointCCAPI.set (/opt/node_modules/@zwave-js/cc/src/cc/ThermostatSetpointCC.ts:229:24)
    at Proxy.ThermostatSetpointCCAPI.<computed> (/opt/node_modules/@zwave-js/cc/src/cc/ThermostatSetpointCC.ts:148:29)
    at ZWaveNode.setValue (/opt/node_modules/zwave-js/src/lib/node/Node.ts:961:29)
    at NodeMessageHandler.handle (/opt/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:23:38)
    at Object.node (/opt/node_modules/@zwave-js/server/dist/lib/server.js:41:96)
    at Client.receiveMessage (/opt/node_modules/@zwave-js/server/dist/lib/server.js:106:99)
2023-04-16T20:10:25.635Z CNTRLR   [Node 003] The node did not respond after 1 attempts, it is presumed dead
2023-04-16T20:10:25.637Z CNTRLR   [Node 003] ping failed: Failed to send the command after 1 attempts (Status Fa
                                  il) (ZW0202)
2023-04-16T20:10:25.650Z CNTRLR   [Node 059] The node did not respond after 1 attempts, it is presumed dead
2023-04-16T20:10:25.652Z CNTRLR   [Node 059] ping failed: Failed to send the command after 1 attempts (Status Fa
                                  il) (ZW0202)
2023-04-16T20:10:25.882Z CNTRLR » [Node 003] pinging the node...
2023-04-16T20:10:25.895Z CNTRLR » [Node 059] pinging the node...
2023-04-16T20:10:25.899Z CNTRLR   [Node 003] The node did not respond after 1 attempts, it is presumed dead
2023-04-16T20:10:25.901Z CNTRLR   [Node 003] ping failed: Failed to send the command after 1 attempts (Status Fa
                                  il) (ZW0202)
2023-04-16T20:10:25.913Z CNTRLR » [Node 128] pinging the node...
2023-04-16T20:10:25.916Z CNTRLR   [Node 059] The node did not respond after 1 attempts, it is presumed dead
2023-04-16T20:10:25.918Z CNTRLR   [Node 059] ping failed: Failed to send the command after 1 attempts (Status Fa
                                  il) (ZW0202)
2023-04-16T20:10:25.931Z CNTRLR   [Node 128] The node did not respond after 1 attempts. It is probably asleep, m
                                  oving its messages to the wakeup queue.
2023-04-16T20:10:25.932Z CNTRLR   [Node 128] ping failed: Failed to send the command after 1 attempts (Status Fa
                                  il) (ZW0202)
2023-04-16T20:10:28.373Z CNTRLR » [Node 129] pinging the node...
2023-04-16T20:10:28.376Z CNTRLR » [Node 045] pinging the node...
2023-04-16T20:10:28.377Z CNTRLR » [Node 003] pinging the node...
2023-04-16T20:10:28.378Z CNTRLR » [Node 025] pinging the node...
2023-04-16T20:10:28.379Z CNTRLR » [Node 089] pinging the node...
2023-04-16T20:10:28.380Z CNTRLR » [Node 079] pinging the node...
2023-04-16T20:10:28.385Z CNTRLR » [Node 059] pinging the node...
2023-04-16T20:10:28.388Z CNTRLR   [Node 129] The node did not respond after 1 attempts, it is presumed dead
2023-04-16T20:10:28.390Z CNTRLR   [Node 129] ping failed: Failed to send the command after 1 attempts (Status Fa
                                  il) (ZW0202)
2023-04-16T20:10:28.403Z CNTRLR   [Node 045] The node did not respond after 1 attempts, it is presumed dead
2023-04-16T20:10:28.405Z CNTRLR   [Node 045] ping failed: Failed to send the command after 1 attempts (Status Fa
                                  il) (ZW0202)
2023-04-16T20:10:28.418Z CNTRLR   [Node 003] The node did not respond after 1 attempts, it is presumed dead
2023-04-16T20:10:28.420Z CNTRLR   [Node 003] ping failed: Failed to send the command after 1 attempts (Status Fa
                                  il) (ZW0202)
2023-04-16T20:10:28.433Z CNTRLR   [Node 025] The node did not respond after 1 attempts, it is presumed dead
2023-04-16T20:10:28.435Z CNTRLR   [Node 025] ping failed: Failed to send the command after 1 attempts (Status Fa
                                  il) (ZW0202)
2023-04-16T20:10:28.448Z CNTRLR   [Node 089] The node did not respond after 1 attempts, it is presumed dead
2023-04-16T20:10:28.449Z CNTRLR   [Node 089] ping failed: Failed to send the command after 1 attempts (Status Fa
                                  il) (ZW0202)
2023-04-16T20:10:28.465Z CNTRLR   [Node 079] The node did not respond after 1 attempts, it is presumed dead
2023-04-16T20:10:28.467Z CNTRLR   [Node 079] ping failed: Failed to send the command after 1 attempts (Status Fa
                                  il) (ZW0202)
2023-04-16T20:10:28.480Z CNTRLR   [Node 059] The node did not respond after 1 attempts, it is presumed dead
2023-04-16T20:10:28.481Z CNTRLR   [Node 059] ping failed: Failed to send the command after 1 attempts (Status Fa
                                  il) (ZW0202)

tmjpugh · April 17, 2023, 3:06pm

I had a node that was out of range that created similar problem

Check all nodes for communication issues

fisch55 · April 17, 2023, 4:17pm

Ok, one device lets crash all devices ?

tmjpugh · April 17, 2023, 5:36pm

Yes. I had this exact situation occur

1 device located some 200’ from contoller. There were closer devices maybe 100’ away but it was clearly at edge of range. It would drop/miss commands and cause retransmits. Once or twice a day my network would randomly go down. Cant remember if reboots brought it back but it did affect all devices. I finally removed the single device after trying everything else. Problem gone.

I didn’t expect this to work but after you try everything…try everything.