I don't see the value of creating a pretend monthly watering schedule in WAN + climate skip. The schedule will run when the zone (or one zone in a multi zone schedule) is dry. You don't know when it is dry without checking the weather each day. Just tell me the latest estimate of when each zone will need to be watered.
Skip and shift are the same thing when the schedule runs each day, aren't they? WAN does not allow any calendar restrictions, won't the schedule will try to run the next day and check for climate skip the next day? What is not explained is if the climate skip will skip just one day, or skip to the next preassigned date using the watering frequency for the month?
A single zone flex and single zone WAN schedule should operate the same way if they are using the same moisture level calculation. However in a flex schedule, I can specify which days to skip or an interval to run the flex schedule to accommodate watering restrictions, and also have multiple zones in flex where each will water independently when needed for each zone. No contest between flex and the new schedules, flex is far superior if current weather data is being used.
What is TLDR?
If I want predictable watering dates, then I will set a fixed schedule (with or without historical adjustments) and not use current weather to determine when to water. If I am using current weather to determine when each zone is dry and schedule a watering, then I don't care about historical averages. In that case, I would want a moisture level graph to show me the next predicted watering for any given zone. I just don't see any value in combining the two in a single schedule, let me pick one or the other.
In my original question, I was trying to understand how WAN was easier than flex, as that was one of the drivers behind the new schedules. I think it will end up being more confusing in the current schedule, with its limitations for multi zones, and all the weather intelligence options that can change the behaviour. I am waiting to see the next iteration of scheduling options.
Thanks for listening.