franz will need to clarrify some specifics.
to get manual behavior, you should disable the smart technologies (weather data, smart budgeting etc.). this will water exactly as your schedules are configured. throw on a rain sensor and you will skip a schedule if the rain sensor is in a triggered state.
to get automatic behaviour, enabled the smart technologies (weather data, smart budgeting, etc.) and that is the behaviour i will discuss.
im also going to speak with authority here, but franz, please correct me where im wrong, im making some strong assumptions here. ill also defer to franz on 2.0, there is verbage on this forum that i understand, but have not been able to make my own observations yet, so i will most likely be speaking out of my anus.
the most important thing i would draw attention to is this:
the only thing that square footage is used for is to construct the gallons used graph that you can access via the cloud or phone app. nothing else, i have not found any uga or tif compnay research concerning turf management that use footage to determine how to water. it is assumed that the irrigation system follows good head to head coverage principles because the only thing that really matters is the flow rate of the head itself. your gallons used graph will be as accurate as your square footage and head type are configured, but still an estimate. i have asked them to support a flow meter, that would be the tits.
so let me answer your specific question and lets assume you set the schedule for a zone to water on tuesday and weds at 1/4 inch with all the smart technologies enabled.
as the software stands right now the schedule would run on tuesday for sure, AND then wed BUT ONLY if the vegitation/sun/soil type/head type and their intergalactic algorithm, indicates that the water that has been applied on tuesday has been been depleted. BUT! if a weather station reports that 1/4 inch of accumulation fell out of the sky on monday, the controller would most likely skip tuesday and water on wed. franz can speak to the tolerances of their algorithm but i cant.
my main complaint right now (supposed to be fixed in 2.0) is that if on monday we get 1/8 accumulation of rain, the controller is going to fire off and deliver 1/4 inch of water on tuesday (because the zone didnt reach its peak of 1/4). what i really want is 1 of 2 things:
either the controller to wait for the 1/8 to be depleted (reaching a dry root canopy, fungus is a problem here in ga when you keep your turf at .16 inch mowing height), then drop 1/4 inch on my yard 1 day after total depletion but on the next scheduled day.
OR the controller delivers 1/8th plus the estimated ET (evapotranspiration) on tuesday which equals the configured 1/4 inch for the zone the following schedule (because 1/8th fell naturally) then wait again for the zone to be totally depleted for an entire day before running the next schedule.
for now i get 1/4 plus the ET rate from the controller and this causes my ground to become soggy and over watered (because in this month, we get rain for an entire week at a time). this is the “aggressive” behavior i was referring to in my previous post.
im not sure exactly how their algorithm works, that is their intellectual property. im making some big assumptions based on my own research/measurements from the last 7 years, which helped me dial in my hunter pro c.
dont feel stupid, this is reasonably difficult stuff. if it was easy, rachio could not provide value to the irrigation market thus they wouldnt exist.