The second alpha of v2026.11.1, still the simplification cycle. This is for the curious. If your garden depends on Smart Irrigation and you do not want surprises, stay on v2026.11.0.
If you installed alpha1, update. With "clear weather data" on (the default in 10.10), alpha1 undid its own move to the new model at every start, and a run that began while Home Assistant was starting could leave every zone as "valve did not open" (#1046, below).
Chained programs
A program can now start after another one, the way backup jobs are chained: "water the beds 30 minutes after the lawn is done". In a schedule, set When to After a program, pick the program, and how many minutes to wait once it has finished.
Until now, two programs that had to follow each other needed two start times, and a guess: the lawn waters longer on a hot day and shorter after rain, so the second program either started while the first was still running or left a gap. A chained program follows the first one whatever its length that day.
- It starts only when the first program really watered. Not when the weather held it back, when it had nothing to water, or when someone stopped it. Then it applies its own days and its own weather, as any start does.
- Running the first program by hand starts the chained one too.
- Chains can be longer: a third program can follow the second.
- Loops are refused (A after B after A), and a program another one starts after cannot be deleted.
- A start waiting for its minutes survives a restart.
- The planning, the week view and the flow place the chained run right after the other one ("after Lawn +30 min").
- It works in YAML too (
type: after,after_program,offset_minutes), and the assistants know it.
What it is for: programs on the same well, pump or tank, with a pause so the water comes back; something that only makes sense after a watering (a fertiliser program, a line flush); pots that only get water on Saturdays, after the lawn. See Chaining programs.
No main program any more
There was one main program, built differently from the others, and programs you added next to it. Now every program is the same kind of program, with its own steps and schedules, independent of the others.
- On update, the main program becomes an ordinary program called "Watering", once. It keeps the same zones in the same order, the same passes, soak and pause, and the same schedules: it waters exactly as before. You can rename it, and delete it like any other, except the last remaining program.
- "Program on" is gone, and so is the per-program switch. A program starts on its own only through its schedules: to stop one, switch its schedules off. It can always be run by hand. A program saved as off is moved once to "all its schedules off", so nothing starts that did not start before.
smart_irrigation.set_program_enabledkeeps working for your automations (it switches all the program's schedules), with a repair notice pointing toset_schedule_enabled. It will be removed in 2027.11.- A new zone has to be put into a program to be watered: there is no program that waters every zone by default.
- A program's id is now built from its name with Home Assistant's own rules (accents turned into plain letters).
- A schedule's "At" reads "When".
- Programs on supplies of their own now water side by side (thanks @johnnyh1975, #1044). Programs whose zones share a pump or main valve, or have none, still take turns.
Less, again
After @johnnyh1975's review of alpha1 (#1045):
- "Will it be skipped?" is one line when nothing holds the run back, with the details behind it.
- Pause, Next step and Stop are on the Home page only, no longer on the planning too.
- A schedule's days: the panel keeps the days of the week, every N days and a period of the year. Even or odd days, days of the month and months are now set in YAML. A schedule that already uses them still shows them.
- A running program says so in its own card (running, paused or waiting its turn, with its step and the time left), and its actions are small buttons in its header row, so the flow comes first.
- The Settings › General card that only pointed to the Weather tab is gone.
- The planning's "next three days" follows the number of days the chart shows.
- An inactive 10.10 start trigger is no longer lost in the move: it becomes a switched-off schedule.
Fixed
- The move to the new model now sticks (#1046, thanks @johnnyh1975). With "clear weather data" on, a stale copy of the settings written back a millisecond later undid it: the 10.10 start trigger was armed again and the move ran at every start. The moves now also run before the platforms are set up, which already arm the start.
- A run that began while Home Assistant was starting held the start up for the whole run (#1046): no automation ran meanwhile, and a valve that only reports its state once Home Assistant has started, such as a template switch, never reported open, so every zone ended as a valve problem. Such a run now opens nothing before Home Assistant has started.