I don't anymore as I have control (emergency) off via room temperature. Am I correct in assuming that setting this value to zero will prevent the relay from shutting off via the driver?
That value causes the relay to shut off by itself with its own internal timer, not from the driver.
Well, I set the timer to zero and lets see if that fixes my problem. Something is definitely shutting off the relay and its not within Hubitat. 
You might want to consider still using this feature as a fail-safe mechanism. That way if Hubitat dies or locks up, the switch would shut off on its own after a predetermined period. Maybe something like 6 hours such that if the system if running unattended or if you pop out and Hubitat gets scrambled the fireplace would shut off. Yes not likely, but it doesn't hurt to add extra measures.
You already have some inherent protection via the thermocouple/thermopile in case the flame/pilot gets blown out. That protects gas flowing without flame. There generally isn't a fail safe for continuous operation though. Gas furnaces typically have spill switches on the vent lines and over temp limit switches to kill the gas but these aren't common on gas logs.
I feel controlling gas appliances should have layers of fail-safe to cover off the unintended cases where things don't always follow the nominal case.
Good idea, but the internal clock on these things will likely drift pretty significantly at longer intervals -- maybe that's not a big deal, but maybe it is.
Auto-off in seconds or just a few minutes is easy for it to handle, but going out into numerous hours gets dicey WRT to precision.
Precision (timing accuracy) isn't important as a fail-safe. It is meant as a catch all if the gas is enabled beyond x hours (or y minutes). If you set it for 21600 seconds (6 hours) it doesn't matter much if that is 5.2 hours or 6.8 hours. You still get the catch all safety net it is meant to cover.
Looks like there are some additional parameters in the newer firmware for the Zen52 relay.
I needed DC Motor mode which is parameter #29 but the driver only goes up to #27.
I was able to set what I needed using your Z-Wave Universal Scanner so I am set but, perhaps you could add these in when time permits? I didnt notice what firmware version I was on but when I first scanned these parameters were not there and after I applied the newest they were so I assume they were added recently.
Thanks so much for both these drivers and the Scanner - both are great!!!
I saved the output from the device data that I think you need:
."},{"num":28,"format":2,"size":1,"defaultVal":0,"range":"0..3","title":"Input Trigger","description":"Choose whether the inputs (wall switches) on the ZEN52 trigger the outputs (loads) or just send input reports for monitoring, keeping outputs separate."},{"num":29,"format":2,"size":1,"defaultVal":0,"range":"0..1","title":"DC Motor Mode","description":"Sync relay 1 and relay 2 to prevent them from being activated at the same time. Set value to 1 to enable the DC motor mode."}]
I am not entirely sure if it is an issue with the 3.20 ZEN16 firmware, this Advanced Driver or my own understanding of the description, but the behavior for the “Input Type for Relay X“ is not what is expected.
The combination of value “10 – on/off report (dry contact switch/sensor)“ and “Report Input Status Only“ for “Input Control SwX“ does give the proper Sw status but still triggers the relay while the description implies it would not trigger.
My workaround was to use “7: Contact Sensor“ instead which does not matter for this application but wanted to let you know about this unexpected behavior.
Did you exclude then include again after adjusting those settings?
Also I have had mixed results with the "Dry Contact" options on various Zooz devices. They seems to insist on sending switch reports on different endpoints instead of just sending some sot of sensor notification on the same endpoint as the relay like every other option does. So it makes the driver on Hubitat a bit more challenging.
ZEN17-800LR Input Reporting Issue Resolved (Firmware 2.30 + Re-Inclusion)
I wanted to follow up in case this helps someone else.
I was having trouble getting the inputs on a Zooz ZEN17-800LR (Hardware v2) to report dry contact changes in Hubitat using Jeff Page's Zooz Universal Relay Advanced driver.
Original symptoms
Hubitat C-8
ZEN17 Hardware v2
Firmware 2.00
Input Types 7 and 10 would not report input changes.
Multiple Configure/Refresh attempts did not resolve the issue.
What I did
Updated the ZEN17 firmware from 2.00 to 2.30 using Hubitat OTA.
Performed a complete Exclude/Include of the device.
Allowed the driver to recreate all child devices.
Tested both S1/C and S2/C using jumper wires.
Results
After the firmware update and fresh inclusion:
Both S1 and S2 report correctly.
Input Type 7 (Contact Sensor) works correctly.
Input Type 10 (Dry Contact Switch/Sensor) also works correctly.
Repeated open/close testing on both inputs is now completely reliable.
The child devices correctly change between Open and Closed every time.
Conclusion
I can't say with certainty whether the fix was:
Firmware 2.30,
the fresh Exclude/Include,
or the combination of both.
However, after performing those steps, the ZEN17 now behaves exactly as expected.
For anyone troubleshooting a ZEN17-800LR that doesn't report input changes, I'd strongly recommend:
updating to the latest firmware,
then performing a complete Exclude/Include before spending too much time chasing wiring or driver issues.
Thanks to Jeff for maintaining this excellent driver. Hopefully this follow-up saves someone else a
few hours of troubleshooting.
A quick scan of this article and search failed find something obvious.
I have a Zen17 and two wireless contact sensors I am trying to have work with the Zooz Garage Door Opener.
Zen17 Firmware is running 2.0
Zen17 driver is Zooz-ZEN17 v1.3.2
Sending a command to the Aggregate Device results in both doors going up. Another command closes them.
Sending a command to the individual Relay device aggregated beneath fails. I see a error string, "groovy.lang.MissingMethodException: No signature of method: user_driver_jtp10181_Zooz_ZEN17_Universal_Relay_Advanced_895.parse() is applicable for argument types: (java.util.ArrayList) values: [[[name:switch, value:on, type:digital, desc:switch is turned on (digital), ...]]]"
Sending from the Zooz Garage Door app for one of the doors fails.
I have uninstalled and reinstalled drivers and the app. No luck. I see other errors in the Relay1 log that show "For input string: "35-1"
There is also a warning right after installation that says, "Zooz ZEN17 Universal Relay Advanced - Relay 1: Unsupported Device USE AT YOUR OWN RISK: [0000, 0000]"
I did do power recycles and configure commands along the way.
It's probably something obvious, but it's not jumping out. Pointers of where to look for guidance or instructions to try would be appreciated. Thanks. -sj