Controller Runs Zones Twice After Rain Sensor Install Decision Tree

Why this matters

When a controller starts double-watering zones right after a rain sensor is added, the customer sees soggy turf and a high water bill and blames the new sensor, but the sensor itself rarely causes double runs. Adding the sensor almost always coincided with the installer entering the program menu, and that is where the real cause hides: an accidental second program, a duplicated start time, or a wiring mistake. Double-application drowns roots (the wet-soil wilt problem), wastes water against conservation rules, and is a guaranteed callback. Sorting whether the sensor wiring, a program change, or a controller fault is responsible gets the run schedule right and clears the sensor of blame, or correctly condemns a miswired sensor circuit.

Symptom presentation

• Zones water two cycles in one day, or the whole program repeats back-to-back.
• Started immediately after the rain-sensor install visit.
• Soggy turf, runoff, and elevated water use even on dry days (so it is not the sensor failing to stop watering in rain; it is over-scheduling).

Quick checks

1. Read every program and start time. Most controllers run multiple programs (A/B/C) and multiple start times per program. Walk the menu: a single program with two start times, or two programs each with one start time on the same zones, both produce a double run. The installer likely created or duplicated one while in the menu.
2. Confirm how the rain sensor is wired. Two methods: across the dedicated SEN/sensor terminals (controller-aware), or in series interrupting the common/MV. A sensor wired to the wrong terminals, or with the SEN jumper left in place while also wired in series, can leave the bypass behavior wrong, but that affects rain shutoff, not extra runs. Verify it is on the correct terminals and the factory jumper is removed if the sensor uses the SEN terminals.
3. Check the rain-sensor bypass switch. If set to BYPASS, the sensor is ignored; that explains watering in rain but not a double run on dry days.
4. Verify the seasonal/water-budget percent and any cycle-and-soak setting were not changed to values that effectively repeat irrigation.

Isolation tree

Branch on the program audit.

• Two start times on the same program, same zones -> classic accidental double start. The installer added a start time, or one already existed and the schedule now stacks. Confirm: two start times listed; the second run begins right after the first completes (or at a second clock time). Delete the redundant start time. Most common cause.
• A second program (B or C) duplicating the zones of program A -> two programs irrigate the same zones. Confirm: program B/C has run times entered for the same stations. Clear the duplicate program.
• Program stacking from overlapping start times -> if two start times are set close together and the first program has not finished, many controllers queue (stack) the second rather than run concurrently, producing what looks like a continuous double run. Confirm by run-time math against the start interval. Space or remove start times.
• Rain-sensor wiring error causing a constant-on or short -> if the sensor leads were landed on a station or common terminal incorrectly, a zone can energize unexpectedly. Confirm by inspecting terminal landings against the controller manual; correct miswires. This is the only branch where the sensor circuit is truly at fault, and it usually shows as a stuck-on zone, not a clean double cycle.
• Cycle-and-soak misconfigured -> a cycle-and-soak setting splits a zone into multiple short runs with soak intervals; if newly enabled, it can look like double-running. Confirm in the advanced menu. Adjust to intended values.
• Controller fault / power event -> rare; a brownout or controller glitch during the install reset the schedule to a default that double-runs. Confirm by full schedule review and, if needed, a clean reprogram.

Confirming diagnosis

Put the controller in manual/test and watch the program list run. Document every program, every start time, and every station run time on paper. The double run will trace to a specific redundant start time, a duplicate program, or a stacking interval, and removing exactly that entry eliminates the second cycle. For the wiring branch, verify sensor leads on the SEN terminals (jumper removed) or correctly in series on the common, per the controller and sensor manuals; a meter across the sensor confirms open (dry, watering allowed) versus closed/normally-closed behavior as designed.

Remediation

• Delete the redundant start time or clear the duplicate program so each zone runs once per scheduled day.
• Re-land any miswired sensor leads on the correct terminals; remove the factory jumper when using the SEN terminals; confirm the bypass switch is in the active (not bypass) position so the sensor actually inhibits watering when wet.
• Reset seasonal/water-budget percent, cycle-and-soak, and start intervals to intended values.
• Re-verify the rain sensor functions: trip it (or squeeze the disc/press the test) and confirm the controller shows sensor-active and skips the cycle.
• Reprogram from scratch if the schedule is tangled; document the final program for the customer.

References

• Hunter Industries, residential controller owner's manuals (Pro-C, X-Core, X2) for program/start-time and rain-sensor (jumper/SEN terminal) wiring.
• Rain Bird, ESP-TM2 / ESP-Me controller manuals (rain-sensor terminals and program structure).
• Irrigation Association, "Rain Sensor Installation and Maintenance" best-practice guidance.
• Toro / manufacturer rain-sensor (wireless and wired) installation instructions for terminal landing and bypass operation.