Multiple log entries for a single device event

So, @mike.maxwell - I looked into this and the overall network performance is solid, however, without more debugging tools (hint, hint. :slight_smile:) it's difficult to tell for sure.

What I do know is that the following device is literally less than three feet (line of sight) from my hub and is still apparently not getting a fast enough response. Again, without Z-wave debugging tools, I'm guessing here, but I'm pretty sure it's not going through another hop in the Z-wave mesh to reach the hub (this device is a Sensative Strips Contact Sensor - battery powered):

[dev:481] 2020-05-06 02:38:54.044 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:53.988 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:53.885 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:53.858 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:53.799 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:53.773 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:53.767 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:53.706 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:53.696 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:53.595 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:52.985 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:52.956 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:52.937 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:52.768 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:52.727 pm [info] Great Room South Left battery is 75%
[dev:481] 2020-05-06 02:38:52.645 pm [info] Great Room South Left battery is 75%

I know the Hubitat team is working on more performance improvements in future releases, but this has to be somehow related, right?

Thanks.

You know that Z-Wave debugging tools are available, right? Zniffer is a 'free' install, but requires a Windows computer to run it on (I use a virtual machine (VirtualBox) for Win10,) as well as a flashed ZWave radio. (around $40)

You'd be surprised by the Routing, I suspect. It has to do with ZWave's intention to build the largest mesh.. large in area or volume. There's a 4 hop limit and therefore, a device 3 feet away can be ignored for one 7 ft away.. simply to make the 'sphere' larger.

1 Like

Thanks - was hoping for ones built into Hubitat, but yeah, I can try to get it running with my Aeotec Z-stick and the single Windows computer I keep around for firmware/radio updates.

It's not really possible to build it in...

  • It's a 2nd ZWave radio in 'promiscuous' mode (so it can listen to all Network numbers)
  • A 2nd radio in such close proximity will cause interference.
  • A permanently installed radio for the 3% that give-a-damn is $$ wasted.

I would NOT use your Aeotec Z-Stick for this. You have to wipe it out and install one-off code to be just a listener. THere's no assurance you can turn it BACK into a regular Z-Stick. There's a chance and if you want to experiment for us and let us know how it goes.. I'm willing to have you use your Z-Stick :smiley: :smiley: ( you know that was humorous, right? )

Point taken - I think I'll find the $40 somewhere for a 'permanent' sniffer. :slight_smile: