Frustration level 100! Scene commanding 5 red dimmers can take over 20+ seconds to complete

jtronicus · December 2, 2020, 4:16pm

The delay you are seeing is likely due to the way the zwave component in Home Assistant works.

Home Assistant/OZW does not support multicast. It is not able to control 5 dimmers in the same command (even though the zwave protocol supports this). When HA receives the central scene, it is then controlling each dimmer individually.
When HA/OZW sends a command to a device, it immediately sends another command to request a status update from that device in order to verify everything updated as expected. If the transition time is not set to 0, HA/OZW may send many of these status requests (until the dimming value stops changing)
Every time a command is sent to a device, the device responds with an acknowledgement packet. This ultimately means that controlling 5 lights will require at least 20 packets back and forth.

If you examine your OZW_Log.txt file while triggering a scene, you will probably see a lot of activity.

The best way I have found to speed things up is to set the transition speed to 0 when controlling dimmers.

nappyjim · December 2, 2020, 6:18pm

Thanks for all the replies.

@djordan2112 well I simplified it to 5 nodes because those are the ones I am trying to control through a scene. But when I first saw this issue, I had 30+ nodes and I thought maybe that was the issue. And when I had all 30 nodes connected, there are 2 switches in same room, literally 10ft way from the z wave stick.

I just paired 2 nodes to try to view the mesh (this is new to me) and they are showing unconnected so I am not sure whats up with that. Both some COMPLETE in the Z wave integration and I can control both without issue or delay (manually, that is).

Heres the mesh. I am going to try to re-pair them as secured nodes, see if that makes a difference.

@jtronicus

I did not know HA doesnt support multicast, thats interesting. But I’ve also tried just a HA script where I turn off the 4 devices and turn on the 1. And my results are the same; sometimes lighting quick, other times its slow.
Does Hubitat support multicast?
Here is the log file from a quick one (only turning off 4 nodes). All appeared to turn off at same time.
I have seen in the past though, in my log file something about the hub didnt recieve an ACK. But its not tied to just one node. One time it may not see an ACK from node 3, next time it will be node 5, next time node 1.
All dimmers are set to 0 for speed.

Log file from a succesful/quick sequence turning off 4 nodes.

2020-12-01 21:30:29.973 Info, Node002, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Level - 0 - 1 - 99

2020-12-01 21:30:29.973 Info, Node002, SwitchMultilevel::Set - Setting to level 99
2020-12-01 21:30:29.973 Detail, Node002, Queuing (Send) SwitchMultilevelCmd_Set (Node=2): 0x01, 0x0a, 0x00, 0x13, 0x02, 0x03, 0x26, 0x01, 0x63, 0x25, 0xb6, 0x30
2020-12-01 21:30:29.973 Detail, Node002, Queuing (Send) SwitchMultilevelCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x26, 0x02, 0x25, 0xb7, 0x53
2020-12-01 21:30:29.973 Detail,
2020-12-01 21:30:29.973 Info, Node002, Sending (Send) message (Callback ID=0xb6, Expected Reply=0x13) - SwitchMultilevelCmd_Set (Node=2): 0x01, 0x0a, 0x00, 0x13, 0x02, 0x03, 0x26, 0x01, 0x63, 0x25, 0xb6, 0x30
2020-12-01 21:30:29.980 Info, Node003, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Level - 0 - 1 - 99
2020-12-01 21:30:29.980 Info, Node003, SwitchMultilevel::Set - Setting to level 99
2020-12-01 21:30:29.980 Detail, Node003, Queuing (Send) SwitchMultilevelCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x26, 0x01, 0x63, 0x25, 0xb8, 0x3f
2020-12-01 21:30:29.980 Detail, Node003, Queuing (Send) SwitchMultilevelCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x26, 0x02, 0x25, 0xb9, 0x5c
2020-12-01 21:30:29.980 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-12-01 21:30:29.981 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2020-12-01 21:30:29.987 Info, Node005, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Level - 0 - 1 - 99
2020-12-01 21:30:29.987 Info, Node005, SwitchMultilevel::Set - Setting to level 99
2020-12-01 21:30:29.987 Detail, Node005, Queuing (Send) SwitchMultilevelCmd_Set (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x26, 0x01, 0x63, 0x25, 0xba, 0x3b
2020-12-01 21:30:29.987 Detail, Node005, Queuing (Send) SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0xbb, 0x58
2020-12-01 21:30:29.993 Info, Node006, Value::Set - COMMAND_CLASS_SWITCH_MULTILEVEL - Level - 0 - 1 - 99
2020-12-01 21:30:29.994 Info, Node006, SwitchMultilevel::Set - Setting to level 99
2020-12-01 21:30:29.994 Detail, Node006, Queuing (Send) SwitchMultilevelCmd_Set (Node=6): 0x01, 0x0a, 0x00, 0x13, 0x06, 0x03, 0x26, 0x01, 0x63, 0x25, 0xbc, 0x3e
2020-12-01 21:30:29.994 Detail, Node006, Queuing (Send) SwitchMultilevelCmd_Get (Node=6): 0x01, 0x09, 0x00, 0x13, 0x06, 0x02, 0x26, 0x02, 0x25, 0xbd, 0x5d
2020-12-01 21:30:29.997 Detail, Node002, Received: 0x01, 0x05, 0x00, 0x13, 0xb6, 0x00, 0x5f
2020-12-01 21:30:29.997 Detail, Node002, ZW_SEND_DATA Request with callback ID 0xb6 received (expected 0xb6)
2020-12-01 21:30:29.997 Info, Node002, Request RTT 23 Average Request RTT 22
2020-12-01 21:30:29.997 Detail, Expected callbackId was received
2020-12-01 21:30:29.997 Detail, Expected reply was received
2020-12-01 21:30:29.997 Detail, Message transaction complete
2020-12-01 21:30:29.997 Detail,
2020-12-01 21:30:29.997 Detail, Node002, Removing current message
2020-12-01 21:30:29.997 Detail,
2020-12-01 21:30:29.997 Info, Node002, Sending (Send) message (Callback ID=0xb7, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x26, 0x02, 0x25, 0xb7, 0x53
2020-12-01 21:30:30.004 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-12-01 21:30:30.004 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
2020-12-01 21:30:30.019 Detail, Node002, Received: 0x01, 0x05, 0x00, 0x13, 0xb7, 0x00, 0x5e
2020-12-01 21:30:30.020 Detail, Node002, ZW_SEND_DATA Request with callback ID 0xb7 received (expected 0xb7)
2020-12-01 21:30:30.020 Info, Node002, Request RTT 23 Average Request RTT 22
2020-12-01 21:30:30.020 Detail, Expected callbackId was received
2020-12-01 21:30:30.038 Detail, Node002, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x26, 0x03, 0x00, 0xd6
2020-12-01 21:30:30.039 Detail,
2020-12-01 21:30:30.039 Info, Node002, Response RTT 42 Average Response RTT 41
2020-12-01 21:30:30.039 Info, Node002, Received SwitchMultiLevel report: level=0
2020-12-01 21:30:30.039 Detail, Node002, Refreshed Value: old value=0, new value=0, type=byte
2020-12-01 21:30:30.039 Detail, Node002, Changes to this value are not verified
2020-12-01 21:30:30.039 Detail, Node002, Expected reply and command class was received
2020-12-01 21:30:30.039 Detail, Node002, Message transaction complete
2020-12-01 21:30:30.039 Detail,
2020-12-01 21:30:30.039 Detail, Node002, Removing current message
2020-12-01 21:30:30.039 Detail, Node002, Notification: ValueChanged
2020-12-01 21:30:30.043 Detail,
2020-12-01 21:30:30.043 Info, Node003, Sending (Send) message (Callback ID=0xb8, Expected Reply=0x13) - SwitchMultilevelCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x26, 0x01, 0x63, 0x25, 0xb8, 0x3f
2020-12-01 21:30:30.050 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-12-01 21:30:30.050 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
2020-12-01 21:30:30.126 Detail, Node003, Received: 0x01, 0x05, 0x00, 0x13, 0xb8, 0x00, 0x51
2020-12-01 21:30:30.127 Detail, Node003, ZW_SEND_DATA Request with callback ID 0xb8 received (expected 0xb8)
2020-12-01 21:30:30.127 Info, Node003, Request RTT 83 Average Request RTT 62
2020-12-01 21:30:30.127 Detail, Expected callbackId was received
2020-12-01 21:30:30.127 Detail, Expected reply was received
2020-12-01 21:30:30.127 Detail, Message transaction complete
2020-12-01 21:30:30.127 Detail,
2020-12-01 21:30:30.127 Detail, Node003, Removing current message
2020-12-01 21:30:30.127 Detail,
2020-12-01 21:30:30.127 Info, Node003, Sending (Send) message (Callback ID=0xb9, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x26, 0x02, 0x25, 0xb9, 0x5c
2020-12-01 21:30:30.134 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-12-01 21:30:30.134 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
2020-12-01 21:30:30.240 Detail, Node003, Received: 0x01, 0x05, 0x00, 0x13, 0xb9, 0x00, 0x50
2020-12-01 21:30:30.241 Detail, Node003, ZW_SEND_DATA Request with callback ID 0xb9 received (expected 0xb9)
2020-12-01 21:30:30.241 Info, Node003, Request RTT 113 Average Request RTT 87
2020-12-01 21:30:30.241 Detail, Expected callbackId was received
2020-12-01 21:30:30.297 Detail, Node003, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x03, 0x03, 0x26, 0x03, 0x00, 0xd7
2020-12-01 21:30:30.297 Detail,
2020-12-01 21:30:30.297 Info, Node003, Response RTT 169 Average Response RTT 173
2020-12-01 21:30:30.297 Info, Node003, Received SwitchMultiLevel report: level=0
2020-12-01 21:30:30.297 Detail, Node003, Refreshed Value: old value=0, new value=0, type=byte
2020-12-01 21:30:30.297 Detail, Node003, Changes to this value are not verified
2020-12-01 21:30:30.298 Detail, Node003, Expected reply and command class was received
2020-12-01 21:30:30.298 Detail, Node003, Message transaction complete
2020-12-01 21:30:30.298 Detail,
2020-12-01 21:30:30.298 Detail, Node003, Removing current message
2020-12-01 21:30:30.298 Detail, Node003, Notification: ValueChanged
2020-12-01 21:30:30.306 Detail,
2020-12-01 21:30:30.306 Info, Node005, Sending (Send) message (Callback ID=0xba, Expected Reply=0x13) - SwitchMultilevelCmd_Set (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x26, 0x01, 0x63, 0x25, 0xba, 0x3b
2020-12-01 21:30:30.313 Detail, Node005, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-12-01 21:30:30.313 Detail, Node005, ZW_SEND_DATA delivered to Z-Wave stack
2020-12-01 21:30:30.336 Detail, Node005, Received: 0x01, 0x05, 0x00, 0x13, 0xba, 0x00, 0x53
2020-12-01 21:30:30.336 Detail, Node005, ZW_SEND_DATA Request with callback ID 0xba received (expected 0xba)
2020-12-01 21:30:30.336 Info, Node005, Request RTT 29 Average Request RTT 28
2020-12-01 21:30:30.336 Detail, Expected callbackId was received
2020-12-01 21:30:30.336 Detail, Expected reply was received
2020-12-01 21:30:30.336 Detail, Message transaction complete
2020-12-01 21:30:30.336 Detail,
2020-12-01 21:30:30.336 Detail, Node005, Removing current message
2020-12-01 21:30:30.337 Detail,
2020-12-01 21:30:30.337 Info, Node005, Sending (Send) message (Callback ID=0xbb, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=5): 0x01, 0x09, 0x00, 0x13, 0x05, 0x02, 0x26, 0x02, 0x25, 0xbb, 0x58
2020-12-01 21:30:30.344 Detail, Node005, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-12-01 21:30:30.344 Detail, Node005, ZW_SEND_DATA delivered to Z-Wave stack
2020-12-01 21:30:30.364 Detail, Node005, Received: 0x01, 0x05, 0x00, 0x13, 0xbb, 0x00, 0x52
2020-12-01 21:30:30.364 Detail, Node005, ZW_SEND_DATA Request with callback ID 0xbb received (expected 0xbb)
2020-12-01 21:30:30.364 Info, Node005, Request RTT 27 Average Request RTT 27
2020-12-01 21:30:30.364 Detail, Expected callbackId was received
2020-12-01 21:30:30.475 Detail, Node005, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x05, 0x03, 0x26, 0x03, 0x00, 0xd1
2020-12-01 21:30:30.476 Detail,
2020-12-01 21:30:30.476 Info, Node005, Response RTT 138 Average Response RTT 96
2020-12-01 21:30:30.476 Info, Node005, Received SwitchMultiLevel report: level=0
2020-12-01 21:30:30.476 Detail, Node005, Refreshed Value: old value=41, new value=0, type=byte
2020-12-01 21:30:30.476 Detail, Node005, Changes to this value are not verified
2020-12-01 21:30:30.476 Detail, Node005, Expected reply and command class was received
2020-12-01 21:30:30.476 Detail, Node005, Message transaction complete
2020-12-01 21:30:30.476 Detail,
2020-12-01 21:30:30.476 Detail, Node005, Removing current message
2020-12-01 21:30:30.476 Detail, Node005, Notification: ValueChanged
2020-12-01 21:30:30.484 Detail,
2020-12-01 21:30:30.484 Info, Node006, Sending (Send) message (Callback ID=0xbc, Expected Reply=0x13) - SwitchMultilevelCmd_Set (Node=6): 0x01, 0x0a, 0x00, 0x13, 0x06, 0x03, 0x26, 0x01, 0x63, 0x25, 0xbc, 0x3e
2020-12-01 21:30:30.490 Detail, Node006, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-12-01 21:30:30.491 Detail, Node006, ZW_SEND_DATA delivered to Z-Wave stack
2020-12-01 21:30:30.567 Detail, Node006, Received: 0x01, 0x05, 0x00, 0x13, 0xbc, 0x00, 0x55
2020-12-01 21:30:30.567 Detail, Node006, ZW_SEND_DATA Request with callback ID 0xbc received (expected 0xbc)
2020-12-01 21:30:30.567 Info, Node006, Request RTT 82 Average Request RTT 59
2020-12-01 21:30:30.567 Detail, Expected callbackId was received
2020-12-01 21:30:30.567 Detail, Expected reply was received
2020-12-01 21:30:30.567 Detail, Message transaction complete
2020-12-01 21:30:30.568 Detail,
2020-12-01 21:30:30.568 Detail, Node006, Removing current message
2020-12-01 21:30:30.568 Detail,
2020-12-01 21:30:30.568 Info, Node006, Sending (Send) message (Callback ID=0xbd, Expected Reply=0x04) - SwitchMultilevelCmd_Get (Node=6): 0x01, 0x09, 0x00, 0x13, 0x06, 0x02, 0x26, 0x02, 0x25, 0xbd, 0x5d
2020-12-01 21:30:30.575 Detail, Node006, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-12-01 21:30:30.575 Detail, Node006, ZW_SEND_DATA delivered to Z-Wave stack
2020-12-01 21:30:30.595 Detail, Node006, Received: 0x01, 0x05, 0x00, 0x13, 0xbd, 0x00, 0x54
2020-12-01 21:30:30.595 Detail, Node006, ZW_SEND_DATA Request with callback ID 0xbd received (expected 0xbd)
2020-12-01 21:30:30.595 Info, Node006, Request RTT 27 Average Request RTT 43
2020-12-01 21:30:30.596 Detail, Expected callbackId was received
2020-12-01 21:30:30.617 Detail, Node006, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x06, 0x03, 0x26, 0x03, 0x01, 0xd3
2020-12-01 21:30:30.617 Detail,
2020-12-01 21:30:30.618 Info, Node006, Response RTT 49 Average Response RTT 53
2020-12-01 21:30:30.618 Info, Node006, Received SwitchMultiLevel report: level=1
2020-12-01 21:30:30.618 Detail, Node006, Refreshed Value: old value=0, new value=1, type=byte
2020-12-01 21:30:30.618 Detail, Node006, Changes to this value are not verified
2020-12-01 21:30:30.618 Detail, Node006, Expected reply and command class was received
2020-12-01 21:30:30.618 Detail, Node006, Message transaction complete
2020-12-01 21:30:30.618 Detail,
2020-12-01 21:30:30.618 Detail, Node006, Removing current message
2020-12-01 21:30:30.618 Detail, Node006, Notification: ValueChanged
2020-12-01 21:30:33.213 Detail, Node002, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x26, 0x03, 0x63, 0xb5
2020-12-01 21:30:33.213 Detail,
2020-12-01 21:30:33.213 Info, Node002, Received SwitchMultiLevel report: level=99
2020-12-01 21:30:33.213 Detail, Node002, Refreshed Value: old value=0, new value=99, type=byte
2020-12-01 21:30:33.213 Detail, Node002, Changes to this value are not verified
2020-12-01 21:30:33.213 Detail, Node002, Notification: ValueChanged
2020-12-01 21:30:33.340 Detail, Node003, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x03, 0x03, 0x26, 0x03, 0x63, 0xb4
2020-12-01 21:30:33.341 Detail,
2020-12-01 21:30:33.341 Info, Node003, Received SwitchMultiLevel report: level=99
2020-12-01 21:30:33.341 Detail, Node003, Refreshed Value: old value=0, new value=99, type=byte
2020-12-01 21:30:33.341 Detail, Node003, Changes to this value are not verified
2020-12-01 21:30:33.342 Detail, Node003, Notification: ValueChanged
2020-12-01 21:30:33.840 Detail, Node006, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x06, 0x03, 0x26, 0x03, 0x63, 0xb1
2020-12-01 21:30:33.841 Detail,
2020-12-01 21:30:33.841 Info, Node006, Received SwitchMultiLevel report: level=99
2020-12-01 21:30:33.841 Detail, Node006, Refreshed Value: old value=1, new value=99, type=byte
2020-12-01 21:30:33.841 Detail, Node006, Changes to this value are not verified
2020-12-01 21:30:33.841 Detail, Node006, Notification: ValueChanged
2020-12-01 21:30:35.722 Detail, Node002, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x02, 0x0a, 0x32, 0x02, 0x21, 0x34, 0x00, 0x00, 0x02, 0x17, 0x00, 0x00, 0xd3
2020-12-01 21:30:35.722 Detail,
2020-12-01 21:30:35.722 Detail, Node002, Refreshed Value: old value=false, new value=false, type=bool
2020-12-01 21:30:35.722 Detail, Node002, Changes to this value are not verified
2020-12-01 21:30:35.722 Info, Node002, Received Meter report from node 2: Power=53.5W
2020-12-01 21:30:35.723 Detail, Node002, Refreshed Value: old value=0.0, new value=53.5, type=decimal
2020-12-01 21:30:35.723 Detail, Node002, Changes to this value are not verified
2020-12-01 21:30:35.723 Detail, Node002, Notification: ValueChanged
2020-12-01 21:30:35.730 Detail, Node002, Notification: ValueChanged
2020-12-01 21:30:36.224 Detail, Node003, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x03, 0x0a, 0x32, 0x02, 0x21, 0x34, 0x00, 0x00, 0x01, 0xcc, 0x00, 0x00, 0x0a
2020-12-01 21:30:36.225 Detail,
2020-12-01 21:30:36.225 Detail, Node003, Refreshed Value: old value=false, new value=false, type=bool
2020-12-01 21:30:36.225 Detail, Node003, Changes to this value are not verified
2020-12-01 21:30:36.225 Info, Node003, Received Meter report from node 3: Power=46.0W
2020-12-01 21:30:36.225 Detail, Node003, Refreshed Value: old value=0.0, new value=46.0, type=decimal
2020-12-01 21:30:36.225 Detail, Node003, Changes to this value are not verified
2020-12-01 21:30:36.225 Detail, Node003, Notification: ValueChanged
2020-12-01 21:30:36.232 Detail, Node003, Notification: ValueChanged
2020-12-01 21:30:37.007 Detail, Node005, Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x05, 0x0a, 0x32, 0x02, 0x21, 0x34, 0x00, 0x00, 0x01, 0x13, 0x00, 0x00, 0xd3
2020-12-01 21:30:37.007 Detail,
2020-12-01 21:30:37.008 Detail, Node005, Refreshed Value: old value=false, new value=false, type=bool
2020-12-01 21:30:37.008 Detail, Node005, Changes to this value are not verified
2020-12-01 21:30:37.008 Info, Node005, Received Meter report from node 5: Power=27.5W
2020-12-01 21:30:37.008 Detail, Node005, Refreshed Value: old value=0.0, new value=27.5, type=decimal
2020-12-01 21:30:37.008 Detail, Node005, Changes to this value are not verified
2020-12-01 21:30:37.008 Detail, Node005, Notification: ValueChanged
2020-12-01 21:30:37.023 Detail, Node005, Notification: ValueChanged
2020-12-01 21:30:37.295 Detail, Node006, Received: 0x01, 0x10, 0x00, 0x04, 0x10, 0x06, 0x0a, 0x32, 0x02, 0x21, 0x34, 0x00, 0x00, 0x02, 0x1e, 0x00, 0x00, 0xce
2020-12-01 21:30:37.295 Detail,
2020-12-01 21:30:37.295 Detail, Node006, Refreshed Value: old value=false, new value=false, type=bool
2020-12-01 21:30:37.295 Detail, Node006, Changes to this value are not verified
2020-12-01 21:30:37.295 Info, Node006, Received Meter report from node 6: Power=54.2W
2020-12-01 21:30:37.295 Detail, Node006, Refreshed Value: old value=0.0, new value=54.2, type=decimal
2020-12-01 21:30:37.295 Detail, Node006, Changes to this value are not verified
2020-12-01 21:30:37.296 Detail, Node006, Notification: ValueChanged
2020-12-01 21:30:37.302 Detail, Node006, Notification: ValueChanged

kreene1987 · December 2, 2020, 7:22pm

Did you ghave this tool working for 1.6 OZW (beta) integration? Or is it only for 1.4 Z-Wave integration?

I am also experiencing a weird lag over the last few days, but am in the middle of transitioning from ST to HA, so it’s likely related to 2 networks battling for bandwidth.

nappyjim · December 2, 2020, 7:47pm

@kreene1987 what tool are you referring to?

I’ve tried running the scene (and script) on both 1.4 and 1.6

kreene1987 · December 2, 2020, 7:50pm

Sorry referring to the z-wave graph tool in HA.

nappyjim · December 2, 2020, 8:12pm

@kreene1987

Gotcha, I got the tool working. Apparently chrome doesnt like javascript or something? Loaded in Edge and Firefox fine.

kreene1987 · December 2, 2020, 8:13pm

Mine is blank in all, but I think it’s because it is looking at the native Z-wave integration and not the add-on for ozwdaemon/OpenZWave.

Learning a lot quickly with ST being SO BAD right now.

nappyjim · December 3, 2020, 4:04am

So I think its a home assistant/multicasting issue as @jtronicus pointed out.

Here’s a video with the original 5 switches, plus two more (behind me in the video, you cant see) connected to Hubitat C7.

EricM_Inovelli · December 4, 2020, 7:04pm

In addition to what has been said, HA does not support S2 at this time (I believe). So, if you added the switches with the “Add Node Secure” option, then communication will be S0. S0 creates 3x the amount of traffic and can cause problems with HA. It will probably help to use the “Add Node” option instead.

I see that you tried secure vs non-secure. That surprises me that you didn’t see a significant speed boost with non-secure.

nappyjim · December 4, 2020, 7:49pm

@EricM_Inovelli

Sorry kinda long…

Yah no real difference. I just re-paired them yesterday as non secure (just choose “add node”) and my issues remain. I dont want to switch to Hubitat because of all the things that CAN pair to HA that cant pair to Hubitat.

I even tried re-writing the node red “scene” to say

Turn on kitchen overhead light
Wait until kitchen overhead light is true
Turn on kitchen table light
Wait until kitchen table light is true
Turn on living room overhead light
…

You get the idea.

I thought surely, this would at least work in a nice smooth sequential state with lights turning on in 1-2 second intervals.

And then there I sat. Kitchen overhead light turned on and now I waited 10 sec for kitchen table light to turn on. And the issue moves, so once again, I cant pin it down to 1 switch.

Checked my mesh, and multiple devices are directly connected to the hub.

The last thing I am going to try before accepting defeat and just living with it until maybe HA changes to multicast is, I just ordered a Rasp Pi4. I am going to load that up, pair the switches, and then place the hub directly in the kitchen just to see if even though my computer currently hosting HA is on the same floor, 15 feet away from the kitchen, it does not have direct line of sight to the switches. Placing the pi into the kitchen, i will have direct line of sight. I just want to SEE if this makes any difference. But shouldent, as thats the whole point of the Z wave mesh, right??

Bry · December 4, 2020, 8:22pm

I have no idea what’s up with your scene, but wouldn’t it be easier to just write a rule to do five things, simulating a scene:

Turn of dimmer A
Turn of dimmer B
Turn of dimmer C
Turn of dimmer D
Turn on the light

It would be interesting to see if you encounter the same issues using another technique.

nappyjim · December 4, 2020, 9:33pm

@Bry can you specify what you mean by a “write a rule”? I use the term scene very loosely…

Heres what I have tried;

Setup script in Home assistant to turn each light off/on. Tried running the script directly from home assistant by pressing the play button or through node red, having it trigger off the “scene” of me pressing down 2x on some switch
Setup a scene in home assistant performing the same as above. Turn on the scene directly through HA and have also tried having it be triggered through a double tap of some switch.
Write logic in node red that when it sees a double tap of some switch, perform various service calls. I’ve tried this multiple ways, the last being as I described in previous post of having it turn on one switch, then waiting for that state to be true before moving on to the next one. See below…

image1010×636 57.8 KB

nappyjim · December 4, 2020, 11:57pm

So I setup the rasp pi 4 and put it in the kitchen so that the stick can physically “see” every switch in the scene…And it did help.

Its not as fast as running it multicast on the Hubitat (which was still sitting in the office, not in line of sight), but better than running it from the rasp pi sitting in the office.

Which still kinda bums me out as that was another one of the advantages of z wave, is that the devices didnt need to be within range of the hub as long as they were within range of another switch. But its not too bad, I got some space above the fridge I can set it.

nappyjim · December 5, 2020, 5:41am

Soooooooo after more testing, I found a few more things

Location REALLY matters (and network heal works): after moving the pi to the office again, healing network and re-running scenes using various methods (HA script, HA scene, node red logic), the delays were pretty bad again. So it must be when in office, the direct connections to the hub drop so everything is being funneled through 1 node. When I moved Pi back to kitchen and ran network heal, and then re-ran same tests, everything was noticeably faster.
The fastest way to complete my scene (turning OFF 1 light, turning ON 4 lights) was using the following node red logic below. Since HA cant multicast, having those waits in there really make a difference and actually perform the scene faster than if I take those wait nodes out. Also tried one service call node turning on all the lights and one more to turn off the 1 light. Tried same as below but removed the waits. Tried running a HA script. Tried running a HA scene.

Heres video off the ‘OFF’ scene and the ‘ON’ scene. The lights that turn off last in the OFF scene are 2 wyze smart bulbs that must go through cloud, so that was the slightly longer delay there.

drphungky · December 8, 2020, 3:10pm

Just another suggestion that could add small confounding factors. I had a similar issue with slow zwave (mine was solved by adding non secure as was already talked about here). However, I also noticed there was a LOT of traffic still happening after the scene, so sometimes I would test something, then if I didn’t wait a full minute or so, the next time I ran whatever command I was running, it would be slower due to HA still doing some zwave status updating. So make sure when troubleshooting to give enough time in between test cases for everything to really reset.

jtronicus · December 9, 2020, 1:15am

If you are using the OpenZwave beta component (or OZW 1.6), you could try adding the following lines to your lzw31-sn.xml config file to see if it helps:

  <CommandClass id="38">
    <Compatibility>
	  <NoRefreshAfterSet index="0">true</NoRefreshAfterSet>
	</Compatibility>
  </CommandClass>

Once updated, you would need to refresh node info on each of your switches. This should cut the amount of zwave traffic significantly by preventing OZW from requesting an update every time it sends a command.

I am not sure if this works on the old zwave component (OZW 1.4)

nappyjim · December 9, 2020, 2:04am

@jtronicus i had to go back to OZW 1.4. With 1.6, if I had to restart the add on for any reason, it was a crapshoot as to whether it would load or not. Apparently its some known issue with how much data the USB transfers or something?? I dunno, over my head.

Went back to 1.4 and will deal with the service restarting everytime I restart home assistant; until 1.6 comes out of beta stages.

PaulT · December 9, 2020, 2:15am

I have 29 zwave devices (mostly inovelli gen1) and don’t see the issues you are talking about.

I am running 1.6 beta with zwave.me dongle via USB pass through on a NAS based VM.

Now zwave.me is basically an oem silicon labs usb stick so they run much newer zwave fw than the Aeotec does.

You could try checking under 1.6 in the ozw admin to see what you packet stats are etc. to get a feel of issues or not. As for secure pairing, shouldn’t that depend on the dongle used more than HA? You might also want to hit the JA discord zwave sub forum. They have big zwave brains there too.

stu1811 · December 9, 2020, 3:15am

I’m starting to look into HA hosted in a vm. Which vm technology are you using?

PaulT · December 9, 2020, 3:35am

@stu1811 I have a Ryzen based QNAP NAS which runs a “branded” version of basically Libvirt/QEMU. I am then running USB pass-through for the Z-Wave dongle “into” the VM so it is visible to HA.

The only thing I had to “tweak” was making sure to use the USB Serial device ID (Supervisor > HW) as the OZW Add-on Serial address. That way if the host VM’s USB port changes, HA has a stable configuration.