Z Wave JS error message

Romi · April 30, 2021, 2:44pm

I’ve been running Home Assistant for an awful long tine and I always seem to find answers to my issues within other user postings of their problems or generalized searches for deeper explanations. However, this one has me stumped. I integrated Z-Wave JS and it is working. It is slow, erratic, and Lovelace controls are incomplete and/or don’t work well if at all. I chalked it up to JS being new and waited for updates to make improvements. But I dont see where other users are having the same kind of issues that Im having. So I think I’ve done something terribly wrong and unless I ask for help I’ll die sitting in my rocker waiting for a solution. I should mention that I have not removed the old z-wave integration but I HAVE tried to get JS working by disabling it. Here’s the error messages. Can anyone enlighten me please?

Unexpected error ZWaveError: Timeout while waiting for an ACK from the controller
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2405:23)
    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2528:28)
    at Driver.trySendCommandSupervised (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2617:15)
    at MultilevelSwitchCCAPI.set (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:173:47)
    at Proxy.MultilevelSwitchCCAPI.<computed> (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:311:33)
    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:715:14)
    at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:17:44)
    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:34:91)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:86:99)
    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:39:45) {
  code: 16,
  context: undefined,
  transactionSource: '    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2405:23)\n' +
    '    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2528:28)\n' +
    '    at Driver.trySendCommandSupervised (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2617:15)\n' +
    '    at MultilevelSwitchCCAPI.set (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:173:47)\n' +
    '    at Proxy.MultilevelSwitchCCAPI.<computed> (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:311:33)\n' +
    '    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:715:14)\n' +
    '    at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:17:44)\n' +
    '    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:34:91)\n' +
    '    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:86:99)\n' +
    '    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:39:45)'
}
2021-04-28T12:16:37.682Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-04-28T12:16:38.791Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2021-04-28T12:16:41.508Z CNTRLR   [Node 005] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2021-04-28T12:16:43.030Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-04-28T12:16:44.140Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2021-04-28T12:16:46.277Z CNTRLR   [Node 005] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2021-04-28T12:16:47.797Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-04-28T12:16:48.907Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
Unexpected error ZWaveError: Timeout while waiting for an ACK from the controller
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2405:23)
    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2528:28)
    at Driver.trySendCommandSupervised (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2617:15)
    at MultilevelSwitchCCAPI.set (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:173:47)
    at Proxy.MultilevelSwitchCCAPI.<computed> (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:311:33)
    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:715:14)
    at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:17:44)
    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:34:91)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:86:99)
    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:39:45) {
  code: 16,
  context: undefined,
  transactionSource: '    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2405:23)\n' +
    '    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2528:28)\n' +
    '    at Driver.trySendCommandSupervised (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2617:15)\n' +
    '    at MultilevelSwitchCCAPI.set (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:173:47)\n' +
    '    at Proxy.MultilevelSwitchCCAPI.<computed> (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:311:33)\n' +
    '    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:715:14)\n' +
    '    at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:17:44)\n' +
    '    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:34:91)\n' +
    '    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:86:99)\n' +
    '    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:39:45)'
}
2021-04-28T12:18:13.972Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-04-28T12:18:15.084Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2021-04-28T12:18:17.801Z CNTRLR   [Node 005] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2021-04-28T12:18:19.321Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-04-28T12:18:20.434Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
2021-04-28T12:18:22.548Z CNTRLR   [Node 005] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2021-04-28T12:18:24.070Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                                  n 100 ms.
2021-04-28T12:18:25.181Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                                  n 1100 ms.
Unexpected error ZWaveError: Timeout while waiting for an ACK from the controller
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2405:23)
    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2528:28)
    at Driver.trySendCommandSupervised (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2617:15)
    at MultilevelSwitchCCAPI.stopLevelChange (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:258:48)
    at Proxy.MultilevelSwitchCCAPI.<computed> (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:374:16)
    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:715:14)
    at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:17:44)
    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:34:91)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:86:99)
    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:39:45) {
  code: 16,
  context: undefined,
  transactionSource: '    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2405:23)\n' +
    '    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2528:28)\n' +
    '    at Driver.trySendCommandSupervised (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2617:15)\n' +
    '    at MultilevelSwitchCCAPI.stopLevelChange (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:258:48)\n' +
    '    at Proxy.MultilevelSwitchCCAPI.<computed> (/usr/src/node_modules/zwave-js/src/lib/commandclass/MultilevelSwitchCC.ts:374:16)\n' +
    '    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:715:14)\n' +
    '    at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:17:44)\n' +
    '    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:34:91)\n' +
    '    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:86:99)\n' +
    '    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:39:45)'
}
````

firstof9 · April 30, 2021, 8:32pm

This looks like the old zwave is still using the stick and zwavejs is crashing because of this.

Romi · May 1, 2021, 12:15am

Thank you Firstof9. That makes sense. I’ll work in that direction.

Spraguej248 · May 24, 2021, 6:12pm

It looks like I’m also having the same or similar problem. I switched over to Zwave JS from the old zwave integration. Zwave JS keeps crashing several times a day. I have uninstalled the Zwave JS add on and re-installed it several times. I do not have the old zwave integration installed. I am able to get zwave working again by restarting the Zwave JS add-on. But I can’t keep doing that several times a day. Below is info from my log which looks pretty similar to above. Did anyone come up with a fix? Thanks!

Blockquote
2021-05-24T17:28:47.408Z CNTRLR [Node 021] treating BasicCC::Set as a report
2021-05-24T17:30:28.362Z CNTRLR [Node 021] treating BasicCC::Set as a report
2021-05-24T17:31:31.663Z CNTRLR [Node 021] treating BasicCC::Set as a report
2021-05-24T17:32:46.655Z CNTRLR [Node 021] treating BasicCC::Set as a report
2021-05-24T17:34:22.195Z CNTRLR [Node 021] treating BasicCC::Set as a report
2021-05-24T17:35:03.173Z CNTRLR [Node 021] treating BasicCC::Set as a report
2021-05-24T17:57:16.692Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-05-24T17:57:17.801Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2021-05-24T17:57:19.913Z CNTRLR [Node 008] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2021-05-24T17:57:21.455Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-05-24T17:57:22.563Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2021-05-24T17:57:24.672Z CNTRLR [Node 008] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2021-05-24T17:57:26.195Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-05-24T17:57:27.304Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
Unexpected error ZWaveError: Timeout while waiting for an ACK from the controller
at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2332:23)
at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2455:28)
at BinarySwitchCCAPI.set (/usr/src/node_modules/zwave-js/src/lib/commandclass/BinarySwitchCC.ts:111:21)
at Proxy.BinarySwitchCCAPI. (/usr/src/node_modules/zwave-js/src/lib/commandclass/BinarySwitchCC.ts:124:14)
at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:741:14)
at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:17:44)
at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:34:91)
at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:86:99)
at WebSocket. (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:39:45)
at WebSocket.emit (events.js:315:20) {
code: 16,
context: undefined,
transactionSource: ’ at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2332:23)\n’ +
’ at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2455:28)\n’ +
’ at BinarySwitchCCAPI.set (/usr/src/node_modules/zwave-js/src/lib/commandclass/BinarySwitchCC.ts:111:21)\n’ +
’ at Proxy.BinarySwitchCCAPI. (/usr/src/node_modules/zwave-js/src/lib/commandclass/BinarySwitchCC.ts:124:14)\n’ +
’ at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:741:14)\n’ +
’ at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:17:44)\n’ +
’ at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:34:91)\n’ +
’ at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:86:99)\n’ +
’ at WebSocket. (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:39:45)\n’ +
’ at WebSocket.emit (events.js:315:20)’
}

firstof9 · May 25, 2021, 2:56am

Something is stealing your USB stick, find out what and fix it.

Spraguej248 · May 25, 2021, 1:42pm

Beautiful! That’s exactly what it was. I was also using Network UPS Tools to connect to my UPS on another USB port. I disabled Network UPS Tools and all my Zwave JS crashes went away. Thanks!

I had Network UPS Tools port set to auto so it was probably scanning the ports or restarting causing a rescan, conflicting with Zwave JS. It wasn’t a problem with the legacy zwave integration but I guess it’s a problem now. Network UPS Tools allows to specify a USB port. I will try that and see if it there are still any conflicts.

Thanks for your help!