Smart Irrigation — Maintained Community Fork

This is an actively maintained community fork of jeroenterheerdt/HAsmartirrigation, which has been stale since late 2025. It ships all the original functionality plus a growing set of bug fixes and improvements — see What's been fixed and improved below.

What it does

This integration calculates how long to run your irrigation system to compensate for moisture loss caused by evapotranspiration. It takes precipitation (rain, snow) and evaporation into account and tells you exactly how many seconds to irrigate — no more guesswork.

• Water only what evaporated — no over- or under-watering
• Tracks a running moisture balance ("bucket") per zone
• Supports multiple zones, each with its own size, throughput, module, and sensor group
• Works with Open-Meteo (free, no API key), Open Weather Map, Pirate Weather, or your own local sensors
• Guided setup wizard — a first-run wizard walks you through weather, calculation module, sensor group, and your first zone in a few steps
• Direct valve control — link a switch or valve entity to each zone; the integration turns it on, waits the calculated duration, and turns it off — no automations needed
• Everyday dashboard — the Zones tab is an at-a-glance dashboard showing, per zone, whether it will water and why, with one-tap Update / Calculate / Irrigate; full configuration lives under Setup → My Zones
• Forward-looking outlook — a banner shows the next scheduled run and whether it will likely be skipped (tap “Why?” for the reasons); per-zone decisions are honest about skip conditions
• Live status estimate — a read-only "Now ≈ −X mm" estimate of each zone's deficit since the last calculation, using the hourly FAO-56 equation where hourly solar data is available — so the status isn't stale between daily calculations
• Lovelace card — a custom:smart-irrigation-zones-card that mirrors the dashboard for non-admin users, addable to any dashboard
• Irrigate Now — trigger immediate irrigation from the dashboard (all zones or per zone), bypassing skip conditions
• Recurring schedules — create daily/weekly/monthly/interval irrigation schedules entirely from the UI (Setup → When to Water) — no automations needed
• Skip conditions — skip irrigation based on forecasted rain (with a configurable forecast look-ahead window), low temperature, high wind speed, or a rain sensor
• Soil-moisture veto — give a zone a soil-moisture sensor and a threshold; an automatic run skips that zone while it reads wet (a per-zone skip gate, never an ET input)
• Mechanical water distributors (experimental, opt-in) — drive a Gardena-style pressure distributor that splits one supply across several outlets; assign zones to its outlets and Smart Irrigation waters them in sequence and tracks the position. Enable under Setup → Experimental.
• Enforces a configurable minimum number of days between irrigation events
• Still fires HA events for power users who prefer automation-based control

What's been fixed and improved

Compared to the last upstream release (v2025.10.0):

Bug fixes

Issue	Fix
Dialog buttons invisible on HA 2026.3+	Migrated from deprecated mwc-button to ha-button / ha-dialog-footer
Sensor group edits silently discarded on save	Frontend no longer echoes server-computed fields back; backend sanitises before storing
Noisy WARNING on startup for sensor values	Downgraded to DEBUG
Pirate Weather precipitation off by 10×	SI mode returns precipAccumulation in cm, not mm — added ×10 conversion
API key / weather service change not taking effect after reconfigure	Options flow values now always win over initial setup data on reload
Days-between-irrigation fires at ~½ the configured interval	Counter was incremented twice per day (in skip path + at midnight); midnight is now the single source
Duplicate sensors after disable / re-enable	Fixed dispatcher listener leak + stopped removing entities from HA registry on unload
Bucket fluctuates with every forecast change	Now uses actual measured precipitation (rain.1h) instead of the daily forecast total

Improvements

• Redesigned UI — a guided first-run setup wizard, a slim everyday Zones dashboard (per-zone "will it water, and why" plus one-tap Update / Calculate / Irrigate), and all zone configuration / reporting consolidated under Setup → My Zones. Destructive actions now confirm, settings auto-save with a "Saved" indicator, and the General settings page is grouped into labelled sections.
• Direct valve control — link a switch/valve entity per zone; the integration controls it directly with no automation needed
• Zone sequencing — choose parallel (all zones at once) or sequential (one at a time) in General Settings
• Recurring schedules — full create/edit/delete UI for irrigation schedules inside the panel
• Irrigate Now buttons — on the Zones dashboard (all zones or per zone), bypasses skip conditions
• Skip conditions — temperature threshold, wind speed threshold, and rain sensor entity added alongside the existing precipitation forecast check
• Fully localized — the panel ships translations for 7 languages besides English

Note: the old Seasonal Adjustments tab was removed in favor of the more flexible Schedules system. If you relied on it, recreate the behavior with per-zone multipliers and recurring schedules.

• Open-Meteo weather service — free, no API key required
• Mobile-friendly number inputs — Zone float fields use step=0.1 + inputmode=decimal; integer fields use step=1 + inputmode=numeric; values parsed with valueAsNumber to avoid browser format differences
• Extended sensor attributes — multiplier, lead_time, maximum_duration, maximum_bucket now exposed as entity attributes for use in automations and templates
• Code hygiene — removed ~280 lines of dead commented-out V1 code, duplicate constant definitions, and orphaned test files

Self-closing valves & blueprints

A zone can delegate the valve close to self-closing hardware. In Setup → My Zones → (zone) → Watering mode, pick one of:

• Classic (default) — the integration opens the valve and closes it itself with a software timer. Simple, but if Home Assistant restarts mid-run the valve stays open until HA comes back.
• Self-closing service — the close is owned by the hardware, not by HA. The valve runs its own countdown: once it is told a run duration it shuts off on its own after that time, with no further contact from Home Assistant — so even if HA restarts or crashes the instant a run starts, the valve still closes and can't over-water. The zone calls a script (picked from a dropdown) that only transmits the duration to the valve; the script is an adapter, not the thing that closes the valve.

Self-closing hardware means anything with its own timer: Zigbee2MQTT valves with a built-in countdown (Tuya countdown_l1, SONOFF cyclic_timed_irrigation), or a DIY/ESPHome controller that closes its own valve after a received runtime. (A plain switch with no hardware timer is not self-closing — use Classic mode.)

To make the script part painless, three script blueprints ship with the integration and are copied into config/blueprints/script/smart_irrigation/ automatically on setup (existing files are never overwritten):

Blueprint	For	Notes
Tuya TS0601 dual water valve (Z2M)	Tuya TS0601_water_switch ("Dual water valve")	publishes countdown_l1 (minutes) + state_l1 ON/OFF — Duration unit = Minutes. Older/custom converters may use valve_l1/on/off.
SONOFF Smart Water Valve SWV (Z2M)	SONOFF Zigbee Smart Water Valve (SWV)	publishes cyclic_timed_irrigation — Duration unit = Seconds
Self-closing valve (entity based)	ZHA / non-MQTT valves	writes a countdown number entity then turns the valve on — requires a hardware countdown entity

Setup:

1. Settings → Automations & Scenes → Blueprints → find the blueprint → create a script from it, filling in your valve's MQTT topic (or entities).
2. In the zone, set Watering mode = Self-closing service, pick your new script under Run service, and set Duration unit to match your device (Tuya = Minutes, SONOFF = Seconds).
3. Optionally set Stop service to the same script — it closes the valve when you stop a run early.

Each blueprint's script opens on duration > 0 and closes on duration = 0, so one script serves as both the run and the stop service.

Blueprints only cover common cases. Any script that accepts a duration field works — the device specifics live in the script, so the same mechanism drives Z2M, ZHA, ESPHome, or anything else.

Pump / master switch (optional)

If a pump or main valve must be powered before any zone can water, configure a master switch under Setup → General → Pump / master switch:

• Master entity — a switch/valve/input_boolean HASI turns on before the first zone of a cycle. Leave empty to never touch a master (e.g. a pressure-controlled waterworks that starts on its own).
• Kicker (optional) — some pressure-controlled pumps don't restart promptly when merely powered; the kicker pulses the master off → pause → on to force a start. The pause is configurable.
• Settle delay — wait after power-on before the first valve opens (pressure build-up), default 10 s.
• Turn off after irrigation (optional, default off) — off = the master stays powered (self-monitoring pump); on = HASI turns it off after the last zone's planned end, and only once no run is still active.

The master applies to every path (scheduled, "Irrigate Now", and manual runs), for both classic and self-closing zones.

Crash caveat: with "turn off after" enabled, an HA outage after the master turns on but before the scheduled off leaves the master on — a non-self-protecting pump could dead-head or run dry. HASI can't prevent this alone; the master device must carry its own protection (dry-run cutoff, max-on timer). This is exactly why "turn off after" is optional — a self-monitoring pump omits it and carries no crash exposure.

Soil-moisture veto (skip when wet)

Give a zone a soil-moisture sensor and a threshold under Setup → My Zones → (zone). On an automatic (scheduled) run, if the sensor reads above the threshold, HASI skips that zone and resets its bucket to 0 (re-anchored to field capacity). Manual Irrigate Now always waters, and an unavailable or non-numeric sensor never blocks watering (fail-open).

Soil moisture is used only as a skip gate — never as an ET input, so the water-balance model is unchanged. The sensor picker is restricted to device_class: moisture. Each skip fires a smart_irrigation_zone_skipped event, shows a dashboard chip, and is recorded in the zone's run history. See My Zones → Soil-moisture veto.

Mechanical water distributors (experimental)

A mechanical pressure-driven indexing distributor (e.g. a Gardena Water Distributor) splits one supply into several outlets, advancing to the next each time the water is pulsed off and on. Enable it under Setup → Experimental → Mechanical water distributors (off by default), then assign zones to its outlets under Setup → Distributors. Smart Irrigation waters the mapped outlets in sequence, tracks the blind position, and coordinates a master valve/pump. See the Distributors docs.

This is a new, experimental feature that could not be fully hardware-tested — treat it as a beta and watch the first days of use closely.

Installation

This integration is not in the default HACS store. Install it as a custom repository:

1. In Home Assistant, open HACS → Integrations → ⋮ → Custom repositories
2. Add https://github.com/JustChr/HAsmartirrigation with category Integration
3. Search for "Smart Irrigation" and install
4. Restart Home Assistant
5. Go to Settings → Devices & Services → Add Integration, search for "Smart Irrigation" and follow the wizard

Manual installation

Download the latest release as a zip, extract the custom_components/smart_irrigation folder into your Home Assistant custom_components directory, then restart.

Documentation

Full documentation: https://JustChr.github.io/HAsmartirrigation/

The docs site is built from the docs/ folder with Jekyll and deployed automatically by the Pages workflow on every change under docs/.

Reporting issues

Open an issue at https://github.com/JustChr/HAsmartirrigation/issues

Development

Quick start

git clone https://github.com/JustChr/HAsmartirrigation.git
cd HAsmartirrigation
make setup          # creates .venv and installs dependencies

Useful commands

make test           # run the test suite
make lint           # ruff + prettier
make format         # auto-format Python and TypeScript

Frontend

The frontend is a TypeScript / Lit bundle. After editing files in custom_components/smart_irrigation/frontend/src/:

cd custom_components/smart_irrigation/frontend
npm run build

The compiled dist/smart-irrigation.js is committed to the repo (gitignored but tracked) so users don't need Node.js to run the integration.

Tests

pytest tests/        # or: make test

See CONTRIBUTING.md for more detail.

Credits

Original integration by @jeroenterheerdt. This fork picks up active maintenance and applies community-contributed fixes from the upstream pull request queue.