Simpler Scheduling for Spring

I look forward to the next generation of the software! Progress is a good thing! Since you’re working on scheduling software, it seems like the place to put my quarter on the table. I may bug support too.

Our lot is somewhat sloped and has dense clay soil. It doesn’t readily absorb water. With our old Rainbird sprinkler, we’d water each zone for 10 to 20 minutes, depending on the zone’s size. After all 6 zones had watered, we’d wait about 30 minutes and water them again. In very hot months (this is Texas, so it gets hot), we’d add a third cycle half an hour after the second one stopped.

It seems that your delay between cycles is more like, sprinkle zone 1 for 9 minutes, wait 9 minutes, sprinkle again.

Whatever the situation, we have water pouring off our yard and into the street. Luckily that’s not a ticketable offense, but it does get the local water militia after you.

A longer delay between cycles for dense soil would probably be a good thing™.

Thanks!

Thanks for the feedback, our smart cycles will cumulatively let the schedule soak for 30 minutes between zones.

Are you seeing different?

This article helps explain how they are implemented, and a cheat sheet to determine what you maximum recommended runtime is and more of an explanation of how the cycle/soak works with our schedules.

Have a great day!

:cheers:

I went out today and measured our zones to get watering times closer to something reasonable. That said, it seemed that the delay between cycles was much shorter than the amount of time mentioned in the article you pointed me to.

Is there a way to download the watering history into a spreadsheet? Honestly, the low contrast on your website in the watering history area makes it hard to read for older eyes. (The Color Contrast Analyzer add-in/extension for Chrome makes it very easy to see what people with mild, or severe, visual impairment - or who are just getting on in years - will see at your site.)

Thanks!

Continuing the discussion from Simpler Scheduling for Spring:
The time honored method of highlight, copy and paste worked. Looking at the history, it looks as though the delays are shorter than you think. I can send you a spreadsheet if you cannot see my history.

However, it seems that it will cycle through other zones only if they are scheduled for that day. So, if only one zone is scheduled, there will some very short delays.

With reports from neighbors of heavy water flow, my wife has been aborting sprinkler runs, so our history may not be the best to look at.

Thanks!

Looking at the calendar the cumulative soak time is 30 minutes. Even though the cycle is 11 minutes you need to take the other zone watering times into account which will always equal 30 minutes delay from when the zone runs again.

Hope this helps.

:cheers:

Thanks for the clarification. Still, judging by the water flowing into the street, the soak period wasn’t long enough.

In the old regime we had two 10 minute cycles and three 15 minute cycles followed by about a 30 minute pause. So, when we ran two cycles there was an 85 minute delay between the two runs in the front yard. (10+15+15+15+30). Runoff was minimal.

I should probably move this over to support with a headline of, “why are we getting so much runoff?”

Thanks!

@mavery76266, it might help to edit your soil type to change the cycle/soak times. Do you know what type of soil you currently have selected? The support team (support@rachio.com) can help you review if you’re unsure (please refer to this post for reference).

1 Like

I like the sound of bringing in history. My preference would be to apply it in terms of flex schedule prediction/estimation, but not to actual execution.

I agree forecasts are 50% a week out and less than useful so history helps.

But I’m getting more comfortable with flex the longer I use it. If I could get a report that shows historical use based on actual, next weeks estimates based on forecast, and the rest of the year based on historical, I’d be a happy camper. Esp if it was presented as a drill down on the water usage graphs, with one more depth added to the drill down - by zone.

By the way, did rain here this week on a day it was scheduled to water. Now I understand how it works :smile:

1 Like

All our zones are set to “clay” since we have a dense clay soil. Someone mentioned having to knock the clay off a shovel when digging. That’s us too!

Thanks!

1 Like

@brkaus, this how Water As Needed will run…historic weather data used to predict, real time weather data used to skip.

Historical to actual use reports will take some work, but we have some cool ideas in the works.

Estimates for the next week based on forecasts are not currently possible due to the weather check being performed roughly an hour before the scheduled watering event to determine if the watering can be skipped, however maybe the likelihood of skipping could be calculated in the future.

Schedules for the rest of the year based on historical weather data are already built. Sneak peek below :wink: …notice how the interval updates by month.



@mavery76266, sounds like a joy to dig in :grimacing:

1 Like

@emil @franz -> Thanks again to both of you for the conversation on the new scheduling. I really appreciate that your willing to engage the community the way you do!

I understand the value to some for the predictable schedule–however, I’d really prefer a system that performs a full watering on the specific day the lawn requires it as opposed to the system adjusting the run-time on a pre-scheduled day (or skipping until the next pre-scheduled watering) based on the calculated need on that particular pre-scheduled day.

From everything I’ve read, full waterings are the best for the health of a lawn (and also leads to the maximum water savings). It’s what drew me to my ESP-SMTe (and generated my initial interest in the Rachio). I would believe that your new method likely comes close in actual effect during use (assuming that the year is similar to historical data)–I just wish you’d leave in the existing method for power users who prefer using the full method. I know you’re grandfathering in existing users–but it doesn’t help a potential new customer like me.

To be candid, I’ll likely hold off on a purchase and continue to follow the customer comments and see what people think of it this year. But likely, the company that will ultimately win my business will be the one that follows the watering method that you had previously implemented.

Thanks again for your time–I do sincerely appreciate the conversation.

1 Like

Thanks for the feedback, very helpful. I do have some ideas next year how we provide this feature without using flex as it is built today :wink:

Hope to have you as a customer someday.

:cheers:

As a current, happy, flex time user, I have a LOT of trepidation about the the new schedule. I really agree with @bzimmer. I feel like I’m really being stupid and I know you have smart people working on this, but I’m just not getting it. I’ve just recommended this system to my daughter in Texas. She won’t be grandfathered in to the flex system. I’m sure hoping it goes ok. Sorry, but I was just a happy user with flex.

Thanks for the feedback, appreciated. I would have her start with a water as needed schedule and I bet the performance is going to be right on par. If not, PM me and I can try to work some magic.

For next watering season when flex is officially retired, I do have some ideas with the water as needed schedules to make them work very close to flex, if not the same, we just need to wait until we rebuild the calendar on the actual device firmware :wink:

Hope this helps.

:cheers:

Franz your Denver, CO example is off. We don’t start watering till April which I would think the frequency would be low and in July and Aug it would have this highest frequency and turning off in Nov.

Oh nooooo! I thought existing flex users could keep this feature indefinitely.

For next watering season we will make a few more changes to water as needed which I think will make the transition natural.

:cheers:

Count me on the list of someone that is concerned. I feel like the best direction would be improving the reporting on flex. Flex has all the correct underlying math and making people think about inches/gallons of water. That is a good thing. Something that starts with minutes is a step backwards in my opinion. May make it more “friendly” to new folks, but if I look at what flex is doing for me with the current predicted rains, actual rains, etc… it is doing the right thing.

For those that aren’t comfortable, there are timed schedules or other options… but the flex approach looks best from an execution standpoint. Simpler isn’t always better.

I’m hesitant to try anything new if I can’t go back to flex.

Thanks for the feedback. We will be taking feedback, improvements, etc. from this year and incorporating into scheduling.

Water as needed does take into account most if not all of the flex concepts. I believe after one more iteration we can bridge the gap for any concerns regarding existing flex functionality.

We are definitely listening and will continue to strive and build the most efficient scheduling software.

:cheers:

Yup, I know you guys listen. That’s why I keep blabbering :slight_smile:

As someone now comfortable with flex, in addition to what I suggested above about using historical weather for long term estimation (> 10 days in future), the two other enhancements controlling water application I could suggest is a second (optional) allowed depletion level that it would use if there was rain in the forecast in the next few days. I’m willing to let things get a bit drier if I think it is going to rain. There is probably also some factor for vegetation dormancy that is missing.

Throw a new user wizard for setup on top of it and all good!

1 Like