getting lots of errors in logs
dev:2622023-03-30 12:45:12.783 PMdebugrefresh()
dev:2622023-03-30 12:44:08.303 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_jtp10181_Zooz_ZEN17_Companion_Driver_651.componentOn() is applicable for argument types: (com.hubitat.app.DeviceWrapper) values: [Zooz Zen17 Universal Relay - Relay 1] (method componentOn)
dev:2622023-03-30 12:44:08.119 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_jtp10181_Zooz_ZEN17_Companion_Driver_651.componentOn() is applicable for argument types: (com.hubitat.app.DeviceWrapper) values: [Zooz Zen17 Universal Relay - Relay 1] (method componentOn)
dev:2622023-03-30 12:44:07.927 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_jtp10181_Zooz_ZEN17_Companion_Driver_651.componentOn() is applicable for argument types: (com.hubitat.app.DeviceWrapper) values: [Zooz Zen17 Universal Relay - Relay 1] (method componentOn)
dev:2622023-03-30 12:44:07.584 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_jtp10181_Zooz_ZEN17_Companion_Driver_651.componentOn() is applicable for argument types: (com.hubitat.app.DeviceWrapper) values: [Zooz Zen17 Universal Relay - Relay 1] (method componentOn)
dev:2622023-03-30 12:44:07.420 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_jtp10181_Zooz_ZEN17_Companion_Driver_651.componentOn() is applicable for argument types: (com.hubitat.app.DeviceWrapper) values: [Zooz Zen17 Universal Relay - Relay 1] (method componentOn)
dev:2622023-03-30 12:44:06.486 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_jtp10181_Zooz_ZEN17_Companion_Driver_651.componentOn() is applicable for argument types: (com.hubitat.app.DeviceWrapper) values: [Zooz Zen17 Universal Relay - Relay 1] (method componentOn)
dev:2622023-03-30 12:44:05.096 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_jtp10181_Zooz_ZEN17_Companion_Driver_651.componentOff() is applicable for argument types: (com.hubitat.app.DeviceWrapper) values: [Zooz Zen17 Universal Relay - Relay 1] (method componentOff)
dev:2622023-03-30 12:43:45.294 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_jtp10181_Zooz_ZEN17_Companion_Driver_651.componentRefresh() is applicable for argument types: (com.hubitat.app.DeviceWrapper) values: [Zooz Zen17 Universal Relay - Relay 1] (method componentRefresh)
dev:2622023-03-30 12:43:43.984 PMerrororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_jtp10181_Zooz_ZEN17_Companion_Driver_651.componentOn() is applicable for argument types: (com.hubitat.app.DeviceWrapper) values: [Zooz Zen17 Universal Relay - Relay 1] (method componentOn)
Yeah I will stick to my good old trusty float switch to keep my basement from flooding. I added some monitoring around it but the sump will work on its own as long as it has power.
Not going to stop me from helping someone get a ZEN17 to do what they want though.
The driver is only for setting the parameters.
After you are done you have to switch back to the normal one to control it. There are instructions on the post about the driver.
This is for backup. So if primary fails then I have float switch that would trigger zen17 to use back up. I appreciate help but I think i need to get more familiar with hubitat, fairly new. I used smartthings for years and was little more declarative in settings.
I was hoping to avoid messing with drivers/code. and use an expression or rule. When float switch triggers S1. Then switch relay to ON for 7 sec then off.
You can do it with a rule, but I thought you were trying to set the auto-off on the device itself? In this case I would say it is better to set on the device so you dont have to rely on the hub and risk it getting stuck in the on position for a long time.
You dont have to mess with any code, just install that driver, follow the instructions, change the setting and switch back to the main driver. Then when you flip it on, it turns back off by itself, no rules needed.
If you don't want to do that, just say so and I am sure the others can help you make a rule instead. I just jumped in to point out the companion driver I created.
I have a ZEN17 and I've seen it lock up a few times where even the physical trigger doesn't work. Your backup float switch should bypass the ZEN17 completely.
Got it. Yes you are right, I would prefer that way since if power fails my hub will be down. Ok I'm going to re read your post and reset zen17 and start from scratch.
How can that work though? w/out zen17 or some relay how can i trigger power to flow from battery to pump?
Since zen17 has dual switches I"m wondering If I can connect to both so if R1 fails R2 can turn on?
The float switch is a switch. As long as it can handle the amps your putting through it, there doesn't need to be relay between it and the pump. Wire it parallel to the ZEN17.
I follow but float switch wouldn't run for like 8 sec right? it run few sec before water level drops and turns off?
It's a back up. Just there to keep your basement from flooding, right? 
1 Like
Yep makes sense. I will implement this as back up to backup. thanks for tip! I will mod it with its own float switch and have it higher in the PIT.
OK I added parameters. Changed back to stock. Errors gone in logs but delay is not happening. Turns off instantly still
Thats not instant, thats 4 seconds.
Did you save at the bottom of the settings after you changed it, and then wait for it to sync?
There should be a "configVals" entry in the data at the bottom of the device page, please post the contents of that.
It clicks off instantly once i turn off switch. I held switch on for good sec.
i reloaded advance confirmed changes, saved, said syncstatus: Synced. Changed driver back to stock and tested again.
Can you show me the rule that turns on the ZEN17? I have a theory that I was thinking about this all wrong for your setup. My assumption was that the logic/rule worked like this:
Contact sensor reports closed to Hub, triggering Hub to turn on ZEN17, ZEN17 programmed to auto-off after 8 seconds. I'm thinking that's not really what's happening.
Is your Contact sensor wired directly to your ZEN17 as an input trigger?
I am guessing it is something with the input selection for Relay 1, which is param 2
Do you have something connected to the inputs as well? You have it configured for a leak sensor and the input is attached to the load (param 10), so the input status is probably overriding your request.
For me I have everything at the defaults besides the auto-off and it works fine.
Right now I'm I just have it on my work desk with small load going to vu meter and trying to get config down before I go into basement and connect everything. So I'm just using paper clip to be my float switch and trigger the switch. I disabled the rule i started working on after you point about power failure so i'm triggering it manually.
but here is the rule
