Manual Default Setting
Previously, the default watering time was fixed at 10 minutes. Now you can customize the default water volume or watering duration based on your needs.
Schedule Setting
Supports up to 6 schedules for more flexible watering automation.
Child Lock Function
Helps prevent accidental operation for safer use.
Abnormal Alerts
Supports water shortage and leakage alerts, so issues can be detected in time.
Seasonal Watering Adjustment
Adjust watering plans according to seasonal changes for smarter and more efficient irrigation.
Please note that the volume unit switching feature (L / gallon) is not available yet. We are already working on this optimization, and a new firmware update supporting volume unit switching is expected to be released in early July.
When will you expand the control options for your own gates? It’s sad that you can’t fully control the valve through scenes. What did you use Cycle irrigation for when it’s actually unusable?!
Thanks for the feedback. I may not have fully understood the issue yet. Could you please share a few more details so we can look into it and improve the experience?
Are you saying that the device cannot be controlled via Scene automation at the moment, or that Cycle Irrigation cannot be configured on the device control page?
At the moment, 【SWV-BSP/NH】 does not support configuring 【Cycle Irrigation】 in Scene automation. Only 【Single Irrigation】can currently be set in Scenes.
We appreciate your suggestion, and we will evaluate its feasibility for improvement in a future version.
For now, you can still achieve a similar effect directly from the device page. After setting the irrigation duration, cycle count, and interval time, just tap 【Start Irrigation】.
For example, if you set the irrigation duration to 【20 minutes】, the cycle count to 【100】, and the interval to 【1 day】, the device will irrigate for 【20 minutes 】every day for the next 100 days.
Should I tell the customer to turn it on manually when needed? Then he won’t buy it because he doesn’t want to worry about watering and wants it to work without his intervention!!!
Irrigation cycles cannot be configured direct from the scene.
First of all, thank you very much for publishing the ZHA quirk for the Hydro ONE series. It is a great improvement compared to the native ZHA support and it exposes many useful features that were previously unavailable.
I have been testing it with a SONOFF Hydro ONE Lite (SWV-ZNE) and I would like to share some feedback and ask a few questions.
1. Schedule programming
The main issue I have found is related to the irrigation schedules.
The quirk exposes the entities to configure a schedule (plan index, start time, duration, repeat mode, weekdays, etc.), but it is not clear how multiple schedules are supposed to be managed.
For example:
I can change the Schedule Irrigation Plan Index.
I can press Schedule Set.
However, I cannot understand how to switch between different stored schedules (for example Schedule 1 and Schedule 2) to verify or edit them independently.
It seems that only one schedule can be edited at a time, although the valve itself supports multiple schedules.
Could you please clarify whether this is the expected behaviour or if there is currently a limitation in the quirk?
2. Documentation
I believe many users would benefit from some documentation explaining what each entity does and how it should be used.
For example:
How to create multiple irrigation schedules.
Meaning of each Schedule entity.
Difference between Repeat Mode options.
Recommended workflow to save, edit and delete schedules.
Seasonal Adjustment usage.
Rain Delay behaviour.
Manual irrigation entities.
Without documentation it is quite difficult to understand the expected workflow.
3. Example configuration
It would also be very helpful to include one or two practical examples, such as:
Irrigate every day at 08:00 for 5 minutes.
Irrigate every day at 20:00 for 5 minutes.
This would make the quirk much easier to use for Home Assistant users.
Thank you again for your work and for supporting ZHA. I appreciate the effort that has gone into developing this quirk and I hope this feedback helps improve the user experience.
