Sprinkler Controller Troubleshooting
Separate a controller problem from a field problem before you replace anything.
Use this hub to troubleshoot residential irrigation timers and smart controllers by symptom. Start with power, scheduling, zone behavior, wiring, sensors, or connectivity, then move to the guide that matches what you can actually observe.
What is the controller actually doing?
Begin with the visible symptom. A dead display, missed schedule, dry zone, and offline app can point to very different troubleshooting paths.
Controller has no power
The display is blank, the unit will not start, or the controller appears completely dead.
Controller says running, no water
The controller indicates an active zone, but the sprinklers or drip line stay dry.
Schedule does not run
Manual watering works, but the programmed schedule is skipped, delayed, or starts at the wrong time.
One zone will not run
Other zones work, but one station stays off or behaves differently from the rest.
Smart controller is offline
The app cannot reach the controller, Wi-Fi is disconnected, or cloud features are unavailable.
Several zones act incorrectly
Multiple stations skip, run together, stop unexpectedly, or show a pattern that is not isolated to one valve.
Follow the signal path instead of guessing the controller.
Start with the simplest observable difference, then move from settings and power toward wiring and field components only when the evidence points there.
Browse by controller component or function.
Use these paths after the symptom has narrowed the problem to power, programming, wiring, sensors, or connectivity.
Controller troubleshooting guides.
Each page should solve a distinct problem. Search-intent variants that do not need a separate diagnosis should strengthen an existing guide instead of creating a duplicate page.
Controller Says Running but No Water Comes Out
Trace one zone from controller output through wiring, solenoid, valve, and water supply.
Sprinkler Controller Has No Power
Work from the supply side toward the controller using model-specific power information.
Sprinkler Schedule Is Not Running
Separate programming, delays, sensor state, and controller settings from field faults.
One Sprinkler Zone Is Not Working
Compare the failed station with working zones to narrow controller, wiring, and valve causes.
Rain Sensor Keeps Sprinklers Off
Check sensor state, bypass behavior, wiring, and controller interpretation before replacing the sensor.
Smart Sprinkler Controller Is Offline
Separate Wi-Fi and account connectivity from local controller operation and irrigation hardware.
Use a brand page when the controller model changes the diagnosis.
Brand pages should add model-specific controls, menus, terminal layouts, error states, or documentation. They should not repeat generic troubleshooting just to create another URL.
How controller content should be reviewed.
Terminal labels, reset procedures, sensor behavior, and electrical specifications should come from current documentation for the relevant controller family.
Unsupported technical claims, unsafe wiring advice, duplicate intent, and misleading diagnostic certainty block publication.
Controller guides should connect naturally to wiring, valve, sensor, pressure, or brand pages when the next diagnostic step moves outside the controller.