Symptoms
Irrigation remains paused long after the configured rain-delay period.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: Irrigation remains paused long after the configured rain-delay period.
- Comparison to run: Compare delay end time, weather feed timestamp and controller local clock.
- Pass condition: Delay expires as configured and a permitted short cycle starts.
Why It Happens
A raw event is not the same thing as an automation action. Timing, state mapping, hub subscriptions and the physical device must be checked separately.
Treat these as competing hypotheses, not confirmed diagnoses. Their implications are different:
- Delay timer was extended manually — investigate this first only if the local state or controlled comparison supports it.
- Weather-based rule repeatedly resets delay — a second layer that may survive a simple restart and requires a targeted check.
- Controller clock or time zone is wrong — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Avoid bypassing rain or freeze protection during unsuitable weather. A smart-home event can be detected correctly by a sensor but then delayed or misread by the hub, bridge, cloud integration or automation rule. Separate raw sensor state from the action triggered by that state. Write down the working configuration and, if available, export settings or create a test-only copy before changing account permissions, routes or file locations.
Make one change at a time, note the original value, and repeat the exact same test after each change. If the new outcome is worse, restore that single setting; a full reset would erase evidence and can create additional problems.
Problem-Specific Diagnosis
Begin with this controlled observation: Compare delay end time, weather feed timestamp and controller local clock. Record the result and time; a vague report such as “sometimes fails” cannot distinguish the three hypotheses.
| Check | What to do | What the result tells you |
|---|---|---|
| Compare a working path | Compare delay end time, weather feed timestamp and controller local clock. | If one controlled route works, the failed route is probably specific to a setting, permission, device, or service rather than a total outage. |
| Check the local state | Check the exact rain-delay end date in the controller. | This can expose or rule out delay timer was extended manually without changing several settings together. |
| Inspect the deeper layer | Inspect rule event history for recurring delay activations. | Use the evidence to separate weather-based rule repeatedly resets delay from controller clock or time zone is wrong; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether weather-based rule repeatedly resets delay is consistent with the evidence. If not, investigate controller clock or time zone is wrong rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. Irrigation remains paused long after the configured rain-delay period. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Compare delay end time, weather feed timestamp and controller local clock. Do not erase logs or reset the device yet. Check the exact rain-delay end date in the controller. Confirm the relevant account, cable, selected output, permission or status before saving changes. If it is already correct, leave it alone and proceed; do not force a change just to try something. Verify weather provider data and local sensor condition. Change only this one condition after recording the old value. If it does not improve the result, restore the former value rather than layering additional guesses on top. Delay expires as configured and a permitted short cycle starts. Repeat the same comparison used in step one. Record what improved, what remains unchanged and whether a reconnect or normal app restart changes the result. Stop here if the expected outcome is stable. Consider delay timer was extended manually, weather-based rule repeatedly resets delay and controller clock or time zone is wrong separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Compare delay end time, weather feed timestamp and controller local clock. Inspect rule event history for recurring delay activations. Focus on logs, state, permissions, protocol negotiation or version support relevant to this failure. Do not collect or share credentials, account tokens or unrelated private content. Temporarily test one low-water cycle under safe conditions without removing weather safety checks. Use an isolated or test-only configuration where possible. Keep an explicit rollback path; do not weaken security, replace backup originals or bypass equipment protection to make one test pass. Delay expires as configured and a permitted short cycle starts. Observe the behavior through the original trigger again. If the change does not produce this measurable result, undo that change and escalate with the recorded facts, rather than repeating disruptive reset attempts.Step-by-Step Troubleshooting
Capture the failing state
Check the first reversible condition
Apply the lowest-risk targeted fix
Retest and document
Distinguish the competing root causes
Inspect the deeper system layer
Run a second independent isolation test
Validate stability and rollback readiness
Solution Checklist
Common Mistakes to Avoid
- Treating delay timer was extended manually as certain before running the comparison: Compare delay end time, weather feed timestamp and controller local clock.
- Trying several changes at once, such as modifying weather-based rule repeatedly resets delay and controller clock or time zone is wrong simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Avoid bypassing rain or freeze protection during unsuitable weather.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
Delay expires as configured and a permitted short cycle starts.
- Repeat the original failing action under equivalent conditions: Irrigation remains paused long after the configured rain-delay period.
- Run the control again: Compare delay end time, weather feed timestamp and controller local clock.
- Check the positive pass condition: Delay expires as configured and a permitted short cycle starts.
- Recheck after a normal restart, reconnection or scheduled cycle only when it is safe and relevant.
A single passing attempt is useful but may conceal intermittent failures. Record whether the fix survives the triggering condition without requiring a daily workaround.
If the Problem Continues
Use the deeper comparison rather than repeating the first steps: Inspect rule event history for recurring delay activations. Temporarily test one low-water cycle under safe conditions without removing weather safety checks.
Give vendor support sanitized event times, hub model, raw-state transitions and firmware details; treat safety and access-control devices as safety equipment, not debugging toys.
If the issue affects money, alarms, shared business records, or protective power equipment, stop risky experiments and use the official administrator, provider or manufacturer channel.
Prevent Recurrence
- Keep a record of the previously failing condition: Compare delay end time, weather feed timestamp and controller local clock.
- Preserve the corrected behavior: Delay expires as configured and a permitted short cycle starts.
- Preserve hub backups and automation screenshots; test critical automations after hub, battery or time-zone changes.
- Review configuration or hardware changes that could reintroduce delay timer was extended manually.
Frequently Asked Questions
Does this symptom prove delay timer was extended manually?
No. Start with the controlled comparison: Compare delay end time, weather feed timestamp and controller local clock. Only treat delay timer was extended manually as a candidate until the evidence supports it.
What if the first two checks do not change anything?
Move to a different layer rather than repeating the same action: Inspect rule event history for recurring delay activations. That helps determine whether weather-based rule repeatedly resets delay or controller clock or time zone is wrong fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: Delay expires as configured and a permitted short cycle starts. Keep a record of the working state for future troubleshooting.