Zwave freezes/stops working after a while

vinisz · September 6, 2023, 3:17pm

Hi,

Since few weeks (don’t know exactly when or after what changes) , my Zwave network (or the add-on) just “freezes” , nothing works anymore.

What I see in the log is this:

    '    at Proxy.set (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:138:24)\n' +
    '    at Proxy.<anonymous> (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:160:16)\n' +
    '    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1139:39)\n' +
    '    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:20:43)\n' +
    '    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:42:96)\n' +
    '    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:119:99)\n' +
    '    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:51:45)'
}
Z-Wave error ZWaveError: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4889:23)
    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5091:28)
    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5202:15)
    at Proxy.set (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:138:24)
    at Proxy.<anonymous> (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:160:16)
    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1139:39)
    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:20:43)
    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:42:96)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:119:99)
    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:51:45) {
  code: 202,
  context: undefined,
  transactionSource: '    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4889:23)\n' +
    '    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5091:28)\n' +
    '    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5202:15)\n' +
    '    at Proxy.set (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:138:24)\n' +
    '    at Proxy.<anonymous> (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:160:16)\n' +
    '    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1139:39)\n' +
    '    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:20:43)\n' +
    '    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:42:96)\n' +
    '    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:119:99)\n' +
    '    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:51:45)'
}
2023-09-06T13:11:20.879Z CNTRLR   [Node 055] Timed out while waiting for a response from the node (ZW0201)
2023-09-06T13:11:33.546Z CNTRLR   The controller response indicated failure after 1/3 attempts. Scheduling next 
                                  try in 100 ms.
2023-09-06T13:11:33.650Z CNTRLR   The controller response indicated failure after 2/3 attempts. Scheduling next 
                                  try in 1100 ms.
2023-09-06T13:11:42.789Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-09-06T13:12:12.794Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-09-06T13:13:09.284Z CNTRLR   [Node 010] The node did not respond after 1 attempts, it is presumed dead
Z-Wave error ZWaveError: The node did not respond after 1 attempts, it is presumed dead (ZW0202)
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4889:23)
    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5091:28)
    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5202:15)
    at Proxy.set (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:138:24)
    at Proxy.<anonymous> (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:160:16)
    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1139:39)
    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:20:43)
    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:42:96)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:119:99)
    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:51:45) {
  code: 202,
  context: undefined,
  transactionSource: '    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4889:23)\n' +
    '    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5091:28)\n' +
    '    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5202:15)\n' +
    '    at Proxy.set (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:138:24)\n' +
    '    at Proxy.<anonymous> (/usr/src/node_modules/@zwave-js/cc/src/cc/BinarySwitchCC.ts:160:16)\n' +
    '    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1139:39)\n' +
    '    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:20:43)\n' +
    '    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:42:96)\n' +
    '    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:119:99)\n' +
    '    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:51:45)'
}
2023-09-06T13:14:00.022Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2023-09-06T14:02:27.181Z CNTRLR   [Node 220] Timed out while waiting for a response from the node (ZW0201)
2023-09-06T14:03:04.895Z DRIVER   Dropping message because it could not be deserialized: The command class Netwo
                                  rk Management Proxy is not implemented (ZW0303)
2023-09-06T14:03:05.024Z DRIVER   Dropping message because it could not be deserialized: The command class Netwo
                                  rk Management Proxy is not implemented (ZW0303)
2023-09-06T14:03:05.044Z DRIVER   Dropping message because it could not be deserialized: The command class Netwo
                                  rk Management Proxy is not implemented (ZW0303)
2023-09-06T14:03:05.123Z DRIVER   Dropping message because it could not be deserialized: The command class Netwo
                                  rk Management Proxy is not implemented (ZW0303)
2023-09-06T14:03:05.193Z DRIVER   Dropping message because it could not be deserialized: The command class Netwo
                                  rk Management Proxy is not implemented (ZW0303)
2023-09-06T14:03:05.276Z DRIVER   Dropping message because it could not be deserialized: The command class Netwo
                                  rk Management Proxy is not implemented (ZW0303)
2023-09-06T14:03:05.995Z DRIVER   Dropping message because it could not be deserialized: The command class Netwo
                                  rk Management Proxy is not implemented (ZW0303)
2023-09-06T14:03:20.765Z CNTRLR   [Node 020] The node did not respond after 3 attempts. It is probably asleep, m
                                  oving its messages to the wakeup queue.
2023-09-06T14:03:54.868Z CNTRLR   [Node 219] The node did not respond after 3 attempts. It is probably asleep, m
                                  oving its messages to the wakeup queue.
2023-09-06T14:04:23.685Z CNTRLR   [Node 012] The node did not respond after 3 attempts. It is probably asleep, m
                                  oving its messages to the wakeup queue.
2023-09-06T14:04:50.772Z CNTRLR   [Node 220] The node did not respond after 3 attempts. It is probably asleep, m
                                  oving its messages to the wakeup queue.
2023-09-06T14:04:54.204Z CNTRLR   [Node 072] Timed out while waiting for a response from the node (ZW0201)
2023-09-06T14:04:58.585Z CNTRLR   The controller response indicated failure after 1/3 attempts. Scheduling next 
                                  try in 100 ms.
2023-09-06T14:05:25.733Z CNTRLR   [Node 210] The node did not respond after 3 attempts. It is probably asleep, m
                                  oving its messages to the wakeup queue.
2023-09-06T14:05:26.925Z CNTRLR   The controller response indicated failure after 1/3 attempts. Scheduling next 
                                  try in 100 ms.
2023-09-06T14:05:27.031Z CNTRLR   The controller response indicated failure after 2/3 attempts. Scheduling next 
                                  try in 1100 ms.

I have no idea what is happening here… anyone ?

NathanCu · September 6, 2023, 3:24pm

Completely power down and restart. The controller stick isn’t answering commands. When mine does that I have to either fully power down and restart HA or pull the USB stick, plug it back in and restart ZWaveJS.

vinisz · September 6, 2023, 3:31pm

Already did that (multiple times) , complete power down of the NUC , pulled the zwave stick from the USB extender cord, back in, power in… Sure , it helps (also restarting the plugin already does) but, after some time (can be like 2, 3 days) things freeze again

GarageDoor · September 6, 2023, 3:32pm

Also having this problem, I believe since updating to 2023.9. Currently on 2023.9.0b4. Have you updated the firmware on your Z-Wave stick recently? Those are the only two things that I’ve changed in the past few weeks.

Updating to 2023.9.0b6 to see if that fixes it. Will report back in a few days.

vinisz · September 6, 2023, 7:53pm

I did not update firmware on zwave stick but yes, I did HA updates like I normal do.
Curious if your update helps, keep me posted (also, whats in the release logs that could impact this ???) btw, I’m on 2023.8.4