LZW30 - Lag when turn on and off in quick succession

I successfully added all my 6 LZW30 to my Home Assistant. It works great. What i noticed was, if i try to toggle the switch quickly in Home Assistant (line on-off-on-off), the first on is instant. I see the light turn on immediately. But the subsequent commands has a delay of around 4 or 5 sec and they all are queued, meaning they all execute, but all the commands expect the first one has a delay.

I monitored the OZW_Log.txt and found this is is where the delay is happening.

2019-10-09 16:33:48.081 Info, Raw: 0x98, 0x81, 0x72, 0xf6, 0xb3, 0xf7, 0xe4, 0x7b, 0x9a, 0xfc, 0xe2, 0xb1, 0xdf, 0x11, 0x2b, 0x27, 0x31, 0xef, 0x7c, 0xa9, 0x96, 0x3b, 0xa5, 0xad, 0xf1, 0x06, 0x80, 0x4c, 0x16, 0x12, 0xee
2019-10-09 16:33:48.081 Detail, Node015, Decrypted Packet: 0x00, 0x32, 0x02, 0x21, 0x34, 0x00, 0x00, 0x01, 0x64, 0x00, 0x00
2019-10-09 16:33:48.081 Detail,
2019-10-09 16:33:48.081 Info, Node015, Response RTT 3797 Average Response RTT 2420
2019-10-09 16:33:48.081 Detail, Node015, Refreshed Value: old value=false, new value=false, type=bool
2019-10-09 16:33:48.081 Detail, Node015, Changes to this value are not verified
2019-10-09 16:33:48.081 Info, Node015, Received Meter report from node 15: Power=35.6W
2019-10-09 16:33:48.082 Detail, Node015, Refreshed Value: old value=24.7, new value=35.6, type=decimal
2019-10-09 16:33:48.082 Detail, Node015, Changes to this value are not verified
2019-10-09 16:33:48.082 Detail, Node015, Notification: ValueChanged
2019-10-09 16:33:48.083 Detail, Node015, Notification: ValueChanged
2019-10-09 16:33:54.284 Error, Node015, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-10-09 16:33:54.284 Detail, Node015, Removing current message
2019-10-09 16:33:54.284 Detail, Node015, Notification: Notification - TimeOut
2019-10-09 16:33:54.286 Detail,
2019-10-09 16:33:54.286 Info, Node015, Processing (Send) Nonce Request message (Callback ID=0xe0, Expected Reply=0x13)
2019-10-09 16:33:54.286 Info, Node015, Sending (Send) message (Callback ID=0xe0, Expected Reply=0x13) - Nonce_Get(SwitchBinaryCmd_Set) - 0x01, 0x09, 0x00, 0x13, 0x0f, 0x02, 0x98, 0x40, 0x05, 0x02:

Notice the Timeout in the logs. Looks like HA send the request and waiting for a response from the switch and eventually timeout out.

Is this expected?

Tagging @EricM_Inovelli - maybe he can understand the logs. It’s a foreign language to me!

Edit: Just talked to Eric and there seems to be a lot of lag when S0 is used in Home Assistant – we aren’t sure why, but it’s just something we noticed. HA does have the option to include with or without security – could you try including one without security to see what happens?

@praveen12bnitt This is something that I have also noticed with HA, but only when I do a secure inclusion. There seems to be a lot of overhead with S0 security and HA. The other hubs I have tried seem to not to do this (like SmartThings, Hubitat, etc.). Unless you did a non-secure inclusion I think this is the issue. Either that or the switch is on the edge of network range or the routing for the switch is not optimized or has a bad node.

As a test you can try a non-secure inclusion to see if that improves the performance.

1 Like

Thanks. I wanted to try to add the switch in non-secure mode, but the problem this is set at the zwave level. So for me to test it, I have to exclude all the devices, which is too much of work. So I am not comfortable to try this out.

Do u know of a way to set this at a device level ?

Hey so I had someone else have this issue who wrote into support and he confirmed that by including via non-secure, this problem was fixed.

I realize it’s a hassle and I don’t know how to set at a device level, but I at least wanted to let you know that @EricM_Inovelli’s hunch was correct.

1 Like

Hi @praveen12bnitt, there should be a separate button to do a non-secure inclusion.

1 Like

Ho. If it’s this simple, I will try our tonight

1 Like

Hey @praveen12bnitt – just wanted to see if you were able to do this or not? Curious on the results if you were able to. If not, no worries – I just wanted to close the loop!

I removed the node and connected it back in normal mode and I no longer see the lag. So adding in secure mode is indeed the problem.

Since it’s just a switch, it’s actually ok to add it as a normal node. Thanks for ur help on this.

1 Like

Awesome, thanks for reporting back!

Just in case anyone else is stumbling upon this in the future, this totally fixed the same issue for me. Glad this thread exists! Thanks @Eric_Inovelli!

Now to go delete and re-add 31 more nodes…

Great to hear! Happy to help and thanks to our awesome community for helping. Funny part is I do not have Home Assistant (way above my pay-grade) but a lot of smart people such as yourself figured it out!