I have been reviewing my logs more lately and keep finding strange anomalies. My latest is all the line items created by a single off command in a rule.
I have a "clean up" rule that runs at 2, 4, 6 AM each day. The rule simply sends an off command to every light that is controlled by the hub. Below is the log for one of devices controlled by this rule.
I see the off [digital] at the scheduled time which makes sense. I don't understand what all the repeated off [physical] log entries are for because there is no one on site, so no one pressed the physical switch. My only hypothesis is maybe marginal Z-Wave coverage and the node is retrying the command acknowledgement?? But why tagged as physical?
Just trying to understand this better (and clean up unneeded entries).
I would recommend enabling debug loggging on the device, so you can see whats causing the events. Should help narrow the issue down to either the device or the driver.
It’s a Leviton in wall on/off switch. It’s either a DZ15S or a DZS15 yes Leviton had the “wisdom” to name two similar switches this way… it is a few years old but I think it was Zwave plus…. I’ll check later…
I can’t check because I am away from this house for a bit longer.
It was originally paired as a genetic Zwave device. It is using the generic Zwave smart switch driver.
Based on your comment I guess I could just try a Leviton driver and see what comes of it….
update: The plot thickens.... it looks like the Generic ZWave smart switch is the proper driver for this device. Also the DZ15S is ZWave Plus but the earlier DZS15 was pre ZWave plus... Now Leviton has an 800 series switch that supersedes both of these... ZW15S
Maybe I cut my losses and move to Zooz ZEN71 as I am switching all my dimmers to ZEN72s....
Looks like the switch is reporting to the hub repeatedly that it turned on.
Since the hub didn’t ask for all those duplicate status updates, it marks the events the only way it knows how, as a “physical” event caused by something else.
