altmenorg/HAsmartirrigation v2026.9.1-beta4

on GitHub

This is a pre-release. HACS only offers it if you have enabled beta versions. It follows beta 3 with a review of the whole integration, and it is almost entirely fixes: some of them change the numbers you get, as they are meant to, so the ones that do are listed first.

Read this first: what may change for you

• A sensor group field with no unit set now reads the sensor in the unit the sensor itself reports. Groups created by the setup wizard have no unit on their fields, and a wind sensor in km/h was read as m/s (3.6 times too strong), a thermometer in °F as °C. If your evaporation drops noticeably after this update, this is likely why. A unit you did set on the group still wins.
• Seasonal adjustments now do what the documentation says. The threshold adjustment was added to the stored bucket at every calculation, so a -5 mm adjustment became -10 mm the next day, and the zone was watered more and more for the whole season. The multiplier adjustment never applied at all. The multiplier now scales the crop factor, and the threshold adjustment moves the irrigation threshold.
• Continuous updates now give each zone its own window, as the scheduled calculation does. A group shared with a manual or disabled zone was never emptied, so each sensor change counted the whole buffer again, including the same rain.
• Solar radiation aggregated by Riemann sum, which the documentation recommends with continuous updates, is the day's mean rate again. The integral was being handed to PyETO as the day's value: over half an hour of constant sun, it produced 40% less evaporation than the Average aggregate.
• The watering calendar credits the rain. The month's rain was added to the evaporation and then subtracted again, so the need came out equal to the evaporation whatever it rained. Its climate model also had humidity, wind and rain peaking in summer instead of winter.

Watering and the bucket

• Direct valve control with no maximum duration (-1) credited every run with -1 second, so the bucket never refilled and the zone was watered again at every start.
• Zones entered as a precipitation rate are credited from that rate after a run. They were credited from the size and throughput the zone was created with, values the panel hides for these zones.
• Setting a bucket by set_bucket, reset_bucket, set_zone or the reset button keeps the evaporation from before it out of the next calculation, as it already did for the rain. set_zone and the reset button bypassed that handling entirely.
• set_zone refuses a state that does not exist (a misspelt state used to be stored), and no longer raises on a zone without a maximum bucket.
• The buffer of a group shared with a manual zone was never pruned and grew without limit; the week cap it promises always holds now.

Weather and calculation

• MJ/day/sq ft solar radiation reached the calculation 116 times too small; every pair of solar units is checked now.
• The pressure from OpenWeatherMap, Pirate Weather, or a sensor marked "relative", is brought down to your site's height (FAO-56). It came out all but unchanged at any altitude; the effect on the evaporation is under 1%.
• PyETO prices each day under the sun of that day: the middle of the readings' window, each forecast day at its own date, and each month of the calendar. The clock was used for all of them.
• Open-Meteo forecast days use the day's mean wind rather than its windiest hour.

Panel and entities

• Editing a zone sends only what you changed. The page posted its whole copy of the zone, so a page left open across the nightly calculation could revert its bucket and its explanation on the next edit. Two zones, or two settings, edited within half a second are all saved now, and a sensor can be removed from a zone.
• The Info page shows the real next start of a clock-time or solar azimuth trigger; it assumed "finish at sunrise" for them.
• "Irrigation needed" follows the zone's irrigation threshold, like the duration does.
• A zone's multiplier entity shows the stored value at startup, and the throughput check no longer flags zones entered as a precipitation rate.
• The Info page's remarks are no longer orange warning banners, and a sensor group's summary reads "7 sources · 3 zones".
• New screenshots on the front page, and the installation steps now say what is true: Smart Irrigation is in the HACS default store.