ZEN16 800LR sensor status not updating

kevinb · June 17, 2025, 3:43pm

@ jtp10181 I have the advanced driver installed via HPM and is showing version 1.3.2 for the Zen16 relay switch. I updated Switch 1 Input Type to 10 Dry Contact Switch/Sensor and saved then powered down the switch and back up. A child device was created as expected with the child object "Zooz MultiRelay - Sensor 1S" however the switch doesn't have a status variable available. I am unable to construct a rule/automation based on the trigger. Am I doing something wrong?

Some background: This switch will monitor two dry contact relay float valves on S1 and S2 to monitor water levels. I am using the relay 3 to turn on and off a water solenoid valve connected to R3.

I haven't progressed to installing/activating S2 yet until I get a handle on how this is supposed to work.

EDIT: I have the switch set to Input Control: No, Report Switch and Input Status. Also, there is another anomaly I've noticed and that is that the main driver status always says "1 Pending Changes" when the input switch is set this way. If I go back to value 2 (default) the pending changes goes away.

jtp10181 · June 17, 2025, 3:51pm

What is he firmware version of your ZEN16? It should be visible on the Device Info tab.

kevinb · June 17, 2025, 4:04pm

The firmware is at 3.10. I did just get a rule to fire when I moved one of the float switches, I still have (now 2) "Pending changes" on the status of the parent device, I just can't read the status like I did on my old relay which may not be an issue (I'm using rules to control the relay not the switch itself)

EDIT: sorry for the edit...the rule that fired was just on the trigger "changed", however I can't execute any logic based on whether the switch is open or closed--it just reads "null"

kevinb · June 17, 2025, 4:10pm

I am getting logs that read when the individual switch changes:

info

zooz zen16 relay: switch is turned off (physical)
zooz zen16 relay: switch is turned on (physical)
zooz zen16 relay: switch is turned off (physical)

Just nothing I can compare to in the rule logic

jtp10181 · June 17, 2025, 5:33pm

You have one of the newer models, I think it is 800LR. You have to change the input settings to how you want then exclude and include the device. When you exclude it will delete the device from your devices list and break any rules. Sorry nothing I can do about it, this is due to newer Z-wave spec and Zooz following it to the T.

I will take a look at the settings not updating (with the pending note), I might have something messed up in my configuration.

kevinb · June 17, 2025, 5:43pm

Yeah, I've done that, and that's okay. This is a new switch/setup but I've excluded it and re-added it and it just brings in the same child device without a switch status. I've tried some of the other options as well.

Trying to understand the process better, so forgive me, but here is what I've done.

(Note: I've done a factory reset on the Zen16/V3 a couple of times so I may have really gone too deep, but...)

I added the Zwave device. It automatically assigned your driver to the parent device now.
I change S1 and S2 to be Dry Contact
The relay switch indicator blinks while the driver says "Syncing..."
Then it goes to Synced, blue light stays on.
I turn the relay switch off and back on
I go to new device setup and start Exclusion, press the relay button 3 times. The device shows up in removed message
I then go to Inclusion, and press the zwave button on the relay 3 times
The device is added, new name, etc.
The child devices for S1 and S2 are created

If I go to the child device (type Generic Switch Component) under Current States, there is nothing displayed. Normally for a switch I will see "Switch" and either on or off.

So when I go create a quick rule to test the switch status so I can turn on/off the appropriate relay, there the Switch status is always null (event though I can trigger based on changed), its like the child device doesn't have a property for switch status.

Am I doing something wrong?

jtp10181 · June 17, 2025, 5:52pm

Factory reset will wipe the settings, so don't do that unless thats what you want.

When you exclude then include again, it should sync the settings from your device, so the input settings you selected before should carry over. Do you see that happening?

What hub model do you have? If a Pro are you using Z-wave JS or legacy ZIP?

Turn on TRACE logging on the main parent device, then try triggering one of the sensors, you should get some logs. Post a screenshot of the logs.

kevinb · June 17, 2025, 5:58pm

Yeah, I only did factory to go back to defaults because I've tried so many of the options.

C8 (not pro, so am using legacy). Current 2.4.2.115 as of today (was on 2.4.2.113 for the last week while doing this).

Logs do show a state change when I move the float switch(es), but as I can see there is no "switch" variable for the child sensor device created or maintained when the physical switch (or when I use the On/Off options on the child device).

I will capture a log after I set things back up to where I think they should be and exclude/include the switch.

Question: I don't need to power off / on the device if I am excluding/including??

kevinb · June 17, 2025, 7:03pm

Here is what I am doing..

From Hubitat/Devices/Add Device/Start Z-Wave Inclusion...
Press button on Relay 3 times, blue light flashes for a period, then solid

Edited the default settings...

#2: 10 Dry Contact Switch/Sensor
#3: 10 Dry Contact Switch/Sensor
#4: 10 Dry Contact Switch/Sensor

Save

Syncing...Synced

Three new child devices appear after refreshing the browser, S1, S2, S3 along with the previous Relays

I used the Remove device in Hubitat, started ZWave Exclusion, pressed the ZW button on Zen16 three times, etc. The device is gone,

Hubitat/Devices/Add Device/Start Z-Wave Inclusion...
Press button on Relay 3 times, blue light flashes for a period, then solid

The device is back, with 3 relay and 3 input child devices. Logs from the device creation:

Summary

dev:32532025-06-17 01:25:58.367 PMdebugzooz zen16 relay: (Relay 3) switch is turned off (physical) [NOT CHANGED]
dev:32532025-06-17 01:25:58.337 PMdebugzooz zen16 relay: (Relay 2) switch is turned off (physical) [NOT CHANGED]
dev:32532025-06-17 01:25:58.293 PMdebugzooz zen16 relay: (Relay 1) switch is turned off (physical) [NOT CHANGED]
dev:32532025-06-17 01:25:58.274 PMdebugzooz zen16 relay: Found child devices for endpoints: [1, 2, 3]
dev:32532025-06-17 01:25:58.243 PMdebugzooz zen16 relay: componentRefresh from Zooz ZEN16 MultiRelay Advanced - Sensor 3S (3253-3S)
dev:32532025-06-17 01:25:58.188 PMdebugzooz zen16 relay: Creating 'Sensor 3S' Child Device
dev:32532025-06-17 01:25:58.185 PMdebugzooz zen16 relay: Creating new child device for endPoint 3 (Sensor 3S), did not find existing
dev:32532025-06-17 01:25:58.164 PMdebugzooz zen16 relay: componentRefresh from Zooz ZEN16 MultiRelay Advanced - Sensor 2S (3253-2S)
dev:32532025-06-17 01:25:58.110 PMdebugzooz zen16 relay: Creating 'Sensor 2S' Child Device
dev:32532025-06-17 01:25:58.107 PMdebugzooz zen16 relay: Creating new child device for endPoint 2 (Sensor 2S), did not find existing
dev:32532025-06-17 01:25:58.018 PMdebugzooz zen16 relay: componentRefresh from Zooz ZEN16 MultiRelay Advanced - Sensor 1S (3253-1S)
dev:32532025-06-17 01:25:57.966 PMdebugzooz zen16 relay: Creating 'Sensor 1S' Child Device
dev:32532025-06-17 01:25:57.964 PMdebugzooz zen16 relay: Creating new child device for endPoint 1 (Sensor 1S), did not find existing
dev:32532025-06-17 01:25:57.952 PMdebugzooz zen16 relay: Checking for child devices (3) endpoints...
dev:32532025-06-17 01:25:56.491 PMdebugzooz zen16 relay: fixedInput - Fixed Input Actions (#31) = 0
dev:32532025-06-17 01:25:56.289 PMdebugzooz zen16 relay: durationS3 - Input Trigger Duration Sw3 (#30) = 5
dev:32532025-06-17 01:25:56.080 PMdebugzooz zen16 relay: durationS2 - Input Trigger Duration Sw2 (#29) = 5
dev:32532025-06-17 01:25:55.892 PMdebugzooz zen16 relay: durationS1 - Input Trigger Duration Sw1 (#28) = 5
dev:32532025-06-17 01:25:55.680 PMdebugzooz zen16 relay: dcMotorMode - DC Motor Mode (#24) = 0
dev:32532025-06-17 01:25:55.486 PMdebugzooz zen16 relay: relay3Default - Default Relay State R3 (#23) = 0
dev:32532025-06-17 01:25:55.279 PMdebugzooz zen16 relay: relay2Default - Default Relay State R2 (#22) = 0
dev:32532025-06-17 01:25:55.032 PMdebugzooz zen16 relay: relay1Default - Default Relay State R1 (#21) = 0
dev:32532025-06-17 01:25:54.844 PMdebugzooz zen16 relay: timerOnUnits3 - Auto Turn-On R3: UNITS (#20) = 0
dev:32532025-06-17 01:25:54.637 PMdebugzooz zen16 relay: timerOnTime3 - Auto Turn-On R3: TIME (#11) = 0
dev:32532025-06-17 01:25:54.453 PMdebugzooz zen16 relay: timerOffUnits3 - Auto Turn-Off R3: UNITS (#19) = 0
dev:32532025-06-17 01:25:54.234 PMdebugzooz zen16 relay: timerOffTime3 - Auto Turn-Off R3: TIME (#10) = 0
dev:32532025-06-17 01:25:54.033 PMdebugzooz zen16 relay: timerOnUnits2 - Auto Turn-On R2: UNITS (#18) = 0
dev:32532025-06-17 01:25:53.844 PMdebugzooz zen16 relay: timerOnTime2 - Auto Turn-On R2: TIME (#9) = 0
dev:32532025-06-17 01:25:53.709 PMdebugzooz zen16 relay: timerOffUnits2 - Auto Turn-Off R2: UNITS (#17) = 0
dev:32532025-06-17 01:25:53.432 PMdebugzooz zen16 relay: timerOffTime2 - Auto Turn-Off R2: TIME (#8) = 0
dev:32532025-06-17 01:25:53.222 PMdebugzooz zen16 relay: timerOnUnits1 - Auto Turn-On R1: UNITS (#16) = 0
dev:32532025-06-17 01:25:53.031 PMdebugzooz zen16 relay: timerOnTime1 - Auto Turn-On R1: TIME (#7) = 0
dev:32532025-06-17 01:25:52.827 PMdebugzooz zen16 relay: timerOffUnits1 - Auto Turn-Off R1: UNITS (#15) = 0
dev:32532025-06-17 01:25:52.615 PMdebugzooz zen16 relay: timerOffTime1 - Auto Turn-Off R1: TIME (#6) = 0
dev:32532025-06-17 01:25:52.409 PMdebugzooz zen16 relay: reverseSw3 - Reverse Sensor Values on Sw3 (#27) = 0
dev:32532025-06-17 01:25:52.219 PMdebugzooz zen16 relay: controlSw3 - Input Control Sw3 (#14) = 1
dev:32532025-06-17 01:25:52.014 PMdebugzooz zen16 relay: inputSw3 - Input Type for Sw3 (#4) = 10
dev:32532025-06-17 01:25:51.791 PMdebugzooz zen16 relay: reverseSw2 - Reverse Sensor Values on Sw2 (#26) = 0
dev:32532025-06-17 01:25:51.590 PMdebugzooz zen16 relay: controlSw2 - Input Control Sw2 (#13) = 1
dev:32532025-06-17 01:25:51.385 PMdebugzooz zen16 relay: inputSw2 - Input Type for Sw2 (#3) = 10
dev:32532025-06-17 01:25:51.200 PMdebugzooz zen16 relay: reverseSw1 - Reverse Sensor Values on Sw1 (#25) = 0
dev:32532025-06-17 01:25:50.994 PMdebugzooz zen16 relay: controlSw1 - Input Control Sw1 (#12) = 1
dev:32532025-06-17 01:25:50.799 PMdebugzooz zen16 relay: inputSw1 - Input Type for Sw1 (#2) = 10
dev:32532025-06-17 01:25:50.593 PMdebugzooz zen16 relay: ledIndicator - LED Indicator Control (#5) = 0
dev:32532025-06-17 01:25:50.388 PMdebugzooz zen16 relay: powerFailure - On / Off Status After Power Failure (#1) = 0
dev:32532025-06-17 01:25:50.191 PMdebugzooz zen16 relay: Lifeline Association: [] | MC: [1:0]
dev:32532025-06-17 01:25:49.422 PMdebugzooz zen16 relay: Getting Fixed Input Actions (#31) from device
dev:32532025-06-17 01:25:49.415 PMdebugzooz zen16 relay: Getting Input Trigger Duration Sw3 (#30) from device
dev:32532025-06-17 01:25:49.408 PMdebugzooz zen16 relay: Getting Input Trigger Duration Sw2 (#29) from device
dev:32532025-06-17 01:25:49.400 PMdebugzooz zen16 relay: Getting Input Trigger Duration Sw1 (#28) from device
dev:32532025-06-17 01:25:49.393 PMdebugzooz zen16 relay: Getting DC Motor Mode (#24) from device
dev:32532025-06-17 01:25:49.386 PMdebugzooz zen16 relay: Getting Default Relay State R3 (#23) from device
dev:32532025-06-17 01:25:49.379 PMdebugzooz zen16 relay: Getting Default Relay State R2 (#22) from device
dev:32532025-06-17 01:25:49.372 PMdebugzooz zen16 relay: Getting Default Relay State R1 (#21) from device
dev:32532025-06-17 01:25:49.365 PMdebugzooz zen16 relay: Getting Auto Turn-On R3: UNITS (#20) from device
dev:32532025-06-17 01:25:49.357 PMdebugzooz zen16 relay: Getting Auto Turn-On R3: TIME (#11) from device
dev:32532025-06-17 01:25:49.350 PMdebugzooz zen16 relay: Getting Auto Turn-Off R3: UNITS (#19) from device
dev:32532025-06-17 01:25:49.343 PMdebugzooz zen16 relay: Getting Auto Turn-Off R3: TIME (#10) from device
dev:32532025-06-17 01:25:49.336 PMdebugzooz zen16 relay: Getting Auto Turn-On R2: UNITS (#18) from device
dev:32532025-06-17 01:25:49.329 PMdebugzooz zen16 relay: Getting Auto Turn-On R2: TIME (#9) from device
dev:32532025-06-17 01:25:49.321 PMdebugzooz zen16 relay: Getting Auto Turn-Off R2: UNITS (#17) from device
dev:32532025-06-17 01:25:49.314 PMdebugzooz zen16 relay: Getting Auto Turn-Off R2: TIME (#8) from device
dev:32532025-06-17 01:25:49.307 PMdebugzooz zen16 relay: Getting Auto Turn-On R1: UNITS (#16) from device
dev:32532025-06-17 01:25:49.300 PMdebugzooz zen16 relay: Getting Auto Turn-On R1: TIME (#7) from device
dev:32532025-06-17 01:25:49.293 PMdebugzooz zen16 relay: Getting Auto Turn-Off R1: UNITS (#15) from device
dev:32532025-06-17 01:25:49.285 PMdebugzooz zen16 relay: Getting Auto Turn-Off R1: TIME (#6) from device
dev:32532025-06-17 01:25:49.278 PMdebugzooz zen16 relay: Getting Reverse Sensor Values on Sw3 (#27) from device
dev:32532025-06-17 01:25:49.271 PMdebugzooz zen16 relay: Getting Input Control Sw3 (#14) from device
dev:32532025-06-17 01:25:49.264 PMdebugzooz zen16 relay: Getting Input Type for Sw3 (#4) from device
dev:32532025-06-17 01:25:49.256 PMdebugzooz zen16 relay: Getting Reverse Sensor Values on Sw2 (#26) from device
dev:32532025-06-17 01:25:49.249 PMdebugzooz zen16 relay: Getting Input Control Sw2 (#13) from device
dev:32532025-06-17 01:25:49.242 PMdebugzooz zen16 relay: Getting Input Type for Sw2 (#3) from device
dev:32532025-06-17 01:25:49.235 PMdebugzooz zen16 relay: Getting Reverse Sensor Values on Sw1 (#25) from device
dev:32532025-06-17 01:25:49.228 PMdebugzooz zen16 relay: Getting Input Control Sw1 (#12) from device
dev:32532025-06-17 01:25:49.221 PMdebugzooz zen16 relay: Getting Input Type for Sw1 (#2) from device
dev:32532025-06-17 01:25:49.214 PMdebugzooz zen16 relay: Getting LED Indicator Control (#5) from device
dev:32532025-06-17 01:25:49.207 PMdebugzooz zen16 relay: Getting On / Off Status After Power Failure (#1) from device
dev:32532025-06-17 01:25:49.192 PMdebugzooz zen16 relay: Setting multi-channel lifeline association...
dev:32532025-06-17 01:25:49.186 PMdebugzooz zen16 relay: executeConfigureCmds...
dev:32532025-06-17 01:25:48.252 PMdebugzooz zen16 relay: (Relay 3) switch is turned off (physical) [NOT CHANGED]
dev:32532025-06-17 01:25:47.646 PMdebugzooz zen16 relay: (Relay 2) switch is turned off (physical) [NOT CHANGED]
dev:32532025-06-17 01:25:46.881 PMdebugzooz zen16 relay: (Relay 1) switch is turned off (physical) [NOT CHANGED]
dev:32532025-06-17 01:25:46.753 PMinfozooz zen16 relay: switch is turned off (physical)
dev:32532025-06-17 01:25:46.737 PMdebugzooz zen16 relay: Set Device Info - Model: ZEN16 | Firmware: 3.10
dev:32532025-06-17 01:25:46.731 PMdebugzooz zen16 relay: Received Version Report - Firmware: 3.10
dev:32532025-06-17 01:25:46.633 PMdebugzooz zen16 relay: fingerprint mfr:"027A", prod:"A000", deviceId:"A00A", inClusters:"0x5E,0x9F,0x55,0x6C", secureInClusters:"0x25,0x30,0x8E,0x59,0x85,0x86,0x73,0x60,0x72,0x87,0x7A,0x5A,0x70"
dev:32532025-06-17 01:25:45.161 PMdebugzooz zen16 relay: Set Device Info - Model: ZEN16 | Firmware: 0.0
dev:32532025-06-17 01:25:44.935 PMdebugZooz ZEN16 MultiRelay Advanced: Unhandled zwaveEvent: ZipNamingNameReport(name: zooz zen16 relay) (ep 0) [hubitat.zwave.commands.zipnamingv1.ZipNamingNameReport]
dev:32532025-06-17 01:25:44.833 PMdebugzooz zen16 relay: componentRefresh from Zooz ZEN16 MultiRelay Advanced - Relay 3 (3253-3)
dev:32532025-06-17 01:25:44.774 PMdebugZooz ZEN16 MultiRelay Advanced: Creating 'Relay 3' Child Device
dev:32532025-06-17 01:25:44.771 PMdebugZooz ZEN16 MultiRelay Advanced: Creating new child device for endPoint 3, did not find existing
dev:32532025-06-17 01:25:44.681 PMdebugzooz zen16 relay: componentRefresh from Zooz ZEN16 MultiRelay Advanced - Relay 2 (3253-2)
dev:32532025-06-17 01:25:44.619 PMdebugZooz ZEN16 MultiRelay Advanced: Creating 'Relay 2' Child Device
dev:32532025-06-17 01:25:44.610 PMdebugZooz ZEN16 MultiRelay Advanced: Creating new child device for endPoint 2, did not find existing
dev:32532025-06-17 01:25:44.543 PMdebugzooz zen16 relay: componentRefresh from Zooz ZEN16 MultiRelay Advanced - Relay 1 (3253-1)
dev:32532025-06-17 01:25:44.390 PMdebugZooz ZEN16 MultiRelay Advanced: Creating 'Relay 1' Child Device
dev:32532025-06-17 01:25:44.387 PMdebugZooz ZEN16 MultiRelay Advanced: Creating new child device for endPoint 1, did not find existing
dev:32532025-06-17 01:25:44.362 PMdebugZooz ZEN16 MultiRelay Advanced: Checking for child devices (3) endpoints...
dev:32532025-06-17 01:25:44.359 PMdebugZooz ZEN16 MultiRelay Advanced: Endpoints (3) Detected and Enabled
dev:32532025-06-17 01:25:44.136 PMdebugZooz ZEN16 MultiRelay Advanced: Probing for Multiple End Points
dev:32532025-06-17 01:25:44.103 PMinfoZooz ZEN16 MultiRelay Advanced: Logging Level is: Debug (3) for 30 Minutes
dev:32532025-06-17 01:25:43.915 PMwarnZooz ZEN16 MultiRelay Advanced: Clearing state variables and data...
dev:32532025-06-17 01:25:43.912 PMwarnZooz ZEN16 MultiRelay Advanced: First Configure detected - retrieve settings from device
dev:32532025-06-17 01:25:43.910 PMwarnZooz ZEN16 MultiRelay Advanced: configure...
dev:32532025-06-17 01:25:43.901 PMwarnZooz ZEN16 MultiRelay Advanced: installed...

If I try to capture the state of the input sensor, the logs will show changes to the Relay, but not the Switch. The logs will show that the relay is on/off:

Summary

dev:32532025-06-17 01:42:59.004 PMdebugzooz zen16 relay: controlSw3 - Input Control Sw3 (#14) = 0
dev:32532025-06-17 01:42:58.538 PMdebugzooz zen16 relay: controlSw2 - Input Control Sw2 (#13) = 0
dev:32532025-06-17 01:42:58.103 PMdebugzooz zen16 relay: controlSw1 - Input Control Sw1 (#12) = 0
dev:32532025-06-17 01:42:57.532 PMdebugzooz zen16 relay: Changing controlSw3 - Input Control Sw3 (#14) from 1 to 0
dev:32532025-06-17 01:42:57.522 PMdebugzooz zen16 relay: Changing controlSw2 - Input Control Sw2 (#13) from 1 to 0
dev:32532025-06-17 01:42:57.513 PMdebugzooz zen16 relay: Changing controlSw1 - Input Control Sw1 (#12) from 1 to 0
dev:32532025-06-17 01:42:57.503 PMdebugzooz zen16 relay: executeConfigureCmds...
dev:32532025-06-17 01:42:56.510 PMdebugzooz zen16 relay: Found child devices for endpoints: [1, 1S, 2, 2S, 3, 3S]
dev:32532025-06-17 01:42:56.483 PMdebugzooz zen16 relay: Checking for child devices (3) endpoints...
dev:32532025-06-17 01:42:55.384 PMdebugzooz zen16 relay: Sensor endPoint 3S found, selected Input Type - 10: Dry Contact Switch/Sensor
dev:32532025-06-17 01:42:55.378 PMdebugzooz zen16 relay: Sensor endPoint 2S found, selected Input Type - 10: Dry Contact Switch/Sensor
dev:32532025-06-17 01:42:55.373 PMdebugzooz zen16 relay: Sensor endPoint 1S found, selected Input Type - 10: Dry Contact Switch/Sensor
dev:32532025-06-17 01:42:55.366 PMinfozooz zen16 relay: Logging Level is: Debug (3) for 30 Minutes
dev:32532025-06-17 01:42:55.316 PMdebugzooz zen16 relay: updated...

So I edit the parent relay and change parameters #12, 13, and 14 to "No: Report Input Status Only" (I can't use the 3rd option or we get stuck in Pending changes)

The device interface shows "Syncing/Synced".

The logs show that the updates were made...

dev:32532025-06-17 01:47:48.698 PMinfozooz zen16 relay: switch is turned off (digital)
dev:32532025-06-17 01:47:48.484 PMdebugzooz zen16 relay: componentOff from Zooz ZEN16 MultiRelay Advanced - Sensor 1S (3253-1S)
dev:32532025-06-17 01:46:07.977 PMinfozooz zen16 relay: switch is turned on (digital)

To me, the child input sensor device doesn't have a property for switch status, or if it does, its not being set after the child device is created, which is why I thought I am doing something wrong. My logic is that I don't want the input condition to change the relay, I want a rule to do that because I have two sensors that will determine what action to take with the relays.

I'm attaching the log as a text file from when I removed and re-included the device in case the post doesn't format well.

Thanks for your help!

zen16-logs.txt

jtp10181 · June 17, 2025, 7:10pm

You have beta hub firmware, so that could be a contributing factor.

I would power cycle it after excluding for good measure.

The Child device DOES have a switch attribute but its not populating for some reason. They don't show until they have an initial value. I need to see the logs to determine anything else.

Can you just post a simple screenshot of the logs next time?

Also, BTW, you will want your settings like this:

The bottom option for the input control was removed on the 800LR model but I missed hiding that in the driver so if you select that it doesn't save and will be stuck pending.

jtp10181 · June 17, 2025, 7:21pm

All I need is for you do exactly as I said above. This is the only logs I need to see, and I don't see any trace logging yet.

Also, you asked about power cycling the device, so did you power cycle it between exclusion and inclusion?

This wont do anything for the sensor, Its only there because it is a built in component driver and I don't want to make a custom one. You have to trigger the sensor input physically on the device.

kevinb · June 17, 2025, 7:58pm

Sorry, I didn't know there was a specific Trace level debug, I have attached the log here.

Yes I had power cycled the Zen16 after excluding, then again after including.

Here I enabled trace and then went to the S1 switch itself to turn it on and back off.

I have it set up as you note, No/Report input status only.

jtp10181 · June 17, 2025, 9:10pm

I did not really want it filtered to only trace, I like to see all level including trace. But anyway, I can see the device is not sending the correct reports.

I only have a v2 device to test with, and mine is set to option 7 contact sensor.

What we want to see is a NotificationReport message like this:

There was a bug in the ZEN17 where for ONLY the option 10 (the one you are using) it did not send the correct messages over. I did account for it in my driver but it looks like maybe the ZEN16 is not sending ANY messages over. Anyway.... try switching it to option 7: Contact Sensor. Then of course you have to exclude and include again.

kevinb · June 17, 2025, 9:19pm

Geeze dude, I'm sorry. The reason the debug got filtered is because I didn't know there was a Trace setting in the device and I was looking to see if that was what you were talking about :-/. Once I found that option in the view debug screen, I then found trace in the device but stupid me just left the filter on...didn't think.

It doesn't matter to me which option--I really thought I was doing something wrong, or my use of the relay switch was wrong. I have a High water float valve, and a low. What I wanted to do is if the Low was triggered, to shut off the pump so it doesn't burn out. And if the High water sensor was triggered, to turn on the water valve.

I only have one relay (R3) to control--so playing around I started to just use the default action to activate the relay seeing that S1 activates R1, S2=>R2 ... and then just write my rules to check the status of the relay R1/R2 instead of S1/S2. There isn't anything connected to R1 and R2.

But Contact Sensor will be fine too and that will leave me growth to add other relays in the future.

Again, thanks. And thanks for being patient with me...you would think that 40+ years in the tech field would make me a bit sharper, but here it's a whole new world for me.

jtp10181 · June 17, 2025, 9:46pm

I think you are doing it correctly, let me know if switching to contact sensor gets the status updates correctly.

kevinb · June 17, 2025, 11:06pm

I couldn't get it. I have the Zen16 removed and reset to try again. I first added the device from the Hubitat app and now I have phantom disconnected children left over from previous pairings so I am going to leave the relay offline and let my zwave network try and heal itself. (What is happening to me is that when I remove the device, I power it off and when I power it back on Hubitat automatically adds it back in). Not sure if that's a recovery thing they intended or an issue with having it added to the SmartStart manifest.

I'll go back and just set things up to read the relay switch status for triggers. But if you are willing, I am willing to help test things further but feel like I've taking up a lot of your time.

jtp10181 · June 17, 2025, 11:46pm

Its not an issue, it is SmartStart working as intended.
You have to remove or disable in SS for that to not happen. Or you could have just left it to re-pair by itself (the power cycle may not be needed).

You will need to remove all the ghost nodes, see section 3: How To Remove Ghosts using hub tools or a UZB Stick

I am pretty sure if you just switch the setting to contact sensor and pair again it will work as intended. Or are you saying you already tried that? Your reply above was not very clear?

Couldn't get what?

kevinb · June 18, 2025, 2:01pm

No, it didn't work, I got the device added back in with the option as a contact switch. The child devices were created and with a state of "Closed" but changes to the input switch weren't reflected in the device.

jtp10181 · June 18, 2025, 2:38pm

I would open a case with Zooz or post on their community. I don't have a v3 device to confirm how it works exactly. I thought it should be the same as the V2 I have here. They use my drivers for testing often, so they can hook a V3 up to Hubitat with my driver and see if they can figure it out.

The behavior you are getting is what the ZEN17 800LR does if its NOT excluded and paired again, but since you are doing that, not sure what's going on.

kevinb · June 18, 2025, 6:35pm

Opened a case with Zooz. I did find some other posts about other relays not having their inputs updated. This could be something going on in Hubitat. And of course I have beta running so I'm not going to question it for now. I know I have several child sensors showing up in my zwave devices that are not there--this happens every time I exclude/include the device. And they are LR so the ghost protocol (wasn't that a movie?) may not work--but ordering a zwave stick just in case...I know have 6 of them