Symptoms
The controller waters even when the current moisture reading is above the configured limit.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: The controller waters even when the current moisture reading is above the configured limit.
- Comparison to run: Compare raw sensor units, latest timestamp and rule threshold.
- Pass condition: An above-threshold test suppresses watering while a dry test allows a safe short cycle.
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:
- Rule checks stale reading — investigate this first only if the local state or controlled comparison supports it.
- Percent and raw-value scales mismatch — a second layer that may survive a simple restart and requires a targeted check.
- Override schedule ignores moisture condition — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Do not disable flood/leak protection or run irrigation during freezing conditions. 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 raw sensor units, latest timestamp and rule threshold. 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 raw sensor units, latest timestamp and rule threshold. | 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 | Identify which rule started the watering cycle in history. | This can expose or rule out rule checks stale reading without changing several settings together. |
| Inspect the deeper layer | Test notification-only rule with the same condition before valve control. | Use the evidence to separate percent and raw-value scales mismatch from override schedule ignores moisture condition; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether percent and raw-value scales mismatch is consistent with the evidence. If not, investigate override schedule ignores moisture condition rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. The controller waters even when the current moisture reading is above the configured limit. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Compare raw sensor units, latest timestamp and rule threshold. Do not erase logs or reset the device yet. Identify which rule started the watering cycle in history. 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. Check sensor last update and correct moisture threshold units. 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. An above-threshold test suppresses watering while a dry test allows a safe short cycle. 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 rule checks stale reading, percent and raw-value scales mismatch and override schedule ignores moisture condition separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Compare raw sensor units, latest timestamp and rule threshold. Test notification-only rule with the same condition before valve control. 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. Inspect overrides, manual runs and rule precedence on the controller. 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. An above-threshold test suppresses watering while a dry test allows a safe short cycle. 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 rule checks stale reading as certain before running the comparison: Compare raw sensor units, latest timestamp and rule threshold.
- Trying several changes at once, such as modifying percent and raw-value scales mismatch and override schedule ignores moisture condition simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Do not disable flood/leak protection or run irrigation during freezing conditions.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
An above-threshold test suppresses watering while a dry test allows a safe short cycle.
- Repeat the original failing action under equivalent conditions: The controller waters even when the current moisture reading is above the configured limit.
- Run the control again: Compare raw sensor units, latest timestamp and rule threshold.
- Check the positive pass condition: An above-threshold test suppresses watering while a dry test allows a safe short cycle.
- 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: Test notification-only rule with the same condition before valve control. Inspect overrides, manual runs and rule precedence on the controller.
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 raw sensor units, latest timestamp and rule threshold.
- Preserve the corrected behavior: An above-threshold test suppresses watering while a dry test allows a safe short cycle.
- Preserve hub backups and automation screenshots; test critical automations after hub, battery or time-zone changes.
- Review configuration or hardware changes that could reintroduce rule checks stale reading.
Frequently Asked Questions
Does this symptom prove rule checks stale reading?
No. Start with the controlled comparison: Compare raw sensor units, latest timestamp and rule threshold. Only treat rule checks stale reading 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: Test notification-only rule with the same condition before valve control. That helps determine whether percent and raw-value scales mismatch or override schedule ignores moisture condition fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: An above-threshold test suppresses watering while a dry test allows a safe short cycle. Keep a record of the working state for future troubleshooting.