Looking for help / suggestions on a Zooz Z-Wave Plus Gas/Water Valve Control ZAC03 I recently purchased. I can work it remotely as a switch (on - off) but when integrating it to the smart home monitor with a leak detector, for some reason it works backwards. Meaning off is on and on is off. I hit the “open” button and it closes and reverses the other way. I have tried throwing the clutch and free spinning it thinking it would simply trigger a move and it would then be in the correct position but when reengaging the clutch it automatically orients it self back. I looked at unscrewing the arm itself and moving it over but it can only be placed one direction. It will only work with the leak detector if it is in the off position. Once a leak is detected it turns the valve on. One thing I had to do was go to the IDE page and choose the Fortrezz Water Valve as Zooz was not yet an option. I figured they would work the same way to no avail. Only a few other water valve options exist in the IDE page like the Zigbee valve but it seems to lock my whole system up. Simulated water valve does nothing as I believe it isnt meant to preform actions just help link other commands. Any ideas?
@cottonbj, so right now the valve is seen just as a switch? When you selected the Fortrezz device handler, I’m assuming it behaved the same, right?
Do you know how to create your own device handler? If so, try this one and let me know if it works for you:
If you need help creating a device handler, check this out to create a device type/handler:
EDIT: I did find “Zwave Water Valve” in ST’s public github repo. I have no idea why the IDE doesn’t make it available. Mine is exactly the same for the most part except I added “switch” capability and changed the name a bit.
Wow, it worked and everything is as it should be. The valve is turning the correct direction and works with the water sensor to shut shut down at the first sign of a leak. I cant thank you enough. I saw your reply but wanted to wait until the weekend to work with it as it usually is a pain to work through. You made it simple and gave links and though im learning as I go, was able to make sense of it all and had it working in 15 mts the first time. My home’s future nonwater damage thanks you immensely. One question, what is the difference between the smartapp function and device handlers?
Hi @cottonbj, glad to hear that things are working!
In a nutshell, device handler code is used to control and manage a device from within SmartThings, and to receive physical actions performed on a device to update SmartThings on it’s current state. So when you control your valve from the phone app, or physically, the device handler manages all the communications/data/changes between ST and device.
SmartApp code enable you to perform actions on a device, or a group of devices, based on rules and conditions you define. In the case of the water valve, SHM turns off the valve and turns on lights. Rule Machine is also a very popular rules engine used within the community when more complex if/then/else conditions need to be met.
Another great SmartApp example, Keenect, is one for managing and controlling temperature in your home with smartvents and thermostats.
Other SmartApps, like SmartTiles, provides a method for using spare phones and tablets as wall control panels with your ST devices. It’s a lightweight client with a lot of flexibility.
Thanks @johnconstantelo Just installed the water valve and switched the type to your custom device handler. Works great
I am not a programmer, but I can usually figure things out. I also have the ZooZ valve control ZAC03 and I want it to automatically close when water is detected. I have tried to create a new smart app repeatedly with no success. I followed your instructions and I get the following message when I create:
No signature of method: script14578073479911318124604.metadata() is applicable for argument types: (script14578073479911318124604$_run_closure1) values: [script14578073479911318124604$_run_closure1@2e55c3c3] Possible solutions: getMetadata(), getState(), setState(java.lang.Object), metaClass(groovy.lang.Closure)
Hi @dstratton, it looks like you tried to create a SmartApp, not a device handler.
John, yes, I’m not home right now. I will look to see where to create a device handler and let you know. Thank you!
Just an update, your advice worked great! Instead of spending $450 for the fortress water valve, I spent $60 on the Zooz and it works great! Just a note, you have to clear the alert on your Dashboard before it will close again with the leak detection.
Thank you again!
John, since you mentioned it, my Z-wave water valve, which works fine with moisture sensors is not available in SmartTiles for some reason. I tried it with the original device handler and the one listed in this thread and in neither case does it show up. If I’m doing something wrong, I’d appreciate you letting me know what to try. My other devices show up fine.
That’s odd! I don’t use SmartTiles (yet), so I’ll have to phone a friend for some expert help. @tgauchat?
SmartTiles doesn’t support Capability Valve directly at this time, @hdinwiddie…
Either add and link a Virtual Switch to your environment, or modify the Device Type Handler to claim Capability Switch and alias the Commands on/off appropriately.
@625alex and I have a lot of new Capabilities to support in SmartTiles V6!
Thanks @tgauchat. The custom device handler referenced in post 6 does have that.
@hdinwiddie, did you try this version?:
Apparently not although I thought I did. It worked!!! Thanks so much as it was the only device I have that wouldn’t show in SmartTiles. I appreciate it!!!
Just a note. It took me 30 minutes to get this to pair with SmartThings. Eventually had to bring it within 2 ft of the hub and physically reboot the hub to get it to see this. Pressing the button 3 times didn’t work. Had to reset it to work.
But the good news is it did show up a water valves and works great.
Bad news it didn’t fit in my 1 inch valve and I will need a custom modification for it to work and fit well.
It’s not really meant for a 1" valve so you might want to test it weekly just in case the water shutoff valve is sticky and burn out your motor. I test my 3/4" valve BI-weekly and find it’s a little sticky the first cycle. That’s also on a new shutoff valve as well.