Why Did Controller Skip The Program: Rain Sensor Vs Clock Vs Power Decision Tree

Why this matters

"The sprinklers did not come on this morning" is a daily callback for any company with an irrigation maintenance program. Most of the time, the controller skipped the cycle intentionally; the customer just did not see why. Pulling the controller's log or applying a structured three-branch diagnostic (rain sensor branch, clock-and-power branch, program-and-budget branch) resolves the question in under 15 minutes. Misdiagnosis sends a tech back with a new valve solenoid and a confused customer.

Symptom presentation

A scheduled cycle did not run, or only some zones in the program ran. Other days in the same week ran normally, or every day this week has been skipped. The customer noticed because the lawn is showing early drought signs in spots, or because they happened to be outside at the usual run time. Manual operation works (the zones fire when the tech runs them at the controller). No visible damage at the controller, no smell of burnt insulation, no obvious failure indication on the display.

Quick checks

Photograph the controller display. Read the date, the time, the current mode (Auto, Off, Rain Delay, etc.), the active program, and any sensor status icons. Most modern controllers display a "Rain Sensor Active" indicator, a Wi-Fi status, and a battery icon for the backup clock battery.

Pull the cycle log if the controller has one. The log will plainly state the skip reason: "Skipped: rain sensor," "Skipped: rain delay," "Skipped: forecast rain," "Skipped: seasonal adjust 0 percent," "Power loss," and so on. Many troubleshooting visits end at this step.

Walk to the rain sensor. Most are mounted on the roofline or a fence post for an unobstructed sky view. The sensor disc should expand when wet and contract when dry; visually confirm it is in the expected state for current weather.

Isolation tree

Branch one, rain-sensor logic. Look at the controller display for the sensor-active icon. If present, the controller is reading the sensor as triggered. Verify: (a) the sensor wires at the terminal are intact, (b) the sensor disc is responding to ambient humidity correctly (not stuck swollen from a failure), (c) the sensor bypass switch on the front panel is not in an unexpected position. Bypass the sensor temporarily and run a test cycle. If the test runs normally with the sensor bypassed and the sensor disc looks stuck or damaged, the sensor is end-of-life. Replace.

Branch two, clock and power. A controller that suffered a power outage and could not retain time from its backup battery defaults to a midnight time on January 1. Programmed start times based on AM/PM never come up because the controller thinks it is a different day or different time. Confirm the displayed clock matches actual time; if not, set the time, restore the schedule, and replace the backup battery if accessible (most modern controllers use a CR2032 or similar coin cell). Recurrent clock loss after each thunderstorm is a sign of a degraded battery or a controller whose surge-protection circuit is faulted.

Branch three, program and budget. The controller's seasonal adjust (often called Water Budget) at 0 percent zeros out the schedule but does not affect manual operation. A homeowner who dialed down for winter and forgot to dial back up will see exactly this symptom. Same with a smart-controller "Skip if rain expected" set to a low threshold that triggers on any forecast above 10 percent probability. Read every program assignment and every seasonal adjust value.

Branch four, sensor input not from a rain sensor. Some controllers accept a soil-moisture sensor or a flow sensor input in the same terminal. A soil-moisture sensor in saturated soil will hold the controller in skip indefinitely until the soil dries. A flow sensor reading an over-limit (suggesting a broken pipe) will lock the controller into a fault state. Confirm what is wired to the sensor input.

Branch five, wireless connectivity. Cloud-based smart controllers that have lost Wi-Fi may default to a backup local schedule, no schedule, or a generic schedule depending on the manufacturer. A controller that "used to work fine until we changed routers" is a connectivity issue, not an irrigation issue. Reconnect the controller to the new network and verify the schedule pushes from the cloud.

Confirming diagnosis

The diagnosis is confirmed when the corrective action produces a normal run on the next scheduled cycle. For rain-sensor replacements, verify the new sensor reads dry on the controller display. For clock corrections, verify the time stays set after a deliberate power-cycle test (kill the breaker for 60 seconds, then restore). For program corrections, verify the seasonal adjust value and the program assignments are saved.

Some controllers maintain a multi-week history accessible by mobile app or front-panel scroll. Pull and attach to the work order. The history is the customer-facing proof; it is much more convincing than a verbal explanation.

Remediation

Replace failed rain sensors with a comparable model and confirm wiring polarity at the terminal. Most disc-style outdoor sensors run 10 to 15 years before disc failure or wire degradation; replacement is a routine maintenance item, not an emergency.

Replace backup batteries on controllers that lost time after a power event. Document the replacement date. A controller older than 12 to 15 years that has lost its surge-protection capability is a candidate for full replacement; intermittent operation will continue otherwise.

Reset seasonal-adjust and budget settings to a season-appropriate baseline. Leave a printed schedule card at the controller. Educate the customer on the difference between Manual (always works) and the scheduled cycle (governed by program logic, sensors, and budget).

For Wi-Fi-connected smart controllers, document the network configuration on the work order so the next visit can re-establish without the customer's help.

References

• US EPA WaterSense Specification for Weather-Based Irrigation Controllers
• ASABE/ICC 802-2014 Landscape Irrigation Sprinkler and Emitter Standard
• California Department of Water Resources, Model Water Efficient Landscape Ordinance (MWELO)
• Irrigation Association, Smart Water Application Technologies (SWAT) protocols
• Texas A and M AgriLife Extension, EL-5380, "Watering Established Lawns"