Thanks!
I’ll try changing drivers to see what the results are.
That helps! Thank you.
Is it known why the logs don’t show each of the two state requests?
Sorry, I don’t understand the question
The two state requests were mentioned in your reference:
Attached is a screenshot of logs for a device using the driver with the bug but it looks like there are no first responses marked as digital; just the second responses marked as physical:
This happens alot with my devices. In some cases a driver fix can help parse the responses correctly, assuming the device has unique messages for physical vs. digital. It should be possible for the hub to know if the hub itself sent the command or was from an external source, but it might be too much work..I have no idea
I've got several Leviton DZ6HD dimmers. I've found that changing the driver doesn't fix the [physical] or [digital] reporting.
To really answer your question about what is logged as a state change, I would have to look at the source for the driver. I do not have access to the source. My knowledge comes from sniffing the Z-wave packets between the hub and device and from prior discussion about the bug with one of the driver developers.
If memory serves, the first one is not logged because the flag incorrectly says it is in response to a digital request, which should already have been logged. When the second hail comes, the flag is clear so it is logged as a physical event.
For me, using the Generic Z-Wave Smart Dimmer driver instead of the DZ6HD driver seems to work. Are you on the latest firmware for the switches? Firmware below 1.2 could be problematic, if i remember correctly.
Yes, definitely advisable to Update to latest firmware. 1.22 fixed a rare lockup that happened during physical operation which required an air gap pull to reset. Latest firmware (that I know of) is here.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
