Automation makes your garden respond on its own: water when soil dries out, vent when it's hot, run a scene at dawn. Rules combine conditions (from sensors, time, and weather) with actions (devices, notifications, scenes).
Build a rule#
Go to Sensors → Automation (/sensors/automation) → New rule. A rule is
"when these conditions hold, do these actions":
- Conditions — add tests like soil moisture < 30%, time between 6–8am, no rain forecast. Combine them with AND/OR groups (and nest groups for "A and (B or C)").
- Actions — open a valve for 10 min, send a notification, run a scene, log an event, or wait between steps.
- Guards — set a cooldown (e.g. at most once per 6 h) and a priority so rules don't fight or spam.
The full grammar (condition types, operators, action types) is documented in the automation rule syntax.
Ready-made building blocks#
- Irrigation — schedule-, moisture-, or evapotranspiration-based watering with usage tracking.
- Climate control — vent/fan actions driven by temperature and wind.
- Scenes (
/sensors/scenes) — named bundles of actions ("Morning", "Heatwave") you can trigger manually or from a rule. - Alerts (
/sensors/alerts) — a focused rule type for threshold notifications (see IoT Setup).
Trust but verify#
- Rules only fire when enabled; start disabled and watch the preview.
- Every trigger is logged (with the conditions that matched), so you can see why something ran. Automation history also reports water savings and flags under-performing rules.
- Cooldowns prevent rapid re-triggering; manual override is always available.
Example#
Bed 3 low-moisture watering: when soil moisture < 30% and rain = 0, open the drip valve for 10 minutes and notify me — at most once every 6 hours. (Full JSON in the rule syntax doc.)