Market guide
Compare weather, sensors, flow and cloud behavior
Keep automation attached to its input and failure modeForecast weather, an on-site sensor, a flow meter and a soil probe observe different conditions. Compare what each controller measures, infers, stores and can actually change.
01
Weather
Name the data source
Record station selection, update interval, rain, wind, freeze and seasonal-adjustment logic plus the offline fallback.
- Forecast
- Internet weather may not represent rain or wind at the property.
- Freeze
- A skip or alert does not winterize exposed piping or prevent freeze damage.
02
Flow
Commission expected flow by zone
Match the exact compatible sensor, pipe size, placement and threshold behavior to known normal operation.
- Alert
- A flow anomaly does not diagnose the failed component.
- Shutoff
- A controller command cannot guarantee that a stuck valve, main break or unmonitored branch stops flowing.
03
Cloud
Audit service and privacy exposure
Record account, location, app permissions, stored history, plan limits, firmware and data-export or deletion behavior.
- Local first
- Removable connectivity and full panel programming can reduce service dependence.
- Security
- Keep controllers updated and isolated appropriately; connectivity does not make irrigation safety-critical protection.
Evidence used
First-party sources behind this guide
- 01Weather-based irrigation controllersU.S. EPA WaterSense · checked August 18, 2026Open source
- 02Weather-based controller resourcesIrrigation Association · checked August 18, 2026Open source
- 03Residential irrigation controllersRain Bird · checked August 18, 2026Open source