A bugfix release for one bug that matters: a zone could be set up so that it was never calculated. If your zones show "Last calculated: —" and the log says "its engine returned nothing", this is the fix. Nothing to do after updating: the affected zones are repaired at startup.
Fixed
-
A zone without a calculation engine was never calculated (#907). A zone added on the Zones page was saved without an engine, and a sensor group created by hand has none to lend it. Nothing could then calculate the zone, while its card said "Calculated by Smart Irrigation", which is what the panel shows for a zone without an engine. Every calculation failed with a message about a provided evapotranspiration missing from the sensor group, which pointed at the wrong place.
- A new zone without an engine is now calculated from the weather, as its card says. A zone that borrowed its sensor group's engine gets its own of the same kind, with the same options.
- At startup, zones already saved without an engine are given one the same way. They calculate at the next scheduled calculation, or right away with "Calculate all zones".
- When a zone still cannot be calculated for this reason, the log now says that it has no calculation engine.
Reported by @89890-prog, with a diagnostics file that made the cause plain.
Weather readings collected before the update were cleared at the usual daily time and are not recovered, so the first calculation covers the readings collected since then 🌱