Z-Wave JS - Network crashes/freezes randomly only when my shed light switch is toggled

[alexbellerive]

The problem

My Z-Wave network seems to freeze randomly when my shed lights are toggled on or off (sometimes it works just fine). This was never an issue with the old Z-Wave integration. None of my other Z-Wave devices respond to commands when this happens. It does clear up after a few minutes and the shed lights end up toggling.

My shed is a little further from the house, so maybe the weaker signal is to blame? It sometimes took a second or two for the lights to toggle with the old Z-Wave integration, but it always worked. I did just add an outdoor plug with a built-in repeater in the backyard to see if it would help, but I'm still experiencing this issue.

The switch is an Inovelli LZW30 (Black Series on/off switch).

Environment

• Add-on with the issue: Z-Wave JS
• Add-on release with the issue: 0.1.10
• Last working add-on release (if known):
• Operating environment (OS/Supervised): Home Assistant on Pi 4 with Aeotec Z-Wave USB stick

Problem-relevant configuration

Traceback/Error logs

15:27:41.372 CNTRLR   [Node 020] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
15:27:42.380 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
15:27:43.487 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
15:27:46.615 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
15:27:47.725 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
15:27:49.835 CNTRLR   [Node 020] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
15:27:51.352 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
15:27:52.459 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 Object.sendDataErrorToZWaveError (/usr/lib/node_modules/zwave-js/src/lib/driver/StateMachineShared.ts:69:11)
    at /usr/lib/node_modules/zwave-js/src/lib/driver/SendThreadMachine.ts:441:4
    at /usr/lib/node_modules/zwave-js/node_modules/xstate/lib/utils.js:410:33
    at Array.reduce (<anonymous>)
    at Object.updateContext (/usr/lib/node_modules/zwave-js/node_modules/xstate/lib/utils.js:400:25)
    at Object.resolveActions (/usr/lib/node_modules/zwave-js/node_modules/xstate/lib/actions.js:409:19)
    at StateNode.resolveTransition (/usr/lib/node_modules/zwave-js/node_modules/xstate/lib/StateNode.js:787:35)
    at StateNode.transition (/usr/lib/node_modules/zwave-js/node_modules/xstate/lib/StateNode.js:733:21)
    at StateNode.resolveRaisedTransition (/usr/lib/node_modules/zwave-js/node_modules/xstate/lib/StateNode.js:738:22)
    at StateNode.resolveTransition (/usr/lib/node_modules/zwave-js/node_modules/xstate/lib/StateNode.js:873:39) {
  code: 16,
  context: undefined,
  transactionSource: 'Transaction: \n' +
    '    at Driver.sendMessage (/usr/lib/node_modules/zwave-js/src/lib/driver/Driver.ts:2094:23)\n' +
    '    at Driver.sendCommand (/usr/lib/node_modules/zwave-js/src/lib/driver/Driver.ts:2195:28)\n' +
    '    at BinarySwitchCCAPI.set (/usr/lib/node_modules/zwave-js/src/lib/commandclass/BinarySwitchCC.ts:111:21)\n' +
    '    at Proxy.BinarySwitchCCAPI.<computed> (/usr/lib/node_modules/zwave-js/src/lib/commandclass/BinarySwitchCC.ts:124:14)\n' +
    '    at ZWaveNode.setValue (/usr/lib/node_modules/zwave-js/src/lib/node/Node.ts:683:14)\n' +
    '    at Function.handle (/usr/lib/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:15:44)\n' +
    '    at Object.node (/usr/lib/node_modules/@zwave-js/server/dist/lib/server.js:32:91)\n' +
    '    at Client.receiveMessage (/usr/lib/node_modules/@zwave-js/server/dist/lib/server.js:85:99)\n' +
    '    at WebSocket.<anonymous> (/usr/lib/node_modules/@zwave-js/server/dist/lib/server.js:37:45)\n' +
    '    at WebSocket.emit (events.js:315:20)'
}
15:27:55.574 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
15:27:56.679 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
15:27:58.788 CNTRLR   [Node 020] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
15:28:00.301 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
15:28:01.407 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
15:28:03.518 CNTRLR   [Node 020] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
15:28:05.029 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
15:28:06.135 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
15:28:09.253 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
15:28:10.363 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
15:28:12.473 CNTRLR   [Node 020] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
15:28:13.986 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
15:28:15.093 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
15:30:14.985 CNTRLR   [Node 020] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
15:30:17.244 DRIVER     no handlers registered!
15:30:19.045 DRIVER     no handlers registered!

Additional information

[probot-home-assistant[bot]]

zwave_js documentation zwave_js source _{^{(message by IssueLinks)}}

[MartinHjelmare]

@Petro31 do you know if this is a known issue with the Inovelli LZW30?

[alexbellerive]

@Petro31 do you if this is a known issue with the Inovelli LZW30?

For what it's worth, I have about a dozen more of them (as well as some Inovelli dimmers) and this is the only one experiencing this issue.

[Petro31]

@MartinHjelmare I have 2 of these devices and have never had an issue. I'm about to install 9 more in the coming weeks.

@alexbellerive what firmware version are you running? Also how far away is the shed?

[alexbellerive]

@Petro31 The shed is probably about 40 feet away from the house (and from the closest node which is also an Inovelli switch). Looking in the JSON dump, it does have several node neighbours.

The firmware version on the switch is 1.20.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.