Symptoms
A leak detector stays in alarm after the water is removed and dried.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: A leak detector stays in alarm after the water is removed and dried.
- Comparison to run: Inspect the sensor contacts and compare the physical alarm with the app state.
- Pass condition: A controlled damp-cloth test triggers and later clears the alarm.
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:
- Moisture remains between contacts — investigate this first only if the local state or controlled comparison supports it.
- State has not synchronized with hub — a second layer that may survive a simple restart and requires a targeted check.
- Probe corrosion creates conductive path — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Keep leak protection active; never defeat alarms to hide a persistent alert. 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: Inspect the sensor contacts and compare the physical alarm with the app state. 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 | Inspect the sensor contacts and compare the physical alarm with the app state. | 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 | Dry the sensing area according to the manufacturer's instructions. | This can expose or rule out moisture remains between contacts without changing several settings together. |
| Inspect the deeper layer | Compare sensor status directly at its hub and in an automation dashboard. | Use the evidence to separate state has not synchronized with hub from probe corrosion creates conductive path; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether state has not synchronized with hub is consistent with the evidence. If not, investigate probe corrosion creates conductive path rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. A leak detector stays in alarm after the water is removed and dried. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Inspect the sensor contacts and compare the physical alarm with the app state. Do not erase logs or reset the device yet. Dry the sensing area according to the manufacturer's instructions. 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 whether the device requires a manual alarm acknowledgement. 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. A controlled damp-cloth test triggers and later clears the alarm. 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 moisture remains between contacts, state has not synchronized with hub and probe corrosion creates conductive path separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Inspect the sensor contacts and compare the physical alarm with the app state. Compare sensor status directly at its hub and in an automation dashboard. 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 for corrosion or damaged leads and replace the sensor if the self-test fails. 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. A controlled damp-cloth test triggers and later clears the alarm. 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 moisture remains between contacts as certain before running the comparison: Inspect the sensor contacts and compare the physical alarm with the app state.
- Trying several changes at once, such as modifying state has not synchronized with hub and probe corrosion creates conductive path simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Keep leak protection active; never defeat alarms to hide a persistent alert.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
A controlled damp-cloth test triggers and later clears the alarm.
- Repeat the original failing action under equivalent conditions: A leak detector stays in alarm after the water is removed and dried.
- Run the control again: Inspect the sensor contacts and compare the physical alarm with the app state.
- Check the positive pass condition: A controlled damp-cloth test triggers and later clears the alarm.
- 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: Compare sensor status directly at its hub and in an automation dashboard. Inspect for corrosion or damaged leads and replace the sensor if the self-test fails.
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: Inspect the sensor contacts and compare the physical alarm with the app state.
- Preserve the corrected behavior: A controlled damp-cloth test triggers and later clears the alarm.
- Preserve hub backups and automation screenshots; test critical automations after hub, battery or time-zone changes.
- Review configuration or hardware changes that could reintroduce moisture remains between contacts.
Frequently Asked Questions
Does this symptom prove moisture remains between contacts?
No. Start with the controlled comparison: Inspect the sensor contacts and compare the physical alarm with the app state. Only treat moisture remains between contacts 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: Compare sensor status directly at its hub and in an automation dashboard. That helps determine whether state has not synchronized with hub or probe corrosion creates conductive path fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: A controlled damp-cloth test triggers and later clears the alarm. Keep a record of the working state for future troubleshooting.