I ended up hiring a plumber. He propressed a new valve down the line. I was impressed and annoyed that it cost as much as it it did since it wasn't sweated on. But wow was it quick, clean and interesting to see how efficiently it's executed.
This actuator is awesome. Even the plumber stuck around to see how well it worked. He couldn't help but ask why I needed 2 ball valves next to each other. However, he was throughly impressed with it and the temp sensor. Was amazed at how the lights and Alexa started notifying.
Then he looked at me like Gacy and threw the bill at me like I was trying to escape my wallets fate.
Thanks for the driver, sir. Much appreciated. Wish I came to HE sooner. Love this platform and community.
Since this driver never left beta state I guess this is the final round of beta before going to final 1.0.0 status! @hydro311
This is totally overhauled and updated to my current code base / library code. I added in a bunch of the new stuff as well.
This is posted to a separate branch on gitHub, I will add to HPM as soon as I feel safe this wont cause anyone a catastrophe. I do not have a battery pack to test and also have not tested the various alerts since I revamped it so I possibly broke something (but probably not).
Please turn on DEBUG - Indefinitely to capture all event logging.
This is what needs to be tested:
heat and freeze alarms
leak alerts
power source changes
battery notifications (I assume % ??)
changing temp to C I think will have issues, need to fix/test
Hey quick question, is there a way to pull lastCheckInDate into an RM rule? I'd like a peace of mind to make sure it doesn't disconnect or is unreachable.
I just realized your driver has built in tester for the valve functionality and enabled that.
All my drivers are setup so the lastActivity date/time that app uses should ONLY get updated if the device sends a report to the hub, and it will update if you send a refresh to the device. Due to this they work great with that app. Have not implemented the "healthStatus" attribute yet but may consider adding that eventually.
I think the self-test feature is enabled by default so yours was possibly doing that all along, unless you had turns the setting off by mistake. Its good because it keeps the valve loosened up as well, so when you really need it to work it does not get stuck.
Hahaha, I guess it was amd glad it's a default option. It wasn't selected from the drop-down, but it did show that enabled is default. Does it log if it fails or alert or do I need to figure out how to monitor that?
Good question... I have some docs somewhere Zooz gave me to help with the driver, I will have dig through that later and see if it says anything about it. Otherwise we might have to ask them.
HI Jeff -- I loaded the new version on both my Titans. I only have the battery pack on one of them, but I did a quick power pull on it, and the battery/mains status updated immediately, so that part seems to be working great.
I haven't had a chance yet to test the wired sensors, but I'm confident that'll all be fine too.
I have debug on, so I'll keep an eye on things as I play around more, but so far so good -- thank you again!!
Ok I was getting that on mine with no battery pack before I updated to 1.19, it’s an idle state message. When you get a chance post a log of what it looks like when you switch to battery and back to mains. Also do a refresh while on battery power to see what it sends back.
Right on... Here are the logs starting with the action of going from mains --> battery power, then doing a refresh while on battery, then going back to mains from battery.
Added this driver to HPM, pointing to the current beta version (which is on a separate gitHub branch if you go looking on my repo for it). Existing users can run a matchup in HPM and it should pick it up. Revamped the entire main post to be in line with my other drivers.
So far so good on testing it seems, I do have that unhandled event taken care of and reworked the power source refreshing based on the logs from @hydro311. I am working on fixing up the handling of switching the settings between F and C, trying to make it as user friendly as possible. The reports from the device will get converted to C/F based on your hub settings, regardless of the setting on the driver. Speaking of that confusing point I am changing some of the settings titles and/or adding descriptions where I feel it is needed.
Look forward to your experience... Mine is working well (AFAIK - I fortunately haven't had a need to truly find out!)
I got it right before they released the Z38, since I was interested in getting another device that could trigger a power-outage alert. I originally had just one Ring repeater in my setup carrying that responsibility. I've since picked up a few 38s, but this Titan is on a different circuit from those, so that's a nice win.
I of course also like the peace-of-mind knowing the main supply can still get cut off if things really go south.
Was the battery an addition? I don't have one. I use an old water cop for the main line and use the titan for the hose bibs. I'm on a well, so maybe battery isn't that important. I did a lot of thinking and rules regarding smoke detectors and cutting off the water.
Yes it’s not included and came out after the original launch of the shut off. They don’t do a great job of making it known on the product page for the zac36 either.
Mine's been working great.
I had it turning on and off once a day, plus, during the summer because I didn't trust the chintzy plastic hose bib timers to not break and spew water all over the place.
Something to think about is that Zooz actually publishes a number of cycles the valve is good for.
I'm not letting it stop me though, lol.
