I have a rule that runs ~3am every night that refreshes a bunch of devices (incl my Titans), resets some Private Booleans, etc -- it just does some housekeeping to make sure everything's set for the next day.
If you consider doing something similar, just make sure it's time deconflicted with any automatic hub backups that typically run around that same time.
If you use DAC to monitor last activity you can set it to refresh the device for you if needed. [RELEASE] Device Activity Check - Get notifications for "inactive" devices
Otherwise you could just set up a daily rule to run the Refresh command.
Thanks. I went with DAC and it is working great.
Question about leak detection reporting. Recently had to remove the Titan and reinstall it - shutoff valve got too rusty and replaced it - but after reconnecting the Titan, it's constantly in an alarm state and won't stop beeping and flashing a red light. Also thinks that a leak was detected based because my hands were wet when handling it. I set parameter 48 to 0, 49 to 0, 50 to 0, and 51 to 0, and still showing as "leak detected yes" in Apple Home. Any advice on how to clear whatever setting is reporting the leak? Much appreciated.
Oh and param 84 is set to 0 as well
Are you wanting to remove the leak sensor and stop using it?
I would enable the leak sensor again and run a refresh, it should update it to dry. Make sure it is clicked into the power fully, on the newer models you have to push harder than you would think to get it in all the way.
Could also trigger it again with a wet paper towel, then dry it and it should report dry back.
Worst case you could also change the driver to "Virtual Leak Sensor" and then manually change it to "dry". That should push the dry state back over to homekit.
Thanks jtp. I'll try that when I get back home later today. Also, do you know how to manually check the value to see whether the leak detector (from the Titan) is active? I'm solely basing this off of Apple Home and maybe that's the issue and not the actual titan leak detector itself).
What do you mean by active? I dont think there is any status messages it sends to indicate if the leak sensor is connected or not, if unplugged I think it just sends Dry as a response when refreshed.
Thanks - by active, I mean which parameter would be signaling whether the titan is wet or dry?
Parameters are the settings, so none. The Attribute (Current State) of water is what gets the values of wet or dry.
Thanks again, jtp. What ended up working was enabling the leak sensor report (param 84) and a refresh. Thanks!
I have the valve fed into homekit but when in the open state it shows as "Waiting...". It does work to open and close the valve. When in closed state it appears to look normal.
It seems someone else had the same issue with another water valve and fixed but unsure of what needed to be changed in the driver. (Cant post links) Sonoff Zigbee Smart Water Valve thread on the forum.
Join the owners group to post links and images: Hub owners - Hubitat
I found the post I think you are talking about. I do not see there was any other follow up on that "Waiting..." message. The follow up afterwards was about an issue where when the valve was opened the state did not update unless they did a refresh.
I have mine shared to HK via Homebridge and mine looks the same with the Waiting... message in the toggle. No idea what it means.
Thanks for the info, as long as it works I'm happy. I previously has a leaksmart valve set up the same way and it never showed as waiting. I couldn't find any documentation on what homekit expects to receive to clear the waiting message.
I had installed my new ZAC36, changed to this community driver, and I believe it was working normally. Then I had to exclude and delete all my Z-wave devices to mess around with SmartStart and my ZSE42 leak sensors. After I got the leak sensors included properly again, I factory reset the Titan, re-calibrated it, and re-included it.
But now I'm seeing this strange behavior whereby the Current State of the valve, when it is initially open, then I command it to close, first changes to "working", then to "open" again. And then the Valve command button still shows Open. However in reality the valve HAS closed.
Oddly, using the web page in Chrome on my desktop Windows computer, the behavior is as described above. This means there is no way to open the valve after closing it, because the Command button immediately goes back to showing Open, and does nothing when you click on it (either left or right side of the button):
Whereas, using the Hubitat web page in Chrome on my Android phone, there are separate buttons for Open and Close, so I can use them to open, even though it thinks the valve is still open.
I've forced a recalibration from the Closed state, but this hasn't helped.
What could be causing this odd behavior?
Here are the log entries starting from the command to close (with valve initially open):
If I then click the Close command:
Clicking Open does nothing. However, after clicking Open using the browser interface on my phone:
So it seems that the valve itself knows it's closed, after executing the command to close; because if you command it to open, it does so. But the driver seems to get confused, and doesn't get the information that the valve is closed, after telling it to close.
This definitely seems weird.
You can turn off this option to expose the command buttons
What hub model? What platform? Are you running Zwave JS? (you can tell by the switch button on the zwave details page if you have a C8 Pro)
Have you run configure at all?
Turn on TRACE logging and get logs again.
Great; thanks! I hadn't realized what that "Show common commands first" was for!
C-8 Pro, Platform version 2.4.3.133.
I am not running Zwave JS; it's legacy.
Yes, I ran configure after initially changing to this driver, and have also done so several times since.
With Trace logging, here is what I get after a close command:
And then here is what I get after a subsequent open command:
To my untrained eye, it appears that the Titan is sending the exact same trace message after closing the valve as it does after opening the valve...
I wonder if I should try forcing a calibration again.
My ball valve is 1-inch size and is quite hard to turn.
At first I wasn't sure the actuator would have sufficient torque to turn it.
During the calibration process it attempts to open the valve several times, apparently trying more and more torque each time, until it finally succeeds.
So I'm thinking maybe when it closes the valve, it's not quite getting it 100% closed, so that the limit switch doesn't quite trip. Of course I have no idea what the internal design of this actuator looks like.
If I force calibration again (close the valve, then hold the button for 5 beeps, then 5 quick presses); will I need to do anything further before trying it again?
Could be some sort of settings conflict. Set all the non-numeric settings to the indicated defaults. Also what firmware version is the ZAC36 (should be visible on the info tab).
Nothing else is needed, I would try doing that.
You can also adjust the open/close angles in the settings although I will be honest I am not 100% sure how it works. On my test rig with a plastic handle I did adjust one of those to make it close less so it would not snap my handle off. It might explain it more in the Zooz online docs.
