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

I know, kinda long, but please read all if you can to help…

So I am not sure this is an inovelli issue, but I kind of tried everything else.

The issue is that a scene automation can be very slow/delayed. So I have a basic scene in my living room/kitchen where if I press down 3x on the paddle it will turn OFF 4 lights that are attached to red dimmers, and turn on 1 light.

Sometimes it will be super quick and accomplish this in a few seconds, other times it will take 20+ seconds. Heres a video of it taking 21 seconds: https://youtu.be/ujUJ03qaYC4

Heres a picture for refernence on the lights.
image

The video starts as soon as activated the scene and you can see nothing happens for 3 seconds, then 3 of the lights turn on almost at same time, then nothing for 10 seconds before the kitchen overhead lights turn on, then few seconds of nothing before the single light over the sink turns off . The video ends right as this happens if you look close.

Heres what I tried

  • Different Z wave sticks (Nortek and AEOTEC)
  • Different home assistant install. Tried it through a virtual PC and through raspberry PI
  • Different Z wave implementation through home assistant. Version 1.4 and OpenZWave Beta.
  • Take home assistant out of equation and use Hubitat
  • Programming the scene through Home assistant script and not node red
  • Factory reset the Z wave sticks and just added the 5 red dimmers involved in the scene
  • Tried pairing switches to Z wave hubs secure and non secure.

All 5 red dimmers have been flashed to 1.48. I’ve sent dim speed to 0, set AC power to neutral and set switch config to load only on all of them. All other parameters are the same and haven’t been changed.

Any thoughts as to a parameter I could try changing on the switches?
I don’t get why sometimes the scene will work super quick and other times, slow. And its never replicatable. Sometimes lights 1,2,3,4 will go quick and then 5 will be slow. Other times 1 will go right away, then long pause, then 2,3,4, then long pause, then 5.

The only Z wave devices I have are these inovellis so I cant rule out this is just a Z wave “standard nusiance” that I cant do anything about. But when posting this in Home Assistant forums, every is saying the time this is taking isnt normal.

I don’t have a Hubitat or HA. It seems to me that once the scene kicks off, the switch is out of the equation. So maybe a bit of delay in the switch communicating, but with the rest of the lag, I’d think that’s doubtful. I’m thinking more of a Zwave mesh issue. The Hub or HA users while have to weight in here.

How are the response speeds when you try to toggle any particular switch directly through a command vs through scene control? The longest I see with some of my massive (to me) scene controls on Hubitat with ~20 Z-Wave devices (all of my lights are ZigBee) is maybe 2 seconds.

I’m not sure what the interface looks like on Home Assistant, but Hubitat can give you good RSSI, RTT, and route info now. That would help identify any routing/bad actor issues in your mesh. Is there any consistency between scene activation delays over a period of a few minutes?

@fatherdoctor

No consistency, completely random. After I pulled of my R Pi to load home assistant on there (to rule out issues between virtual machine and z wave USB stick). I loaded fresh copy of HA, installed openzwave beta on there, paired the 5 switches, made scene to turn 4 off and 1 on. Ran it, and it completed almost instantly! I was like oh that’s it, something wrong between virtual machine and usb stick.

But then tried it again, 20 seconds. Tried again, 5 seconds. Tried again, 6 seconds. Tried again, 28 seconds.

Home assistant forum is also saying I should look at the mesh even though I only have 5 total devices. I’ll try to do that tonight.

If I toggle each one individually it’s nearly instant in the response, unless I try to turn off & on in quick succession.

@nappyjim It really does sound like a mesh issue. Try running a z-wave heal (it will take a little while even with only 5 nodes) and you might install this tool to get a fast human readable status of your mesh nodes.

Alternatively, it does appear that Home Assistant gives you a way to directly query the switches to get some great low level diagnostics (something you can’t do out of the box with Hubitat). After you heal the mesh, try to check the lastResponseRTT, retries, and sentFailed, values on the nodes that respond last.

1 Like

@fatherdoctor

Ignore this, figured out Chrome was the issue. Tried it with edge and I can see the mesh.

I tried that z wave mesh thing, I downloaded the .js, placed it in config/www

Added that code to configuration.yaml
Restarted home assistant

Where am I supposed to see it? I tried Add card, I didnt see anything new.

This may be your problem. In my experience, 13+ seems to be the magic number of Zwave devices for a good mesh. Where is your hub in relation to these 5 switches? You may have a device that has a weaker signal and is causing your mesh issuses especially with limited routes to get back to your hub.

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.

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

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.

@kreene1987 what tool are you referring to?

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

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

@kreene1987

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

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.

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.

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.

@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

  1. Turn on kitchen overhead light
  2. Wait until kitchen overhead light is true
  3. Turn on kitchen table light
  4. Wait until kitchen table light is true
  5. 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??

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.

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

Heres what I have tried;

  1. 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
    image

  2. 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.
    image

  3. 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…

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.