I’ve got 2 zones surrounding my house, left and right. Since I live in Texas with crappy soil, watering evenly is important.
However, although both zones are configured EXACTLY the same (advanced parameters checked as well), one gets one more minute of watering than the other, which makes that region have just a little bit more moisture. Over time, that difference might end up having one side watered one day, but not the other, which is exactly what I want to avoid.
Also, they are both part of the same Flex Daily Schedule. And if I look at the Watering Times, they both show the same amount of minutes. But when I look at the history of each zone, I do see that one zone gets one minute more than the other.
I tried doing a fresh start on both zones by setting their moisture level to either full or empty, but later on I still see the same discrepancy.
I had the same or similar issue. I’ve got 2 zones that were split from one zone for flow pressure reasons I guess. But they need to run on the same day, close in time for them to complete the square precipitation rate.
The culprit was the minimize water hammer setting. I guess in order to minimize water hammer, one zone will start earlier or run later than it should, not sure what it is, to overlap the run. Meaning if you have one running for 10 minutes then I guess around the 9 minute mark the other will start and run at the same time or start something to that nature. What ever it is, it is enough to push one of the zones that ran longer to the another day depending on weather conditions like very hot days with high ET.
Other things I found from troubleshooting is that the decimal values that return from the API seem to be of low precision. In programming terms, meaning that there is weird behavior in the decimal places to warrant suspicion that it is using something like Float32 or lower. For instance, if you set the available water to 0.12 then your will get 0.1192319 or 0.121234 or something to that nature back from the api but the app shows 0.12.
Thanks for your reply. Yes, I do have water hammering enabled. I had it enabled from the beginning (2017) just thinking it was better to enable it than not, not necessarily because I had an issue. How did you solve the issue yourself, disabling it? The other option might be manually reducing the watering time for the zone which normally gets a little more because of this.
If you have bad water hammer then I suggest maybe you keep it on and understand that maybe it is causing weird behaviors. I did had a water hammer issue but when I switched all heads with pressure regulated heads and nozzles with high efficiency ones like hunter pro he for the sprays and krain for the rotary, the hammer significantly reduced (barely hear it now). When I turned off the reduce water hammer option, that weird behavior with one zone getting pushed to another day stopped. Based on what I observed, it will not stop water hammer when the sprinkler system first turns on or when it comes out of a soak with no other zones running, just the cycling it mitigates the hammering if I am correct.
As per the other posts from the link, I saw that one person switched values and back and got weird values that was not the same as before. And others observing abnormal rounding with water hammer turned on. I also noticed those things and is interesting if this is still an ongoing issue.
Yes, this is due to the water hammer feature. Schedule will show the scheduled times, and history will show actual times which account for the extra overlap of the water hammer, rounded up to the nearest minute. Actual event doesn’t add more than 10 additional seconds to the run, so does nothing to really change your watering.
