Yeah, @jvm33 your seeing much more events then I am. After looking closer at mine they are only in sets of 2, with the exception of the dim percentage with 3. There may be two different issues here even, or possibly still related.
I am not trying to say that a storm isn't a storm, there could be storms, but do I think they are the FIRST thing to imagine?? It's the old hoof beats question, why think of Zebras? I'm ok with thinking Storm after determining it's not a mesh effect... 
v2.2.3.145 is the latest and in the area of C-7 ZWave, the best, thus far. The Storm Topic was a factor in the last week of July and the first week of August.. a month ago. I am ready to give v2.2.3.145 the benefit of the doubt here, that those issues got quashed.
I've run Zniffer, almost continually for the past month... (a few times a day I'll stop then restart the capture to discard everything to that moment,) but I'm not seeing discovery frames in that quantity.. yes, they do occur, just not (for me) in any alarming pattern.
This has all been helpful - one other thought I had - I have a HomeSeer Hubitat Plugin that I'm using. I'm going to disable that tonight to see if, just maybe, that plugin is generating lots of "get" request - I think that's a long shot, but it still makes sense to eliminat possible third-party plugin interactions. I've already taken the Desktop app off my system, so
@lewis.heidrick. Thanks for all the suggestions yesterday. I've noticed there's been a firmware update about once a week for C7 issues - I'm going to wait until the next one, see what happens after that, and then resume trying to fix this problem.
Also, on another theory, I think the last few times I saw the problem, the problem device was in a lighting "Group" - maybe there is a problem with the Groups/Scenes app. I'll experiment with this theory a bit more (i.e., by getting rid of the use of Groups ).
There is still an issue with generic drivers causing sets of 2 events for every action, which seems to happen irrespective of the hub version. I also suspect this to be the culprit of the increased latency. I just don't want this to be overlooked because I know there is a lot of changes happening to the C7 version.
Also the issue of the driver displaying 2 sets of events for both digital and physical, for just 1 action. Hopefully the Leviton DZ6HD driver is also fixed, as this has been broken since it's release.
I know a lot is going on with the C7 but these latency /driver issues were not present in firmware that was released before the inclusion of the C7, so it really should be a higher priority.
1 Like
I have the same issue of this when I use a community driver instead of the generic driver for my Honeywell Z-Wave Plus Dimmers (Non Enbrighten version). Using the generic driver doesn't cause the issue.
I have mostly the Leviton DZ6HD dimmers, but I do have 1 of the GE 14294 dimmers which also exhibits the problem as well. It may be that this only affects certain dimmers/switches, but either way this is a bug. Personally I would prefer to use the Leviton driver that was written specific for my devices, so hopefully the issue is fixed for both the generic and the Leviton drivers.
I switched back to the generic driver for the honeywell switches and it mostly went away although I still have a zooz power strip that is very enthusiastically telling me it's on. At least it isn't locking up anymore. Hopefully they'll track it down.
The issue still exists with the generic driver for me. If I switch to the Leviton driver the multiple events disappear but then all events are reported as physical, so it breaks automations like motion lighting then may need to know if the event is digital/physical for certain overrides.
Although even at this point with the generic driver I see both physical and digital events, so IDK what is working.
Sometimes devices don't handle physical or virtual events and just send whatever they feel like. I saw this a lot on ST, not so much now on HE but occasionally. I haven't messed with Leviton switches much other than regular occupancy switches (non-zwave/zigbee)
There was a case I saw a long time ago about someone using the non smart generic dimmer driver and it working correctly for them. I'll see if I can track it down.
Also came across this article that discusses Leviton dimmers and physical presses but it's quite old also.
The Leviton dimmers are Z-Wave plus and with the generic driver they did work in the past with the generic driver. It used to separate the events into digital/physical correctly and did not have multiple events, so this was broken at some point.
The Leviton driver never worked from its inception when it came to separating the events by physical/digital.
The thing is the Leviton DZ6HD driver is specific to that particular device, if it does not have the same functionality/compatibility as the generic driver then what is even the point of having the driver? It rubs me the wrong way too because it seems that the HE staff has no intention of fixing this driver, and if this is the case then why even have the driver included if its broken?
No one ever likes to hear this, and will argue it all day long, but multiple messages like that are almost always (like 99%+ in my experience) a mesh issue.
Now, the "mesh issue" could be being caused by the hub - so I'm not saying it is not hub related - but still.
Yes, little things like logging physical and digital for the same occurrence can happen, depending on how the driver is coded. But that isn't a big deal as the event will be de-duplicated anyway before an actual event is made. So that isn't a big deal.
The only way you can prove it isn't mesh related is get out a sniffer.
I'm not sure what the exact issue is between the two drivers but we can always chime in support and ask them to take a look.
If this is the case then why with no additional devices removed/added did this issue start happening around the time that the C7 hub came out? I have NOT touched my Z-Wave devices or moved anything in over 6 months.
It's possible they broke some drivers along the way. I'm sure they had to update a bunch of them to get them to play nice with the new stack. I'd still ask support to take a look.
I can't see your mesh or invisible radio waves....
The only way you know for sure if those messages are really happening is to use a sniffer on the mesh.
You are making assumptions that may/may not be right on what is happening. Without knowing what messages are actually flying around, it is just that - a guess.
All I can say, is after years (on and off) of logging zwave traffic, I have only seen repeat messages like shown in some of the pictures above when there were problems with the mesh. Again, the "problem" could be on the hub side/the hub itself - it is on the mesh too, ya know.
No way of knowing without low level data.
I understand this but without making any changes to my mesh and all of a sudden an issue that was not present now exists, with only a change in HE firmware you can see why I hesitate to believe it is my mesh. I have around 40 dimmers/switches spread all throughout the house and everything is Z-Wave plus, and for years it was working fine....
AGAIN, the hub is PART OF THE MESH TOO. I'm not necessarily saying it is one of your devices - although it still could be. Device routes are fluid, and change - sometimes for the worse. Devices get flaky at times. Etc.
The point is that you don't really know if it is:
- Mesh issue (device or otherwise)
- Driver issue
- Hub software issue
Because you don't know if the messages are really happening on the mesh. Without data, it is a guess. And that is OK - everyone makes guesses based on the information they have.
