I'm having an issue that I can't seem to avoid. I can have light switches show single events in the logs but as soon as I turn on some rules I made I see multiple on and off physical events and it seems to be lagging out my Hubitat.
Here is an example rule that as soon as I trigger results in the repeated events. I've tried several variations of this this rule and it keeps happening.
dev:542019-05-08 11:01:51.627 pm infoKitchen Sink Switch is off [physical]
dev:542019-05-08 11:01:51.437 pm infoKitchen Sink Switch is off [physical]
dev:542019-05-08 11:01:51.186 pm infoKitchen Sink Switch is off [physical]
dev:2892019-05-08 11:01:50.976 pm infoKitchen Entrance Switch is off [physical]
dev:2892019-05-08 11:01:50.744 pm infoKitchen Entrance Switch is off [physical]
dev:542019-05-08 11:01:50.564 pm infoKitchen Sink Switch is off [physical]
dev:542019-05-08 11:01:50.326 pm infoKitchen Sink Switch is off [physical]
dev:542019-05-08 11:01:50.116 pm infoKitchen Sink Switch is off [physical]
dev:2892019-05-08 11:01:49.904 pm infoKitchen Entrance Switch is off [physical]
dev:2892019-05-08 11:01:49.697 pm infoKitchen Entrance Switch is off [physical]
dev:542019-05-08 11:01:49.474 pm infoKitchen Sink Switch is off [physical]
dev:542019-05-08 11:01:49.260 pm infoKitchen Sink Switch is off [physical]
dev:542019-05-08 11:01:49.073 pm infoKitchen Sink Switch is off [physical]
dev:542019-05-08 11:01:48.818 pm infoKitchen Sink Switch is off [physical]
dev:542019-05-08 11:01:48.588 pm infoKitchen Sink Switch is off [physical]
dev:542019-05-08 11:01:48.365 pm infoKitchen Sink Switch is off [physical]
dev:2892019-05-08 11:01:48.128 pm infoKitchen Entrance Switch is off [physical]
dev:542019-05-08 11:01:47.899 pm infoKitchen Sink Switch is off [physical]
dev:2892019-05-08 11:01:47.695 pm infoKitchen Entrance Switch is off [physical]
dev:542019-05-08 11:01:47.473 pm infoKitchen Sink Switch is off [physical]
dev:2892019-05-08 11:01:47.275 pm infoKitchen Entrance Switch is off [physical]
dev:2892019-05-08 11:01:47.044 pm infoKitchen Entrance Switch is off [digital]
app:3652019-05-08 11:01:42.855 pm infoMirror Kitchen Off: became False
app:3652019-05-08 11:01:42.813 pm infoMirror Kitchen Off: Kitchen Sink Switch switch off
dev:542019-05-08 11:01:42.679 pm infoKitchen Sink Switch was turned off[digital]
app:3652019-05-08 11:01:39.423 pm infoMirror Kitchen Off: became True
app:3652019-05-08 11:01:39.360 pm infoMirror Kitchen Off: Kitchen Switch switch off
dev:532019-05-08 11:01:39.258 pm infoKitchen Switch was turned off[physical]
Am I doing something wrong or is this just my devices polluting the z-wave network and the Hubitat is having to digest it and causing the system to lag.
I'm probably not understanding the logic, but it appears to me that triggered rule will never be true. The trigger is either switch turning off but the definition is for either on. That can't happen, can it?
If any of the two switches turn off after being on it will test to see if the other switch is on still and then turn it off and some others. It's basically attempting to mirror switch states and I added the rules to avoid the kitchen from turning into a rave as they fight turning each other off and on when I'm a little faster on the physical switches than the Hubitat. The If statements are unneeded and added in an attempt to try and stop repeating events.
Thank you, looks like to me it is the device sometimes doing it. Turned on debug logging for the device and sometimes is spits out several hails which I assume are status change alerts.
So I actually just today finally figured out what was causing this by chance after noticing one device wasn't doing it.
If I make the leviton switch a Generic Z-Wave Smart Switch (which is what it joined as) it does this. If I do it as a Leviton Generic Z-Wave Switch it doesn't.
Not really sure what the difference is between them as products but like a tale as old as time it came down to drivers.
@Rich, I posted a day or so ago about similar activity with my Leviton switches but only after updating the firmware to version 1.2 from 1.13. Thanks for posting your findings. Does anyone know if there is any functional difference between the smart and non-smart version of the Generic Z-wave dimmer.
Looking around to find out the difference between the smart driver and the non-smart driver, from this post: Built in "Z-Wave Generic Dimmer" vs "ZWave Generic Smart Dimmer") and this post: Zwave smart switch and dimmer fingerprints it seems the non-smart driver won't allow the device to report it's status to the hub after a physical on/off? Definitely not ideal. What are the chances the smart driver can be updated to fix these issues?
I've also come across this non-built in App Driver code for leviton switches but I don't have any experience with using custom drivers and am a little hesitant to try it out.
The smart dimmer is optimized for devices that are known to report properly, generally Z-Wave+ devices.
In the end which ever driver works the best for the specific device in question is the one you should use.
