Maybe check to make sure the dimmer is on firmware version 1.2? The earlier versions were a bit buggy.
I have over a hundred of these. I've been using the DZ6HD specific driver since it was introduced and have had no problem with the driver itself. It's possible that you are experiencing coincidental issues with Z-Wave.
I suppose it's possible that there is some DZ6HD specific Z-Wave issue, but I find this doubtful because it should be using SiLabs chips just like every other 500 series device.
I'm not sure what effect will exclude and re-include will have... It will choose the same DZ6HD system driver (you are using the system driver, yes?). Before excluding and re-including, I'd suggest the following:
- Double check that you are using the System DZ6HD driver.
- Do a configure in the driver.
- Do a repair.
If you haven't done so, I would also check the device firmware. I believe the current version is 1.20. You can check it with Mike' Basic Z-Wave tool.
Hello @dennypage (I've been a great fan of some of your work!)
As you can see from my first screen shot, I was using the built in driver of "generic zwave dimmer", before moving to 2.2.4.151. That release brought with it, a new built in driver called "Leviton DZ6HD" .
I suspect (though, I have no proof) that this was the cause of the issue.
Please note: C7 only.
P.S. Thanks very much for the suggestion to check the firmware version:
Thanks 
FWIW, the DZ6HD system driver has been around for some time. Since 2.3 at least.
[Edit: Since 2.2.0 https://docs.hubitat.com/index.php?title=Release_Notes_2.2.0]
I still want to point out that this driver reports all events as "physical" no matter if the light is turned on from the physical dimmer or HE web interface.
The Generic Z-Wave Smart Dimmer driver does not exhibit this issue.
Now that you mention it... it depends upon where you look at the event. In the events list for the node, it says "physical" almost all of the time (but not 100%). However if you look in the log, it is usually correct. Yes, I would consider this a bug, although a minor one. @bcopeland @mike.maxwell
Yeah I was looking at the logs or events for the device itself. I have no way to check the node since I have a C4 hub.
Can anyone advise if this driver has been updated and working properly now? I'm hesitant to try the new driver because the last time I did, there were problems that arose that couldn't be solved from switching back to the generic driver. Had to factory reset my switch and re-do all my automations.
There haven't been any recent changes to this driver.
Ok thanks. I'm still getting dozens of log entries for my leviton switches on the generic smart dimmer drivers and was hoping this driver would fix that.
Doesn't sound right, even for the generic driver, can you post a screen shot example for just one device?
Here's another switch, not a dimmer like above, doing the same:
One more for good meassure
All Leviton switches/dimmers updated to firmware 1.2
These drivers can be modified to not display duplicate description text to some extent, or you can turn that off in the driver, but this problem is not driver related.
In one case above I see the device sending an off state event 7 times in under one second, this can only be a mesh issue such that the device is not receiving the ack from the hub, so it sends it again, this is further supported by the fact that the count of duplicate events isn't always the same.
What I mean about that is that some driver device combinations could issue two on or off events for every action, but it would always be two.
The odd thing is that it only became an issue after the big update (2.2.3?). My Schlage locks also became less reliable at that point and my sirens/chimes are extremely laggy. None of these, including the duplicate entries, were issues before the big update. So frustrating!
Is this a c5? or a c7 that were talking about...
It's a C5
I also have a tonne of z-wave plus switches all throughout the house and my z-wave network wasn't an issue prior to the update. Sirens/chimes sounded almost instantly upon opening a door, schlage locks were 80 % reliable statuses instead of the now rarely showing the proper status.
Ok, most definatly not related to the driver or the platform version.
There haven't been any changes in the c5 zwave code in quite some time, probably close to a year or more.
