Rachio's running state confirms a command, not actual flow. If all zones fail, check the irrigation supply, common wire, master valve, pump, and any sensor wired into the common path. If one zone fails, focus on its output, wire, splice, solenoid, and valve. Manually opening one valve is the decisive first test.
Prove whether the missing event is command, electricity, or flow
Run one affected and one unrelated zone locally when possible. Then manually open one known valve to separate shared hydraulics from electrical control.
| Quick Run result | Strongest clue | Next test |
|---|---|---|
| One zone dry; others water | Local station circuit or valve | Terminal, conductor, splice, solenoid, manual valve |
| Every zone counts down but stays dry | Shared field or supply boundary | Water shutoff, common, master valve, pump, inline sensor |
| Manual valve produces normal flow | Supply and valve hydraulics are available | Zone-to-C voltage at controller and valve |
| App and local control behave the same | Wi-Fi/app path is not the blocker | Continue at controller terminals and field hardware |
Use this boundary: A Rachio run state is a command record, not a flow sensor reading. Confirm physical water at the heads before calling the run successful.
Match the pattern before opening anything
| Possible cause | Best clue | First check |
|---|---|---|
| Irrigation supply off | No valve opens manually | Verify the dedicated shutoff |
| Common wire or inline sensor open | Every zone fails electrically | Inspect shared common path |
| Master valve or pump configuration | All stations show running but stay dry | Review master-valve setup |
| Local station fault | Only one zone fails | Test terminal, wire, splice, and solenoid |
Read the system before replacing a part
Use the observation that most closely matches your yard. Each row changes the next test, so you do not spend an afternoon proving the wrong theory.
What it meansShared supply, common wire, master valve, pump relay, or M-terminal configuration is likely.
Do nextCheck common and master hardware before individual valves.
What it meansThat zone wire, splice, solenoid, valve, or lateral is the boundary.
Do nextCompare with a working zone and manually open the valve.
What it meansRachio may have protected the output from an electrical problem.
Do nextResolve the fault before hydraulic diagnosis.
What it meansWater supply and valve hydraulics can work.
Do nextTrace the station-to-common command path.
Four tests that narrow the fault
Stop as soon as one result gives you a clear boundary. The goal is not to perform every test; it is to eliminate whole groups of causes safely.
- 01
Count failed zones
Run two unrelated zones with Quick Run and record whether each valve responds.
IF YES / NORMALOne failure stays local.
IF NO / ABNORMALGrouped failure moves to common, supply, M terminal, master valve, or pump.
- 02
Check fault and M-terminal state
Record any zone fault and verify whether a master valve or pump is configured and wired to the correct generation-specific M terminal.
IF YES / NORMALNo protective fault or missing master command explains the run.
IF NO / ABNORMALCorrect the electrical/configuration fault first.
- 03
Open one valve manually
Use the exact valve's approved bleed procedure with the irrigation supply available.
IF YES / NORMALNormal spray proves the hydraulic path.
IF NO / ABNORMALMove upstream to shutoff, master valve, pump, or water supply.
- 04
Compare voltage at controller and valve
A trained person measures station-to-common during the app's active run.
IF YES / NORMALCommand at the valve raises solenoid or valve mechanics.
IF NO / ABNORMALCommand lost in the field identifies wire or splice.
Common fixes that waste time
It reports software state, not voltage at the valve or water movement.
All-zone symptoms usually involve something shared.
Incorrect master-valve or pump configuration can create new behavior and safety issues.
How the evidence changes the repair
Rachio showed Quick Run for every zone, but none produced water after controller replacement.
- No zone faults appeared.
- Individual valves opened manually with normal water.
- The property used a master valve, but the M terminal had not been enabled in the new controller configuration.
The app, field valves, and water path each passed different tests. Restoring the documented master-valve configuration completed the shared command path.
How to confirm the repair actually held
A single successful start can hide an intermittent splice, sticky valve, remaining leak, or scheduling problem. Recreate the original conditions before calling the job finished.
Pass: The original symptom stays absent during the direct test.
If not: Repeat the last isolation step; the fault is incomplete or intermittent.
Pass: Automatic behavior and recorded status now match physical watering.
If not: A schedule, sensor, smart feature, master command, or cloud-state issue remains.
Pass: The correction holds under normal time, moisture, load, and network conditions.
If not: Use the first changed condition to locate the remaining intermittent boundary.
Recognize the controller state
Original diagnostic reconstruction. Not a photograph of the product and not copied from a competitor.
Check these in order
- 01
Test two zones with Quick Run
One failed zone suggests a local circuit. Two unrelated failed zones point toward shared water, common, master-valve, pump, or controller supply causes.
- 02
Try local controller control
Start a zone from the physical controller when supported. If app and local commands behave the same, Wi-Fi and the phone are no longer the main suspects.
- 03
Open one valve manually
Use the valve's approved manual method. Water flow proves the supply and hydraulic valve path; no flow means solve supply, flow control, pump, or master-valve issues before electrical testing.
- 04
Inspect shared common and sensor paths
A rain sensor wired inline with common can interrupt every solenoid without creating an obvious app warning. Check controller common terminals and shared waterproof splices with power off.
- 05
Measure from controller to valve
During a Quick Run, compare zone-to-common voltage at the controller and at the valve. Voltage that disappears along the route indicates field wiring; voltage at the valve with no opening indicates solenoid or valve trouble.
- A pump, relay, master valve, or backflow assembly is involved.
- An inline sensor or underground common-wire break is suspected.
- Correct voltage is present but the controller or several valves behave inconsistently.
What homeowners ask about this symptom
Can a rain sensor stop all Rachio zones without an app warning?
Yes, especially if an older sensor is wired inline with the common conductor instead of directly to the controller's sensor input.
Why does manually opening a valve matter?
It bypasses the controller and field electrical circuit. The result immediately tells you whether to investigate water and valve hydraulics or electrical control.
Sources and review notes
General maintenance logic is checked against EPA WaterSense outdoor irrigation guidance. Product controls and disassembly steps vary by model; use the current manufacturer manual for your exact valve, controller, or sprinkler head.
Published and last reviewed: September 14, 2026