Would be nice to get some feedback on if this issue is being looked into, Thanks.
Can't reproduce it yet, but I've created a GitHub issue and will be on lookout for similar occurrences.
1 Like
Thanks. Yeah not sure whats causing it, but I can easily reproduce it with any of my Leviton DZ6HD or GE dimmers. And I never noticed it until the first 2.2.3 update.
I also noticed that even with motion lighting I see 4 events in the log for 1 action.
How many concurrent zwave events are happening with this and which hub do you have?
C7 hub. Latest firmware (2.2.3.145). It also happend on the last few 2.2.3.x versions. This is an unpredictable occurrence - sometimes everything is fine. Other times, there is a burst of these log messages for one physical or control action.
As a further investigation, I wrote a simple JavaScript program to monitor the eventStream port and these messages are repeated on the eventStream - so its not just a logging issue, these are events that propagate through the system. That can't be good for performance!
I wonder if it’s related to this
I have a C5 hub, if I turn on a single switch I will see 4 events for that single action. It doesn't matter if it is from the physical switch, HE or motion lighting, all will exhibit the same issue.
This would also prob explain the increased latency I have seen also.
I just saw something like this on my C7 with the 145 firmware while I was running a zwave repair.
Just as the Zooz Double Plug was starting repair, it reported power, and the logs showed the reports duplicated a dozen or so times
Throwing my hat into the ring too. I am seeing these multiple logged events for single actions very much the same as the others are reporting. Its a very common occurrence and can't be good for overall performance both to the mesh and the hub itself.
For reference, I have a C7 Hub running version 2.2.3.145.
Did you find a solution - I'm still having this problem. I'm hoping this is to be fixed in the next firmware (2.2.4), but I haven't seen much to indicate one way or another if that's the case.
The drivers need to be fixed, not much else we can do unfortunately.
I'm not so sure it is universally a driver problem based on sniffer logs...
It is hard for me to tell for sure though, because it rarely happens on my c7 hubs.
A couple times I've caught it though the hub was sending a command, and getting responses from the end device in the expected time frame, but then sent the same command out a bunch more times.
And in those cases I've verified it was not the driver asking it to send the commands multiple times.
So it is still a bit of a mystery to me. I'm just happy it is very rare on my hubs. 
My guess is this is one of those things that will magically stop happening at some point after an update, and no one will know exactly why.
1 Like
Well something changed in the 2.2.3 versions, because when I reverted back to 2.2.2 the issue was not present.
There may be differences between hub versions as well because I am on a C4, so not sure.
1 Like
If you look at the hubitat github site, this driver: (HubitatPublic/examples/drivers/genericZWaveCentralSceneDimmer.groovy at master · hubitat/HubitatPublic · GitHub) you can see that at the 2.2.3 they changed to a new way of handling secure encapsulation ("switch to internal secure encap method"). Presumably, they would have also made similar changes to other drivers to use this new security encapsulation. So it certainly looks like drivers were significantly changed in 2.2.3 - it would seem that's something that deserves focus.
Yeah, they changed/improved the secure wrapper in 2.2.3.
The driver on the device I saw repeat messages on didn't use the new wrapper though.
Doesn't mean it isn't related somewhere under the hood though. Dunno.
I'm just glad it is a short lived, maybe once a week thing on my hub.
And I've never gotten my development hub to do it at all, which is unfortunate as I would have better data to work off of. I'm not willing to try and 'break' my production network to try and reproduce it more frequently there.
I wish that was the case but I can repeat the issue on any of my Z-Wave dimmers/switches.
I'm reverting to 2.2.2 to see if that is better then holding out for the 2.2.4 firmware, then plan to raise issues again if they persist (from postings on this message board, the Hubitat staff seem to be addressing many bugs in 2.2.4 -- now I just have to wait and see). For me, 2.2.3 was a giant mess.
1 Like
