Eliminating unnecessary Z-Wave network traffic

[Ltek]

Battery z-wave devices can be slow due to wake-up and connection times. In my experience, and that reported by others I have seen, this has not been a network communication issue. Using USB/Other powered units has not been an issue.

the slower-ness I'm talking about is 'response', not wake/reporting. For motion sensors I want the fastest response possible so lights can come on, entry notifications happen, etc. Zigbee has been generally faster even when my Zwave network was small and I'm using deConz, which is an additional hop to get to HS -- vs HS's Zwave that my zwave sensors are communicating directly with.

[ksum]

Ltek For the motion sensor to respond on most battery powered motion sensors it has to "wake up" the z-wave portion of the sensor and send the message out. This is "asleep" to save battery life. The motion sensors I have on USB respond and result in a light turning on faster than I could flip the switch. Near Instantly and just as fast as any other units I have used. I have also had a couple battery units which turned a light on just as quickly. At 80 nodes, I do not have a huge z-wave network, but it isn't small either. That said, I have never done anything other than optimizations to eliminate traffic. I use to poll a few older style switches, but have removed that.

[Ltek]

MalcolmS I'm now getting a few Zooz dimmers showing "Failed sending Z-wave command to device" ... its consistent on the same 3 dimmers. You still getting those errors... what are they on?

[MalcolmS]

MalcolmS I'm now getting a few Zooz dimmers showing "Failed sending Z-wave command to device" ... its consistent on the same 3 dimmers. You still getting those errors... what are they on?

Mostly, but not exclusively, my errors occur with Qubino Mini Dimmers. I find if I stop and restart the Zwave plug every three hours or so that fixes it!

[Ltek]

Mostly, but not exclusively, my errors occur with Qubino Mini Dimmers. I find if I stop and restart the Zwave plug every three hours or so that fixes it!

"fixes it" ... funny right.

I was seeing it when I first installed the 47 new dimmers and it stopped after I optimized. But now seeing it randomly (not a lot, but they do miss commands) with different switches and a restart does not "fix it" ... After seeing a bunch from 3 dimmers, I did a restart and 1.5 hrs later I saw it happen once on a totally different dimmer. ALL have 20+ strong node routes. HS's zwave plugin v3 has been beta for 10 years, and v4 looks like its alpha; v5 will be called 'almost alpha'

[MalcolmS]

All of mine have direct routes to the controller.
Do you use the Linked Device feature at all? I do in a couple of rooms and was going to try removing the links to see if that 'helped'.
I feel your pain.

[Ltek]

All of mine have direct routes to the controller.

I just checked many devices (not all since it takes forever)...
Most have "Z-Wave System SmartStick (Node 1)" as the first 'Neighbor Node'. I'm not sure why a few dont, even one with 30+ nodes but not the SmartStick -- many devices in the vicinity of the SmartStick so distance should not be an issue. Any idea how to 'fix' this and get the SmartStick into the Neighbor Node list? I dont think this is causing the issue but good to try to ensure they all have direct routes if possible.

Do you use the Linked Device feature at all? I do in a couple of rooms and was going to try removing the links to see if that 'helped'.

I was using Linked Devices in 5 rooms and removed all of them as that 'feature' is amazingly buggy. I then tried using Zwave Associations (directly in the devices) but after a week of testing those same 5 rooms concluded that Homeseer doesnt do it correctly OR Zwave associations dont work proper OR Zooz doesnt do it correctly... or some combo of those three. Associations worked fine sometimes with rooms with only 2 dimmers... but not always. Room with 4 dimmers it never worked after trying multiple 'resets' and different methods, even daisy chaining.