The most common cause is an extra start time. One start time begins the entire program; it is not a separate start time for each station. Check every start-time slot in every active program before resetting the controller.
Match the pattern before opening anything
| Possible cause | Best clue | First check |
|---|---|---|
| Extra start time | All stations repeat in the same order | Inspect every start slot in Program A |
| Second active program | Only some stations repeat | Review Programs B–D |
| Overlapping long programs | Second cycle begins as the first ends | Add all station run times |
| Cycle and soak | One station pauses and resumes in segments | Check advanced watering settings |
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 meansAn additional program start time is the leading explanation.
Do nextInspect every start slot in each active program.
What it meansThose stations may have runtimes in a second program.
Do nextCompare station assignments across Programs A–D.
What it meansAn overlapping start may have been stacked until the program finished.
Do nextAdd every runtime and compare total duration with start times.
What it meansCycle-and-soak may be intentional rather than duplication.
Do nextCheck advanced watering and total planned runtime.
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
Record every enabled start
Photograph all start-time slots in Programs A, B, C, and D before editing.
IF YES / NORMALOnly intended program starts remain.
IF NO / ABNORMALEach extra start can launch the entire program again.
- 02
Map which stations repeat
Write the actual second-run sequence rather than relying on memory.
IF YES / NORMALA full repeat points to a start; a subset points to another program.
IF NO / ABNORMALIrregular behavior needs history and controller-state observation.
- 03
Calculate program stacking
Add all station runtimes and any soak delays to the first start time.
IF YES / NORMALLater starts lie outside the active window.
IF NO / ABNORMALA start inside that window may wait and appear as an immediate restart.
- 04
Observe one simplified day
Leave one documented start in the intended program and monitor the next permitted cycle.
IF YES / NORMALThe sequence runs once.
IF NO / ABNORMALInspect another active program or connected smart schedule before resetting.
Numbers worth measuring
This calculation explains many supposedly random immediate restarts.
Common fixes that waste time
A start time launches the whole program; its number is not a station number.
It removes the schedule evidence that reveals the duplicate.
Short repeated segments can be an intentional runoff-control strategy.
How the evidence changes the repair
A six-station ESP-ME3 finished at 6:08 a.m. and immediately began again.
- The first start was 5:00 a.m. and total programmed runtime was 68 minutes.
- A second Program A start remained enabled at 5:30 a.m.
- The overlapping command was stacked until the active sequence ended.
The 6:08 restart was mathematically predictable. Removing the extra 5:30 start fixed the repeat without changing station runtimes or hardware.
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 does not return during the direct test.
If not: Stop and repeat the last dividing test; the fault boundary was incomplete or intermittent.
Pass: Automatic behavior now matches the documented controller state.
If not: Hardware may be repaired while schedule, sensor, program, or connectivity logic remains separate.
Pass: The repair holds under normal time, load, moisture, and network conditions.
If not: Use the first changed condition to identify the remaining intermittent cause.
Recognize the controller state
Original diagnostic reconstruction. Not a photograph of the product and not copied from a competitor.
Check these in order
- 01
Identify what repeats
Write down whether every station repeats, only a subset repeats, or one station pauses and resumes. Those three patterns point to extra start times, another program, or cycle-and-soak behavior.
- 02
Photograph the current schedule
Capture watering days, run times, and all start-time screens before editing. This prevents a quick fix from turning into a mystery later.
- 03
Keep one start time per intended program
A start time launches all stations assigned to that program in sequence. Turn unintended start slots to OFF rather than assigning a different start time to each station.
- 04
Inspect every active program
Programs B, C, and D can hold their own start times and station run times. A station assigned to two programs can run twice even when Program A looks correct.
- 05
Calculate overlap before blaming hardware
Add the run times for the program, including repeated soak cycles. If another start begins before the first sequence finishes, the controller may stack watering and appear to restart immediately.
- Water continues after the dial is turned to OFF.
- A station runs with no program shown active.
- Controller behavior remains inconsistent after documenting and simplifying all programs.
What homeowners ask about this symptom
Does each ESP-ME3 station need its own start time?
No. A program start time begins the program, and its stations run sequentially using their individual run times.
Why does only one zone run twice?
That zone may have a run time in two programs, or cycle-and-soak may intentionally split its watering into segments.
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: August 30, 2026