I’m hoping to have the ZEN17 driver completed by tomorrow morning, but I figured it would probably be a good idea to post my implementation plan ahead of time in case anyone has suggestions or throws a wrench into my plan…
When the S1 and S2 Input Type Settings are set to Momentary, Toggle (any), Toggle (up/down), or Garage Door:
-
The driver will display the main switch on the dashboard and just the 3 switches (main/R1/R2) on the device details screen.
-
It will have the “Dashboard View” setting that allows you to see the Large tile on the dashboard with all 3 switches.
-
I’ve already finished this part of the driver.
-
It’s basically the same implementation as the ZEN16.
When the S1 or S2 Input Type setting is set to any of the other options (motion, contact, water, etc.):
-
The look/behavior will be the same as above, except there will also be a tile for each input (S1/S2)
-
The S1 and S2 tiles will be a custom capability that displays the Input Type and its value (Contact Closed, Motion Active, Water Wet, etc.). If only one of the input types is set to a sensor value then the other S# tile will show something like “N/A”.
-
The driver will support all of the capabilities that are available as input types (Motion Sensor, Contact Sensor, etc.), but only the selected input type’s corresponding capability will change with the state of the input. The other capabilities will always be set to their inactive state. (inactive, closed, dry, etc.)
-
Since the S1 and S2 tiles on the device details screen show the type of sensor and its value the actual capabilities won’t be shown there.
-
When selecting the device in a Routine you’ll see all of those capabilities.
-
I don’t plan on including the “Heat”, “CO”, or “CO2” input types, but I can easily add them later if requested.
-
The manual says you need to remove the device and join it again after changing the input type settings, which might still be required, but I won’t know for sure until I start testing that part of the driver…