UPDATE: In seeking out support from Zooz on this issue, I found the following information on the Zooz ZEN58 support page for Hubitat:
"The ZEN58 Low Voltage XS Relay has been officially integrated with Hubitat as of Hubitat version 2.4.2.134. Once you include your device, you will have access to the available settings.
*(NOTE - the built-in Hubitat driver does not support the creation of a child device to monitor the input when using parameter 5 at this time. Hubitat will address this in the next platform update. )"
I'm currently running 2.4.4.156 Hubitat software, so either the issue was not addressed in the "next platform update" or the information about how to achieve a child device is still a well-kept secret.
I purchased two ZEN58 Relay Modules but so far, I've only been able to pair one of them so it shows with a child device for the sense lines.
I've tried the recommended pair/unpair/repair sequence outlined in the Zooz advanced setup but not with any happy results. I honestly don't know what I may have done to get the first one working. Seems I just kept trying different things, gave up, and then later when I looked at my device list, it showed the child.
Unfortunately, the second unit hasn't responded to my various configuration attempts, including Hub reboots.
Has anyone had success reliably pairing a ZEN58 so that the child device appears in the device list? If so, what steps did you follow to make this happen?
Thank you.
Looks like they should be automatically created when any switch events come in for any endpoints that are not the root node, assuming you are using the built-in driver, the exact type (driver) of which will depend on some other configuration parameter values you've set. This may happen during regular use of the device, or a "Refresh" might help if you just set it up.
If that doesn't help, enabling debug logging and sharing that output here (particularly when any events come in, or a "Refresh" if you can't make something happen manually) as well as the values of all your configuration parameters (the "Preferences" tab) may help.
And, of course, make sure you have the list of child devices expanded if there's an arrow next to the parent device on the "Devices" page and it isn't if that's where you're looking, but I'm guessing that's not it. 
1 Like
Thank you for the reply.
On the working device it shows one parent and one child. The parent provides relay control, the child reports the status of the sense line. Works fine.
Here are the Preferences:
Driver=ZoozZen58LV XS Relay
Relay Control=Disable local control (Parameter 9)
Relay Type=Normally Open (Parameter 10)
Input Trigger=Disabled (Parameter 11)
Input Type=Motion Alert (Parameter 5)
Scene Control and Multi-Tap Scene Control=Both Disabled (Parameters ?? & 12)
Auto-On Timer=Disabled (Parameter 8)
The second (no child) device is set to the same preferences but fails to show a child device.
I've performed the requisite set parameters/exclude/re-include serveral times. All to no avail.
Refresh seems to make no difference.
Could you please expand on this? I'm not quite following.
Again, thank you for the help.
I don't have one of these devices (I'm just looking at the driver), but presumably it must act as a multi-channel device with different "endpoints" for the different relays or inputs, and that must be where data for any of these comes in on. This was more for noting in case you have any way to force an "event" (Z-Wave report) from something you have attached, like activating a sensor or something -- in which case debug logging should reveal what the driver sees and might help figure out more if that alone doesn't do the trick.
If they're both configured the same way, I don't see any reason they should behave differently (maybe different firmware? And are both really responsive on the Z-Wave network, e.g., you didn't include the device and then move it somewhere out of range?). I don't think exclusion and re-inclusion is likely to help and if anything might erase any configuration parameters you have on the device and put you back a step (not sure if Zoom products do this, but some do).
1 Like
For the record, I have the 57, and I struggled with this as well. Not sure I ever succeeded now that I think on it....
S.
1 Like
After struggling with this for a while, I discovered that when you initially add the ZEN58 with parameter 5 set to something higher than 5, it appear as only one device. If you close the switch contacts (cross the leads), you will see a button press appear on the root device. However, sometime in the next 30 minutes, the child device magically appears. Other similar Zooz products, like the ZEN17 and ZEN52 do not exhibit this type of behavior; they are created with child devices from the start.
Thank you.
Is parameter 5 the only parameter you change from the defaults before doing the cross leads / wait 30-minutes routine?
Do the child devices show up without having to execute an exclude / re-include cycle as Zooz suggests?
I assume you are using the standard "Zooz Zen58 LV XS Relay" driver?
Which driver do you use for the ZEN52? My experience is that I need to use the community driver (Zooz ZEN17 Universal Relay Advanced) in order to achieve child devices with the ZEN 51 & 52.
Thanks again.
