Updated August 4, 2026. A HomeKit Secure Video camera can show a healthy live view while recorded events are missing, delayed, misclassified, or unavailable to the person who needs them. This checklist audits the entire recording path: camera, Home app settings, home hub, iCloud+ eligibility, network, activity zones, notifications, people permissions, and clip export.
Do not wait for an incident to discover that a camera was set to stream only, an activity zone excluded the doorway, the home hub was offline, or the household could not export the event.
What counts as a recording gap?
A gap is any expected event that cannot be found in the Home app timeline or exported when needed. It can be:
- coverage gap: the person or vehicle never entered the camera’s usable view;
- detection gap: motion occurred but did not meet the selected recording trigger;
- mode gap: recording rules differed when people were home or away;
- hub/network gap: the camera, router, or home hub was unavailable;
- account gap: the home owner, iCloud+ plan, or permissions did not support the expected function;
- timeline gap: the event exists but time, camera name, or filters make it hard to find;
- evidence gap: the household can view the clip but cannot save, share, or preserve it.
Start with Apple’s current requirements
Apple’s iPhone camera setup guide explains current Home app camera options. Apple’s iCloud HomeKit Secure Video guide covers the supported camera, home hub, home setup, and iCloud+ path. Check those pages against the operating-system versions and Apple Account used in the home; plan and feature terms can change.
Record these facts before changing settings:
- camera brand, exact model, firmware, and power source;
- Home owner Apple Account and current iCloud+ plan;
- active home hub model, software version, and network location;
- camera room/name and physical location;
- streaming and recording mode for Home and Away;
- selected event types and activity zones;
- people allowed to stream, view recordings, or change accessories;
- date and result of the last successful staged test.
1. Prove the live path first
Open the camera from the Home app while connected to the home network, then test from cellular data. Record image load time, audio, status messages, and whether the camera recovers after the app is closed. A failed live view points to a camera, power, network, hub, or account problem that should be fixed before recording logic is tuned.
Use the HomeKit camera setup checklist if the accessory is new, recently reset, or was transferred from another home.
2. Audit Stream & Allow Recording settings
Open the exact camera’s recording options and capture the current Home and Away states. Do not assume both are the same. A privacy-minded household may intentionally stream while home and record while away; the risk is forgetting that rule during a long absence, guest stay, or schedule change.
For each mode, write:
| State | Streaming | Recording | Who should trigger it? | Test result |
|---|---|---|---|---|
| People home | Current setting | Current setting | Person / animal / vehicle / package / any motion as configured | Pass/fail |
| People away | Current setting | Current setting | Configured event types | Pass/fail |
Change one variable at a time. If several detection types, zones, and presence rules change together, a successful test will not show which setting fixed the gap.
3. Test presence and Home/Away changes
Home/Away behavior depends on the home’s people and location state. Test it deliberately:
- Confirm which people count toward presence.
- Check that the correct home and address are selected.
- Verify location access on the devices used for automations.
- Have all counted residents leave the property with their devices.
- Confirm the Home app reaches the expected Away state.
- Stage a recording event and verify the timeline.
- Return and repeat the Home-state test.
Do not weaken phone privacy settings blindly to force a result. Document the minimum supported location permission and explain it to each resident.
4. Check activity zones and the physical scene
An activity zone can reduce street, tree, or neighbor motion, but a badly drawn zone can exclude the first step onto the porch or the hand reaching for a door. Walk the actual approach at the left, center, and right edges. Repeat in daylight, after dark, and with exterior lights switching.
Inspect:
- door frame, eaves, furniture, plants, and parked vehicles blocking the view;
- backlight, glare, reflections, and infrared bounce;
- lens dirt, condensation, insects, and spider webs;
- camera height and angle;
- privacy zones masking more than intended;
- motion beginning outside the chosen activity zone.
Use the HomeKit camera privacy-zone guide to balance evidence with household and neighbor privacy.
5. Stage exact detection events
Run separate tests for a person, vehicle, animal, package, and generic motion only where the camera and current settings support them. Record the test time, route, lighting, distance, clothing contrast, and result. Do not treat one successful daytime person test as proof that night recording, packages, or vehicles work.
A simple test sheet:
| Event | Time/light | Expected | Recorded? | Notification? | Exported? |
|---|---|---|---|---|---|
| Person at main approach | Day / night | Person event | Yes/no | Yes/no | Yes/no |
| Vehicle at drive | Day / night | Vehicle event | Yes/no | Yes/no | Yes/no |
| Package placement | Normal delivery point | Package event if supported | Yes/no | Yes/no | Yes/no |
6. Separate recording from notifications
A recording can exist without a phone alert, and a notification can arrive without a useful clip. Audit both. Check the Home app’s camera notification rules, time restrictions, selected event types, person/activity-zone filters, and the phone’s notification delivery settings.
Use the HomeKit notification reliability checklist to test primary and backup devices. The responder should know how to move from the alert to the correct camera timeline and what action is safe.
7. Check the home hub path
Record which Apple TV or HomePod is currently connected as the home hub and which devices are standby candidates. Confirm power, network, software version, room name, and account. Then use the home hub redundancy guide to test a controlled primary-hub outage.
After failover, repeat a live view, staged recording, notification, and remote-access test. A standby label is not proof that the complete security path survives.
8. Test network and power failures
Map camera Wi-Fi, access point, router, modem, home hub, and household power. Run controlled tests:
- camera reconnect after access-point restart;
- home hub reconnect after router restart;
- internet loss while local Wi-Fi remains active;
- power restoration after the camera and hub restart in a different order;
- remote access after the public IP or router changes.
Do not assume a battery camera or UPS-backed router preserves recording if the home hub, bridge, or access point loses power.
9. Audit household permissions
Apple’s Home sharing guidance explains current owner and resident controls. Review every person in the home. Confirm who can:
- stream camera video;
- view recordings;
- add or edit accessories;
- change recording and notification rules;
- receive sensitive camera alerts;
- invite or remove people.
Remove former residents, contractors, house sitters, and test accounts. Give the minimum access needed. Never share the home owner’s Apple Account password.
10. Find and export a clip
Stage an event, open the timeline, find the exact time, review the event label, and save the clip. Open the saved file on a second device and confirm video, audio, timestamp context, and playback. Follow the HomeKit camera evidence-export checklist for preservation and incident notes.
Do not screen-record as the only evidence path unless no supported export exists. Preserve the original file, note who exported it and when, and keep a separate incident log.
11. Build a gap log
For every missing or weak event, record:
- camera and physical location;
- expected event and exact time;
- Home/Away state;
- recording and notification settings;
- activity-zone and detection type;
- hub, camera, network, and power status;
- whether live view worked;
- change made and repeat-test result.
A log prevents repeated guesswork and shows patterns such as night-only misses, one camera dropping after router restarts, or Away mode failing when one resident’s phone stays home.
12. Monthly maintenance
Run one staged event per camera each month and after camera firmware, router, iOS, Apple TV, HomePod, iCloud plan, Apple Account, or household changes. Clean lenses, review zones, check timestamps, verify users, export a clip, and update the gap log. The HomeKit security maintenance checklist covers the wider accessory set.
Follow the FTC’s connected-device security advice: keep software current, use strong unique passwords, protect the network, and enable stronger account protection where available.
60-minute HomeKit Secure Video recording-gap audit
- 0–10 minutes: inventory camera, firmware, owner, iCloud+ path, hub, recording modes, zones, and permissions.
- 10–20 minutes: test live view locally and remotely; confirm Home and Away state transitions.
- 20–30 minutes: stage separate person and applicable vehicle/package events at scene edges and center.
- 30–40 minutes: compare timeline recordings with phone notifications on primary and backup devices.
- 40–50 minutes: restart the camera path or fail over the home hub under a controlled plan; repeat one event.
- 50–60 minutes: find, export, and play the clip on a second device; review people permissions and write the next maintenance date.
Verdict
A healthy HomeKit Secure Video setup is not proved by a live thumbnail. It is proved when staged events record in both intended presence modes, the right people receive useful alerts, the home hub and network recover, and a clip can be exported on demand. Run the audit before relying on the timeline as evidence.
Frequently asked questions
Why can I see live video but no recordings?
Possible causes include stream-only mode, unsupported iCloud+ or hub state, event filters, activity zones, presence rules, network interruptions, or camera-specific faults. Audit one layer at a time.
Do notifications prove a clip was recorded?
No. Check the Home app timeline and export the clip. Alerts and recordings have related but separate settings and failure paths.
How often should every camera be tested?
Run a staged event monthly and after firmware, router, hub, phone, account, iCloud plan, or household changes.
Should every resident see camera recordings?
No. Give each person only the access needed, review permissions after household changes, and do not share the owner’s Apple Account password.
What is the most important evidence test?
Stage a realistic event, find it by time and camera, export it, and open the saved file on a second device.
