As reported here by others, ver1.0 of strip does not work right with built in driver. Can someone please look into this @Hubitat_Staff .
Does anyone have a custom driver perhaps? Thank you.
Might be helpful if you posted a screenshot of z-wave logs while you operated the ZEN20.
@aaiyar
Sequence of events:
Device added, Configure pressed. At that point, I tuned on each of the 5 outlets physically on the device - not reported. Then I went to Ch1 child and did off - on. Not reported on the child log, but visible on the parent log. The child status never changed.
There is a Z-Wave Plus logo on the bottom of the unit.
Parent log:
Child 1:
Those are probably useful, but I specifically indicated z-wave logs (from Settings -> Z-Wave Settings).
@aaiyar
My bad and thank you for looking into this. Here is what I get when I send on/off/on/off. The device does trigger it's relay very fast, it's the status report for individual channels that I am after.
I know this is a bit old now, but for anyone who is still wondering, the built-in ZEN20 driver will be fixed -- in a future build, possibly still a future 2.3.9 hotfix -- to address the issue with on/off commands for the child devices not updating their status (if the device responds).
However, the ZEN20 V1 doesn't appear to send any reports to the hub for physical events, so the driver per se can't do anything about that. If you really need these events, polling might work, though that's generally preferable to avoid, otherwise "digital" changes should update things (or the newer versions of the ZEN20 all seem to send events on their own for digital or physical changes as expected).
More details:
