Skip to main content
All CollectionsOps Center
Irrigation Alerts

Irrigation Alerts

Overview of the text alerts sent by the Lumo Ops Center

Updated over 3 months ago

Irrigation alerts can be configured to notify users in eight (8) different irrigation scenarios, allowing you to act quickly in case of an irrigation issue. Users receive these alerts via text message.

Configuration

Alerts can be configured by contacting Lumo Support directly. They can be sent to users of the Ops Center, or individuals by phone numbers that can receive SMS notifications. Alerts can be turned on or off by individual, Farms, or Blocks in the Ops Center.

Alert Types

Scheduled Irrigation Updates

These below alerts inform users about the progress or status of a scheduled irrigation.

Schedule Alert

Scenario

Conditions for Sending

Start of Irrigation Schedule

Sent 5 minutes after scheduled start time of irrigation.

Send 1 per schedule (could be multiple Blocks)

Success

  • Valve confirmed that they received schedule

  • All valves are online

  • All valves report Open

Offline Success

  • Valves confirmed that they received schedule

  • At least one valve is offline

  • All online valves report Open

Partial Failure

  • Some valves failed to confirm schedule and/or report Open

Failure

  • ALL valves failed to confirm schedule and/or report Open

End of Irrigation Schedule

Sent 5 minutes after scheduled end time of irrigation

Send 1 per schedule (could be multiple Blocks)

Success

  • Did not send an “Irrigation Start - Failure” alert

  • All valves report Closed

  • All valves report zero flow

Offline Success

  • Did not send an “Irrigation Start - Failure” alert

  • At least one valve is offline

  • All online valves report zero flow

Partial Failure

  • Did not send an “Irrigation Start - Failure” alert

  • Some valves fail to report Closed
    OR
    Some valves continue to report flow

Failure

  • Did not send an “Irrigation Start - Failure” alert

  • All valves fail to report Closed
    OR
    All valves continue to report flow

Fault Detection

Fault Detection alerts inform users about potentially catastrophic issues that could cause damage to crops or infrastructure.

Flow Alert

Conditions for Sending

Possible Causes

High Flow Detected

  • Flow Rate at Block was ≥ 50% higher than the Expected** in the last 15 minutes

Leak downstream of valve

Low Flow Detected

  • Flow Rate at Block was ≥ 40% lower than the Expected** in the last 15 minutes

  • At least some flow was detected (i.e. > 0 gpm)

Leak upstream of valve

Clogged emitters / filters

No Flow Detected

  • No flow detected since the start of the irrigation

Manual valve turned off

Smart Baseline

Smart Baseline alerts engage users to alert them to irrigations that need their attention for calibrating the system.

Alert

Purpose

Conditions for Sending

Last 24 Hour Recap

Engage users with recent irrigations that need their input for calibration to complete

  • At least 1 scheduled irrigation occurred in the last 24 hours at a Block where Smart Baseline calibration is currently NOT complete

Last Week Recap

Remind users at the beginning of the week to engage with Smart Baseline

  • At least 1 scheduled irrigation occurred in the last week at a Block where Smart Baseline calibration is currently NOT complete

Did this answer your question?