Camera streams live video but no stored events appear. A partial failure matters: one capability still functions, while a closely related step does not. This guide focuses on isolating that difference in smart home devices, not on indiscriminate resets. Use the known-good behavior as your control, change one variable at a time, and retest the original scenario after each intervention.
Start with a two-device or two-mode comparison
Baseline test: Trigger one harmless motion event while watching notification. Record the current device model, OS or firmware version, and whether this occurs with one file, account, network or source. A reproducible contrast is more informative than a vague message such as “not working.” If the control fails too, stop treating this as a feature-specific problem and investigate the shared dependency first.
The least risky fix
Route A — Correct the observable mismatch
Review activity zone and recording entitlement before resetting device. Start only after capturing the baseline. When the recommended control is not present on your model, look for its supported equivalent in the product documentation rather than following screenshots from another version.
Return immediately to the failing task and check whether the outcome changed. If it did, preserve the working setting and avoid piling on additional changes. If it did not, undo the change where appropriate before moving to deeper checks.
Diagnosis by evidence
| Hypothesis | Evidence worth checking | Next decision |
|---|---|---|
| Motion detection zone excludes path | Repeat the same action under a controlled alternate state and record the exact difference in outcome. | If the control still works, focus on the affected path rather than resetting the whole device. |
| Subscription/storage unavailable | Inspect the permission, account or entitlement attached to this feature, without changing any other user profiles. | If this condition is not present, leave the associated setting unchanged. |
| Recording privacy schedule disabled | Inspect the permission, account or entitlement attached to this feature, without changing any other user profiles. | Only escalate to this branch if the simpler comparison did not explain the failure. |
What to do when it persists
Route B — Test the underlying dependency
Compare local SD/cloud event status, time zone and privacy controls. This advanced comparison is worthwhile only if the simple check did not resolve the problem. The first two possibilities to separate are motion detection zone excludes path and subscription/storage unavailable. Do not interpret their presence as proof of a diagnosis; a compatible device and a partially failed service may coexist.
Route C — Handle a limitation or persistent fault
A third explanation is recording privacy schedule disabled. Check whether the feature requires particular hardware, account privileges, region settings or source formats. When a feature is unsupported, there may be no legitimate settings-only fix; use the vendor-documented alternative rather than an unsafe workaround.
Protect your setup: Do not record neighbors' private areas. Preserve privacy schedules and automation rules, and confirm what the product model actually supports. Do not expose home controls directly to the internet.
Step-by-Step Troubleshooting
Follow the Beginner steps first. Advanced steps are for isolating hardware, application or network-specific causes after a safe baseline test.
Confirm the boundary
Camera streams live video but no stored events appear. Do not assume this is a complete outage. Trigger one harmless motion event while watching notification. Keep the account and connections unchanged between attempts.
Capture a useful baseline
Write down the affected model, software version, active input and when this started. Trigger one harmless motion event while watching notification. A working comparison tells you which part of the chain is still healthy.
Use the least disruptive correction
Review activity zone and recording entitlement before resetting device. Apply one supported change at a time; stop if your model uses a different setting or does not advertise the feature.
Confirm the expected outcome
Test event produces expected clip in correct account. Try the original failing action again, not an unrelated easier test; retain the old setting until you know the change helped.
Test the first dependency
Investigate whether motion detection zone excludes path. Specifically, repeat the same action under a controlled alternate state and record the exact difference in outcome. Compare the result with the working baseline from the beginner route.
Separate another possible cause
Assess whether subscription/storage unavailable. For this branch, inspect the permission, account or entitlement attached to this feature, without changing any other user profiles. Do not change that configuration unless the evidence supports it.
Inspect the third branch
Compare local SD/cloud event status, time zone and privacy controls. Also consider recording privacy schedule disabled. Record the exact point of failure and check product-specific support limits.
Validate and plan a rollback
Test event produces expected clip in correct account. Do not record neighbors' private areas. If the last change made matters worse, restore it and request supported assistance with a redacted troubleshooting summary.
Verify the result
Success looks like this: Test event produces expected clip in correct account. Run this check on the same device and account that originally failed. A different device passing is useful as a comparison, but it does not prove the original issue is fixed.
What to check if it still fails
Before contacting support, collect the exact model and version, the outcome of the baseline test, and whether the controlled correction changed anything. Keep passwords, private media, account identifiers, serial numbers and network keys out of screenshots or shared logs. Do not record neighbors' private areas.
Solution Checklist
Frequently asked questions
Should I reset the entire device?
Not at this stage. Trigger one harmless motion event while watching notification. A reset can erase useful state and is not justified when a specific path can still be isolated.
Which detail should I give support?
Report the exact symptom and the outcome of the targeted test: Test event produces expected clip in correct account.
Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.