This is a pre-release. HACS only offers it if you have enabled beta versions. Everything from beta 1 and beta 2 is in it, plus the changes below.
Read this first: solar azimuth triggers will fire at a different time
If one of your start triggers is a solar azimuth trigger, it has been firing at the wrong time, and after this release it fires at a different one. That is the correction.
Three errors sat on the same path. The sun's azimuth was computed with the longitude applied the wrong way round and without the equation of time, which put the sun 9 degrees off in western France, 48 in Berlin and over 100 in California or Australia. The trigger then handed it the local time where it expected UTC, which moved it again by your time zone's offset, two hours in a French summer. And with manual coordinates set, it took the latitude from them but the longitude from Home Assistant. The azimuth is now astral's calculation, the one Home Assistant's own sun uses, and it is tested against solar noon worked out by hand for four sites.
Sunrise, sunset and clock-time triggers are not affected.
New: skip a run on measured conditions
Four conditions, all off by default, that are checked when the first start trigger of the day is reached:
- Rain sensor: skip while a binary sensor says it is raining.
- Freeze: skip at or below a temperature, 2 °C (36 °F) unless you set one.
- Wind: skip at or above a wind speed, 20 km/h (12 mph) unless you set one. In strong wind a sprinkler waters the path, not the bed.
- Soil moisture, per zone: give a zone a soil moisture sensor and a threshold, and while the soil is at or above it that zone sits the run out while the others water. Its bucket is kept, so the deficit rolls over to the next run. The sensor does not enter the water balance: it only says when the soil already holds what the balance says it lacks.
Freeze and wind read the sensor you choose, in whatever unit it reports, or the weather service's current reading when you choose none. They are under Settings > General; soil moisture is on each zone. The Info page shows each condition with its numbers, and the skipped event carries the reason.
A sensor that cannot be read never stops a run, and neither does a condition that fails outright: watering goes ahead as it would without it.
Rain from a gauge whose total is revised down
A "rain today" sensor fed by a web service restates its total as the service corrects itself, sometimes downward. The Delta aggregate took such a drop as a new starting point and counted the climb back as new rain: 4.3 mm, revised to 3.0, then 5.0 booked 6.3 mm where 5.0 fell. The fuller bucket then watered less than the zone needed. A counter that restarted at midnight and was first read at 0.2 rather than 0 lost those 0.2 mm. Only a total above the highest one seen is new rain now; a drop to 0 or across midnight is a reset, and any other drop a revision that counts nothing. Reported by @Megalos.
Also
- The documentation now has a section on the conditions that skip a run.