Controller
Model, app/controller online status, affected zone, and any error text.
Use this flow when a controller is powered or online but one sprinkler zone does not water. It separates schedule and sensor checks from zone-specific physical faults.
The controller appears powered or online, but one zone will not run. The first split is whether the failure is schedule/sensor related, affects every zone, or is isolated to one zone.
Model, app/controller online status, affected zone, and any error text.
Whether other zones run and whether the affected zone opens, flows weakly, or stays dry.
Schedule, sensor, water supply, landscaping, firmware, wiring, or weather changes.
The clock, program, seasonal adjustment, or a rain/freeze sensor prevented the run.
A valve, solenoid, field wire, or valve box issue affects one zone.
The water source, pump, pressure, or plumbing serving the zone is unavailable.
The controller or app is offline or showing stale state.
Record the model, affected zone, errors, and whether other zones run.
Verify clock, program, seasonal adjustment, and sensor state. Do not bypass safety controls.
If safe, run the zone manually and watch the valve box, water flow, leaks, and pressure.
Stop and prepare a technician handoff for wiring, electrical, pump, valve, plumbing, leak, or pressure work.
Does manual activation fail for only one zone, or do all zones fail?
Escalate when safe checks do not restore the zone or the evidence points to model-specific wiring, electrical, pump, valve, plumbing, leak, or unsafe-pressure work.
This vendor-neutral flow was checked against Rain Bird and Hunter controller troubleshooting material. Product-specific instructions still take precedence for the installed model.
Use private discovery to record the controller, zone, evidence, and handoff without placing account secrets in public chat.
Open private discoveryThe support assistant can ask the next question and create a technician-ready handoff when the issue crosses into physical work.
Open support chat