You can but it is probably not working right because of the odd way the device sends reports when you set it to Dry Contact Sensor (as I mentioned above). That would be my guess anyway.
Same for open/close or switch (on/off)
I did try both after changing from dry contact.
Did you exclude and then include it again after changing the input type? That is required for the device to report correctly.
I assume it can work with the built in Hubitat driver, or other people would have said something by now. So you either have it configured wrong or did not do the required exclude/include (do not factory reset).
Tried excluding and including both with open/close and switch (on/off) for input
Then rebuilt rules I deleted before exclusion / inclusion
Same behavior as before the input is Not independent from the relay state.
Tried multiple settings and never got true separation between input and relay activation, both trigger the basic rule created.
If someone could post the settings (all) that make the input trigger separate from a relay activation please post as I am unable to get that function?
I just cannot get it to create the child no matter how I configured it and excluded and then included.
Has firmware version 1.10 on label but sure doesn't do what it's supposed to do.
HELP
I've been wrestling with an odd issue that inexplicably popped up on one of my Z17s, so as part of that troubleshooting, I needed to do an exclude/reinclude...
FWIW, these steps Jeff posted a while ago in a Z16 thread are what finally worked to get my 2 contact-sensor child devices to successfully show up again. Steps are at the end of the linked post
I can try pairing my ZEN58 to Hubitat and see what it does exactly. Its possible the driver is broken or doesnt support it.
@bryonhu do you know if you are running the Zwave JS gateway or legacy ZIP? Zwave JS is only for the C8Pro and you can tell by what the button on the zwave details page says.
Looks like I'm running legacy as the button to Swich to ZwaveJS is showing
Tried again for some time, multiple settings and excluded then included.
A child device is never created and without it I can't get the independent control and input sensing.
Reading the Zen58 pdf a child device should be created?
At a glance it looks like this built in driver is half baked and makes no attempt to even process the open/close event when set that way.
Here are the settings to disconnect the input from the relay, that IS working. But I dont get any events for the open/close sensor.
The scene control does give you button presses, that could maybe be used but a quick "press" would give a pushed event only, and then a longer contact would give a held/released.
This is open/close reports with Zwave JS, I need to switch back to ZIP but I dont think it will help. You can see the driver is skipping them over, it says "skip".
I could see the input in the logs when switched in legacy.zip mode
It seems the issue is not creating a child device to separate the relay from the wired input
EDIT: I really only needed the ability to sense open/close contacts and it works that way for my need.
But it would of been nice to have a fully independent relay for other uses.
Ultimately, the failure to create a child device was what my issue was as well. I can put it in dry contact mode, and it seems to work, but without the child device, there's no way to use the state change.
S.
1 Like
That's the least of its problems, as I stated above, it is ignoring the events totally.
@bertabcd1234 @bcopeland not sure who made the ZEN58 driver but it is not fully functional for the device's capabilities.
Well at least it's not something I am doing wrong...LoL 
I have it setup where the input does not trigger the relay
and the input does trigger on/off state
I can turn on/off the relay and it also sets the state to on or off,
the issue is this on/off state is shared between the input and the relay.
That's where I figured the child device would come into play to separate the two, but I am a Noob and I'm just guessing 
It is doing the main task I bought it for, so once the driver fully matures then I will get my "Bonus" relay
That would probably only happen if its set to On/Off Dry Contact for the input type. With it set to Open/Close when I trigger the switch nothing happens except some skipped messages.
Yes it is set to Dry Contact On/Off mode for input as the ZooZ PDF indicated for my needs.
It is working just fine to turn on and off another device as planned with the Basic Rules that were created.
Just curious if the Zen58 driver will be updated to fix the input and output "child device" issues?
That would be a question for Bryan (or possibly Robert), depending on who made the native driver. Jeff hasn't blended the 57/58 into his community Zooz Relay driver.
Bumping this again because Zooz has still not released their "custom driver" and the Hubitat built-in driver is not creating the necessary child device to be able to use the relay and contact sensor separately. @bcopeland , any input? @agnes.zooz, any word on when your Hubitat driver will be available?