ZEN78 Setup

This first setup is to replace my Aeotec heavy duty switch that I use for the well pump. LR is one rationale, more features, plus I've never fully understood the Aeotec docs.

The well pump switch and legacy WaterCop valve get exercised daily since I turn the water off when I leave the house. I also have a standby generator.

If not addressed, mfr's defaults.

Auto Turn On After Overload: Set to 5 seconds. It's been my experience that sometimes a spurious current signal can shut down a device. The pump is on a breaker.

LED Indicator: I like it to glow when it's on.

On/Off Status After Power Failure: Remember Status, but with the following:
Turn On Delay After Power Outage: Wait 2 minutes to let the generator stabilize, if the pump was running at the time of the outage

Temperature Reporting Threshold: I'm thinking 1°F should be good. The well pump only runs periodically, so there shouldn't be that much heating going on in the box. I think max is 100 anyway. This will go along with the nearby Titan's temp readings, although its sensor is separate from the controller enclosure.

Input Type: I don't think I'll be adding a switch at this time, use the built in button. Again, it's on a breaker.

Electric Reporting: I'm undecided here. Perhaps monitor kWh to detect perhaps a failed foot valve (I'm on shaky ground here). Create baseline first. Pump has been in hole since house built 23 years ago. Maybe watts as well. The rest, probably disable.

Alerts: There are several alerts available. I've brought up the issue of using device-generated alerts in the past, to no avail.

Next up is coordination of the legacy WaterCop, controlled reliably by an old ZEN16 multi relay. My understanding is the hub has issues vis a vis ZWJS with the current ZEN16 LR model. I'll have to revisit this.

ref:
https://www.support.getzooz.com/kb/article/2189-zen78-high-power-relay-advanced-settings/

Seems to be a discrepancy in heat alert level between what the device driver picked up and the Zooz doc. Not that alerts will likely be a factor:

image

Got it swapped out.
It was turning on stuff via rule but not off!
Turned out rebooting with database rebuild got it back on track!
Whew!
First for me.
edit: Now I have to figure out how to exclude/remove/factory reset, whatever, the old Aeotec switch. I should have done it before I removed it from 240. The ZEN78 can be powered by 120. Not so sure about the Aeotec. Ugh.
edit2: Success

1 Like

After a lot of sturm und drang on the universal z-wave switch driver page, I figured out what works for me.

  • I used that driver to set parameters
  • When re-energized, the relay seems to send an 'off' to the ZEN16 that controls the WaterCop shutoff valve
  • I have the pump and shutoff valve mirrored
  • The delay on after power restoration didn't get rid of the 'off', so I set parameters 2 to 0, and 16 to 0, both disabled
  • Instead I used auto-on, parameter 14, set to 1 (minute)
  • Now, even upon a partial restoration, of 120v, which is for sure given my propensity to be cheap with the propane and run the house on a little Honda, the water cop valve will close-hopefully I will not have turned on any water upstairs and empty the pipes, but it is what it is
  • The well pump will turn on 1 minute (for now) after restoration of 240v, and at that time open the shutoff valve
  • After changing parameters, I switched to the system driver; 'Configure' did not change the parameter settings
  • I'll mess around with the reporting settings in future (tomorrow?)
  • Then gather kWh baseline data for a rule to tell me if the check valve failed, perhaps high watts as well

Good night.

edit: Well that didn't work. Back to the drawing board...tomorrow.

Was a coordination issue with the ZEN17.
Made that 'all relays turn on after power restoration.
Restoration delay now works as it should on the ZEN78.
Not exactly what I wanted, but I don't think it really matters.
We'll see in the next outage.

Oh, and that Basic Z-Wave driver didn't work, totally, for changing parameters.
Something to keep in mind.

And the parameter for disabling reports doesn't seem to work. Zero gives a reading a second in most cases. I'll have to fool around with that. Right now, they're all reporting at the five minute default.

Device reports multiple "Ons" and "Offs".
Doing a load right now, but I'm pretty sure I've seen the multiple "Offs" as well.

edit: I wonder what could cause this? 8 reports in less than 3 seconds.

Is this on Zwave JS or ZIP?

It is probably just the device sending multiple reports for whatever reason. The driver is possibly issuing a "Get" command to be sure it gets the current state, which may add an extra one (or more depending on how the device reports it).

This is why on my drivers I suppress duplicate logs like this to debug logging, although usually it is just 2, not 8.

Debug logs might shed a little more light on what is going on, if the actual reports are slightly different.

ZWJS

I recall mention of similar issues in the past.
Events are fine.
It doesn't seem to affect any rules, far as I can tell, but I guess that'd be a possibility.
edit: Not a debug log, but an nice picture. :slight_smile:

debug log:

This one is different than the others:

Probably just bugs in Zwave JS

2 Likes

To reiterate a previous observation:

Disabling reporting frequency ("0" for the respective parameters) for watts, volts, kwh, amps, does not work. It spits updates out every second or so. I had to set it to 24 hours to basically suppress reports.
@agnes.zooz , can this be fixed?

You would be better off opening a support ticket with them or posting on their forums. They tend to be a little slow to respond on here.

1 Like

Thanks. Didn't realize they had a forum.