Hi - I'm new to the community and my first time using Hubitat. I have a C-8 and paired the ZAC36 to Hubitat. However, Hubitat is showing that the device is in the "Closed" position despite the device being in the open position. I understand that there's a parameter 17 that can be toggled to either 0 or 1. Can someone please help me with next steps as to how to invert this parameter setting? Thanks in advance!
If you are not already using my custom driver from the first post, please try that. You can install it via HPM (recommended so you get updates) or manually. The HPM instructions are linked to in my first post. Here are the docs for installing code manually: Drivers Code | Hubitat Documentation
I think you will find once you switch to my driver the status will be reported correctly.
1 Like
Thanks! I installed HPM and your driver through that. Enabled the inverse switch report and now it's reporting properly. Thank you!
The inverse switch setting should not impact the "valve" state on my driver. I belive I have it setup to report the open/close correctly with either setting. That setting will only impact he "switch" state that is reported. Zooz told me it is for legacy hub support and they wanted me to make it off by default because that is less confusing to people.
Thanks for the clarification. Just to confirm my understanding is correct, if I want to setup an automation/rule when a leak detector detects a leak and I want to close the valve, would I set the valve to "close" after enabling the inverse reporting? Or would I set it to "open" (which would close the valve, inversely speaking). Thanks!
Close will ALWAYS close the valve. The inverse setting only changes the "switch" state/commands, not the valve state. Best way to use it is just ignore the switch state and always rely on the valve open/close state.
2 Likes
UPDATE
Mostly just a maintenance update but a lot of code changes, let me know if any issues.
Version [1.0.6] - 2025-02-15
- Added singleThreaded flag
- Update library and common code
- First configure will sync settings from device instead of forcing defaults
- Force debug logging when configure is run
- Changed Set Parameter to update displayed settings
- Added associations support
- Added driverVersion state and automatic configure for updates / driver changes
- Updated support info link for 2.4.x platform
3 Likes
New Hubitat user, new C-8 Pro hub w/ updated firmware, installed the Zooz Titan ZAC36 actuator, calibrated (operates fine). Without your driver was getting the incorrect valve status. Installed HPM and today's version of your code, pressed the configure button on commands tab in the valve device but I don't believe the new code is functioning as I don't see the 'inverse switch' option in the preferences tab. Am I missing something??
1 Like
Just to double check. Did you select the customer driver before clicking configure?
The built-in driver should have been selected automatically when you paired the valve. After you installed this custom driver you need to select it on the device details page. Once it is selected you click configure.
Edit: I should add that you need to select the custom driver on the device details page and then click save. After clicking save you can continue the process by clicking configure.
2 Likes
Thanks - took me a while to understand that I had to select the driver in the 'Type' field in the Device Info tab. Found the inverse switch report toggle - all good now!
2 Likes
3 posts were split to a new topic: [2.4.1.121] ZWJS - Zooz ZAC36 custom driver errors
Thanks for this driver. I've had a waxman leaksmart valve for nearly a decade and it failed and doesn't close the gate. So I didn't really want to pay to have a new smart valve installed (and I think that model was discontinued) So I bought the titan to use on a ball valve that luckily I had installed to block off the leaksmart should it ever fail.
Device type works great! Only issue I'm having is that the "dumb" water sensor that is included is not registering wet and therefore not closing the valve. Happy to hear if anyone has ideas on it otherwise I'll contact the merchant during the week.
1 Like
Make sure it is plugged in fully. I recently got one of the newer 800LR models and I also thought the sensor was broken, pushed it in harder than I thought I should have to and it snapped into place, now its working.
2 Likes
yup that was it
1 Like
My ZAC36 when viewed in the "Devices" area on the iOS App shows up with a question mark and "unsupported".
How can I go about tweaking/changing thigs so that I can see the status of the valve and also control it via the app?
Hmm, mine shows up as a leak sensor. Issue is the device has multiple capabilities and the devices page does not have a way to select which one to show.
I think that is being worked on right now with the current beta app and platform: [iOS Mobile App Beta 2.1.1] What’s new in build 390 "Dashboard like devices" I think will allow you to customize the tiles.
Otherwise for now you would have to make a dashboard so you can set the tile as a valve.
Or you could also create a Virtual water valve (or switch) and then sync that with the real device with a rule or the Mirror app. Using the virtual devices has a better chance of working because there will only be one capability.
I just switched to this driver for my ZAC36, installed from Hubitat Package Manager, thanks. Hub C-5, Platform 2.4.0.151
Getting this Java error when hitting Configure:
[edit] Another log of the Config error:
Also seeing a conflict in what firmware version it reports. On the Commands page I get 1.19 and on the Device Info page I get 2.10 (which is probably correct given the reported hardware version of 4):
[edit 2]: Maybe the data on the Commands page was leftover from the firmware flashing. It eventually cleared when I used the "Device" driver to clear states.
Yes, it was
I think the errors might be from values on the settings which are not set at all (blank). It should be the Temperature Units for Settings setting. Make sure it is set, save, and try again.
2 Likes
That particular setting appeared to be set on the Preferences page, but I selected F anyway. After I hit Save, parameter 81 was the only that showed in the logs. See below. Configure worked this time with no errors. There were a number of other parameters from 34 on up that went from null to a value. Thank you.
Is it possible to force the device to check in more often? I use an app to ensure all devices have reported in every 72 hours and since this device is mains powered and in a temperature consistent room, there is no state change often enough to demonstrate that it is online. which is important to me for such a critical device.
I see that there is a scheduled job of checking in, but that date/time comes and goes and just seems to reschedule itself.
What can I do to be sure this device is online? I know I can force the valve to change its state but that seems like unnecessary wear. Thanks.
