Symptoms
Smart Smoke Detector Sounds Locally but Test Alerts Never Reach the Phone. This symptom affects a particular operation; a related feature may still behave normally.
To capture the distinction, begin with this observation: Run a built-in test according to detector instructions and note local alarm and phone notification separately. Note whether the failure follows a specific file, account, input, session or device.
Why It Happens
Three different mechanisms can lead to a similar visible symptom. Use a comparison before deciding which applies:
- A local sensor or actuator works, but the hub or phone state is stale.
- An automation, time schedule or permission uses a different sensor/code/event type.
- Placement, interference or hardware calibration changes the physical reading.
Use the diagnostic comparisons below to distinguish these possibilities before choosing a correction.
Before Making Changes
Never disable, dismantle or relocate a smoke detector to test phone alerts. A lock, detector, heater or garage door is safety equipment; never bypass mechanical or emergency protections. Use a disposable test item if the operation can send notifications or alter shared data.
Write down each original setting so you can reverse the change; do not risk the sole remaining copy of a file or account record.
Problem-Specific Diagnosis
The useful question is which layer makes the same action behave differently. Observe the physical device and its event history separately from what the phone app displays. These observations guide testing; they are not a diagnosis until verified.
| What you observe | What it suggests | Next comparison |
|---|---|---|
| One path succeeds and the original path fails | Physical success but stale app tile points to status reporting or hub connectivity. | Compare phone notification settings and hub connection using safe manufacturer test mode. |
| The result changes when account, source or device changes | Correct event recorded without push alert suggests notification or service eligibility. | Run a built-in test according to detector instructions and note local alarm and phone notification separately. |
| Both the original and control fail consistently | Local control failing as well suggests hardware, alignment or safety state. | Inspect detector model cloud-alert support, gateway subscription and push delivery; consult fire safety requirements. |
Step-by-Step Troubleshooting
Start with the Beginner tab for reversible checks. Choose Advanced only when the comparison points to a specific setting or integration.
Capture the symptom without changing data
Run a built-in test according to detector instructions and note local alarm and phone notification separately. Note the device or app, affected item, time, and visible state. This baseline will let you tell a genuine fix from a temporary refresh.
Check the safest relevant setting
Verify the safety alert type is enabled in the companion app and correct household users are selected. Make only that one small change, then repeat the original action once before adjusting anything else.
Compare an independent path
Compare phone notification settings and hub connection using safe manufacturer test mode. Keep other variables steady. If the alternate path works, focus on the layer that differs; if both fail, investigate shared dependencies.
Confirm the everyday workflow
Authorized test alert arrives while local alarm remains functional. Repeat the check from a fresh session if practical. Restore the original setting if this change did not improve the result.
Identify the failing boundary
Inspect detector model cloud-alert support, gateway subscription and push delivery; consult fire safety requirements. Record the result and the original configuration so it can be restored; do not infer a cause without a comparison.
Separate client, account and device layers
Observe the physical device and its event history separately from what the phone app displays. Determine whether the mismatch follows the content, account, hardware path or application before choosing a targeted correction.
Apply one narrow correction
Based on the evidence, adjust only the affected rule, profile, input, route or supported feature setting. Verify the safety alert type is enabled in the companion app and correct household users are selected. If a change is unavailable for this model or account, stop rather than forcing it.
Prove the fix and document rollback
Authorized test alert arrives while local alarm remains functional. Test the original failing path and the control path. Reverse the last change if it introduces another fault; preserve screenshots of the working state.
Solution Checklist
Common Mistakes to Avoid
Do not silence life-safety alarms, defeat garage reversal sensors, disable access logging or experiment without alternate entry. For this specific scenario: Never disable, dismantle or relocate a smoke detector to test phone alerts. Changing more than one setting at once makes it harder to identify the actual cause.
How to Verify the Fix
Authorized test alert arrives while local alarm remains functional. Repeat the original action in a fresh session rather than assuming that one successful preview proves the repair. Confirm the control path still works.
- Reproduce the fault with the original input before making a change.
- Rerun the comparison: Compare phone notification settings and hub connection using safe manufacturer test mode.
- Verify that the successful result persists after reopening the affected app or reconnecting the device.
- If other functionality regresses, restore the recorded previous settings.
If the Problem Continues
If the test still fails, preserve the baseline and the comparison results. Inspect detector model cloud-alert support, gateway subscription and push delivery; consult fire safety requirements. Share the exact device model, app version, relevant screenshots without private information, and the smallest reproduction with official product support or the account administrator. If the fault is hardware-related or safety-critical, use authorized service instead of bypassing protection.
Prevent Recurrence
Recheck alerts, battery and sensor alignment regularly; document automations and retain emergency manual control. Document the final working setting and the test that demonstrated success. After an app, device, router or account change, check a small example again before relying on the workflow.
FAQ
Does this mean the entire device or service has failed?
Not necessarily. A local sensor or actuator works, but the hub or phone state is stale. Compare a known-good path before assuming a widespread fault.
What should I test before resetting anything?
Run a built-in test according to detector instructions and note local alarm and phone notification separately. Observe the physical device and its event history separately from what the phone app displays. This is more informative than a full reset.
How can I tell whether the problem is solved?
Authorized test alert arrives while local alarm remains functional. Verify the result again after reconnecting or restarting the relevant app or device.