Z-Wave JS terrible response time to turn on

Configuration Z-Wave
1

Hey, so I started migrating to Z-Wave JS and it’s up and running but the response times, especially when turning on for some reason, are terrible. It sometimes take 15 seconds for the light to turn on. When I turn them off and on from the old deprecated z-wave integration, the lights work great. Is it because I’m running both integrations?

Here’s a log sample from the Z-Wave JS Server add-on:

New client
New client
Client disconnected
Code 1000: 
13:12:42.184 DRIVER   Dropping message because it contains invalid data
13:12:42.228 DRIVER   Dropping message because it contains invalid data
13:12:42.860 DRIVER     no handlers registered!
13:12:53.675 DRIVER     no handlers registered!
13:13:03.133 DRIVER     no handlers registered!
13:13:21.671 DRIVER     no handlers registered!
13:13:34.467 DRIVER   Dropping message because it contains invalid data
13:13:34.479 DRIVER   Dropping message because it contains invalid data
13:13:34.482 DRIVER   Dropping message because it contains invalid data
13:18:02.611 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
13:18:03.726 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
13:18:05.851 CNTRLR   [Node 007] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
13:18:07.375 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
13:18:08.487 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
13:18:10.607 CNTRLR   [Node 007] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
13:18:12.134 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
13:18:13.245 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/server/node_modules/zwave-js/src/lib/driver/StateMachineShared.ts:69:11)
    at /usr/lib/node_modules/@zwave-js/server/node_modules/zwave-js/src/lib/driver/SendThreadMachine.ts:436:4
    at /usr/lib/node_modules/@zwave-js/server/node_modules/xstate/lib/utils.js:410:33
    at Array.reduce (<anonymous>)
    at Object.updateContext (/usr/lib/node_modules/@zwave-js/server/node_modules/xstate/lib/utils.js:400:25)
    at Object.resolveActions (/usr/lib/node_modules/@zwave-js/server/node_modules/xstate/lib/actions.js:409:19)
    at StateNode.resolveTransition (/usr/lib/node_modules/@zwave-js/server/node_modules/xstate/lib/StateNode.js:787:35)
    at StateNode.transition (/usr/lib/node_modules/@zwave-js/server/node_modules/xstate/lib/StateNode.js:733:21)
    at StateNode.resolveRaisedTransition (/usr/lib/node_modules/@zwave-js/server/node_modules/xstate/lib/StateNode.js:738:22)
    at StateNode.resolveTransition (/usr/lib/node_modules/@zwave-js/server/node_modules/xstate/lib/StateNode.js:873:39) {
  code: 16,
  context: undefined,
  transactionSource: 'Transaction: \n' +
    '    at Driver.sendMessage (/usr/lib/node_modules/@zwave-js/server/node_modules/zwave-js/src/lib/driver/Driver.ts:2061:23)\n' +
    '    at Driver.sendCommand (/usr/lib/node_modules/@zwave-js/server/node_modules/zwave-js/src/lib/driver/Driver.ts:2162:28)\n' +
    '    at BinarySwitchCCAPI.set (/usr/lib/node_modules/@zwave-js/server/node_modules/zwave-js/src/lib/commandclass/BinarySwitchCC.ts:111:21)\n' +
    '    at Proxy.BinarySwitchCCAPI.<computed> (/usr/lib/node_modules/@zwave-js/server/node_modules/zwave-js/src/lib/commandclass/BinarySwitchCC.ts:124:14)\n' +
    '    at ZWaveNode.setValue (/usr/lib/node_modules/@zwave-js/server/node_modules/zwave-js/src/lib/node/Node.ts:667: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:30:91)\n' +
    '    at Client.receiveMessage (/usr/lib/node_modules/@zwave-js/server/dist/lib/server.js:61:99)\n' +
    '    at WebSocket.<anonymous> (/usr/lib/node_modules/@zwave-js/server/dist/lib/server.js:35:45)\n' +
    '    at WebSocket.emit (events.js:315:20)'
}
13:18:16.746 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
13:18:17.858 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
13:18:19.977 CNTRLR   [Node 007] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
13:18:21.504 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
13:18:22.615 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
13:18:24.732 CNTRLR   [Node 007] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
13:18:26.276 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
2

If you are running both integrations at the same time, then that is a definite problem. You can’t share the USB device between multiple addons/integrations that are running at the same time.

3

Hey thanks!
Just deleted the old integration and rebooted the pi for good measure and everything is working great.

4

Hi, I am new to HA. I recently migrated from Smartthings to HA. For the past month, I used the Smartthings integration to run HA. It worked very well. This weekend, after learning that the new version of ZWaveJS was released I fully migrated to ZwaveJS to MQTT. Everything is up and running but I am experiencing huge latency as well, up to 25 sec for the lights to turn on/off. The UI is also not working right: it shows the lights are on when they are not. I am running HA from a Raspberry Pi. Is anyone experiencing the same?

1 Like
5

Hey, this sounds really similar to the issues I was having when I created this topic. What Z-Wave dongle are you using on your RPi, and do you still have the SmartThings Integration installed and active?

6

I have the same issue , usually when I turn off/on few switches at the same time

7

i am using the GoControl Z-Wave/Zigbee QuickStick Combo by NORTEK SECURITY & CONTROL. I did delete the SmartThings integration too.

8

I have a very similar issue with a Nortek USB stick, running core-2021.3.3 and Zwave JS 0.1.11

HA is running on a Virtualbox.
At times the Zwave commands stop working completely till I restart the Z-Wave JS.

I’d love to find out what is causing this and hopefully resolve it.

Following…

9

Hi BO1,

My problem got fixed: it so happens that I was using the 64Bit version of HA given that my Pi had a 64Bit Chip. As soon as I installed the 32Bit version of HA, the problem went away. It seems the 64bit version is not stable.

I hope this helps.

1 Like
10

When using the Nortek under VirtualBox, make sure you are sharing the physical USB device with the Home Assistant guest. Do not share the serial ports from the host as they are notoriously unreliable and buggy with the Nortek.

11

image

This is how I have them shared. Is this correct?