@franz I beg you guys to leave the Flex Schedule functionality in place!!!
I really do not like the new algorithm at all. This new algorithm guarantees there will be times that my grass will need water but won’t get it because it is on a “dumb” interval-based schedule. If I understand the new algorithm the only reason it is “better” than the “dumb” Rainbird timer I had before is:
- The intervals can be more than 7 days.
- The intervals are automatically adjusted throughout the year.
- A particular runtime can be skipped if the grass isn’t “dry” yet…I actually don’t consider this a good thing and I’d note that this behavior could be approximated with my old Rainbird timer and rain sensor.
I don’t understand why you’ve come to the conclusion that the old system was too difficult for the user? I picked my grass and sprinkler type and it automatically watered as soon it was necessary and for as long as it was necessary…what could be easier? I don’t see how this new algorithm makes things any easier, surely the user will still have to provide the same data (only now they’ll have inferior results).
…I suppose maybe I can set it to run everyday and everyday it’ll do the evap calculations to see if the run should be canceled? Maybe that’ll simulate the behavior of Flex Schedules?
You’re phrasing about not wanting to migrate was confusing. Are you saying that if I update my iOS app I won’t be able to use Flex Schedules anymore? Are you also saying that even if I never update my iOS app that at some point after the “watering season” the Flex Schedules will disappear?