Second release candidate for v2026.10.1. Bug fixes only, as announced with rc1: nothing new, four faults found by running rc1 on a real installation before the stable. If you are on rc1, update.
Fixes
- Recurring schedules can be created at last. Creating, changing or deleting one with
create_recurring_schedule,update_recurring_scheduleordelete_recurring_schedulefailed with an error, and always had since schedules were added: the step that saves them was never written. Together with rc1's fix (a schedule never ran its action), recurring schedules now work end to end, which was checked on a real installation: a schedule created two minutes ahead ran its action on time. - A dry run of one zone writes nothing again. Since early September,
calculate_zonewithdry_run: truesaved its result for real: the bucket, the duration, the last calculation and the point the next calculation starts from. The all-zones dry run was not affected. If you used it on a zone, that zone was simply calculated, as if you had pressed Calculate. calculate_zoneandupdate_zonework with a single entity written as text, the usual form in YAML (entity_id: sensor.smart_irrigation_lawn). The entity was read letter by letter, no zone matched, and nothing happened, without an error.- Calculating a zone that has no new readings since its last calculation no longer raises an error; it says there is nothing new to calculate. The same fault was found and fixed by @frankyhun in their fork.
Everything in rc1 applies, including its changes to how much water some zones get.
Trying it
Enable beta versions for Smart Irrigation in HACS, update, restart, and reload the browser. 1823 backend tests.