Events

Main page: Usage
Previous: Services
Next: Automations

The integration fires the following Home Assistant events:

Event	When it fires
irrigation_plus_start_irrigation_all_zones	When a recurring schedule with the irrigate action runs. The event carries the schedule name and the targeted zones. Listen to this event if you control your valves with your own automations instead of linked entities.
irrigation_plus_recurring_schedule_triggered	Whenever any recurring schedule fires (before the action runs); carries the schedule details.
irrigation_plus_irrigation_started	When a self-closing zone starts a run (scheduled or manual). Carries the zone(s) with zone_id, zone (name) and seconds.
irrigation_plus_irrigation_finished	When a self-closing run reaches its end. Carries the zone(s) with zone_id, zone and the resulting bucket, plus a problems list. That list is empty for a normal completion; a run whose flow sensor measured no water across the whole window ends here too, is recorded as failed, and carries {"zone_id": ..., "reason": "flow_never_started"}. An automation that treats this event as proof the zone was watered should check problems.
irrigation_plus_zone_problem	When a zone's run fails. Carries zone_id, zone, entity_id and a reason. Reasons: valve_did_not_open (a self-closing zone's valve did not confirm open, e.g. the run service reported no state), flow_never_started (the run finished its window and its flow sensor measured no water — a dry cistern, a closed main, a blocked filter), plus the OpenSprinkler and batch reasons. entity_id names whatever the reason is about and may be null for reasons that name no entity.
irrigation_plus_zone_skipped	When a zone is skipped on an automatic run because its soil-moisture sensor reads wetter than the zone's threshold. Carries zone_id, zone (name), entity_id (the sensor), reason (soil_moisture), observed and threshold. The zone's bucket is reset to 0 at the same time. Listen to this to log/audit skips (e.g. write to InfluxDB).

The irrigation_started / irrigation_finished events let you drive a pump, a light or a notification from your own automation. If you only need a pump powered before watering, the built-in pump / master switch usually removes the need for a custom automation.

Important: the start event is fired only by schedules — if you have no irrigate schedule, it never fires. To reproduce the classic "irrigation finishes right at sunrise" behaviour, create a schedule whose Finish row is At sunrise, leaving Start on No limit (see Schedules); the schedule computes the start time from the estimated run length for you.

Note that Irrigate Now (the dashboard button) does not fire the schedule event irrigation_plus_start_irrigation_all_zones — it actuates the zone directly. For a self-closing zone it still fires irrigation_plus_irrigation_started, because that event tracks the run, not the schedule.

Main page: Usage
Previous: Services
Next: Automations