Short Answer: Home Assistant Can Feed Apple Home, but It Does Not Become HomeKit Secure Video

Yes, Home Assistant can expose camera accessories to Apple Home. The current HomeKit Bridge docs describe camera support, accessory mode, audio, stream settings, and optional linked motion or doorbell sensors so Apple Home can show the camera and react to events.

No, that does not mean Home Assistant is directly providing HomeKit Secure Video recording. Apple's current HSV documentation describes an iCloud+ recording flow with a home hub, ten days of activity history, and Apple-side analysis for people, pets, or cars. Home Assistant's current docs do not describe a built-in HSV recording role.

Inference from the current docs: the built-in Home Assistant HomeKit bridge is a camera streaming and event bridge for Apple Home, not a documented HomeKit Secure Video recorder.

Why This Question Keeps Coming Up

This is not a manufactured topic. On the Home Assistant Community forum, a December 1, 2024 What the heck?! thread asked again why cameras exposed to HomeKit still did not support HomeKit Secure Video, explicitly noting that the same complaint had already been raised two years earlier.

Reddit shows the same demand in more practical language. In the r/homeassistant thread Getting non-HomeKit cameras into HomeKit, the actual homeowner question was simple: if cameras land in Home Assistant first, will Apple Home see them, and what features will be missing? The top answer drew the same line this article is drawing: Home Assistant can provide the feed, but not the full HSV feature set, which is why people keep pointing toward Scrypted.

A newer Home Assistant Community thread about Ring plus HomeKit pushed the same requirement further on November 23, 2025: the user specifically wanted HomeKit Secure Video recording and the familiar Apple TV live-view pop-up on motion. The answer again was not "turn on a Home Assistant option." It was "look at Scrypted."

That repeated pattern matters. The demand is not just "can I see a thumbnail?" The demand is usually one of two more specific things:

  • I want Apple Home to be the family-facing camera app.
  • I want Apple's recording timeline, recognition, and alerts, not just a stream tile.

What Home Assistant Officially Supports Today

Home Assistant added HomeKit camera support back on May 20, 2020, when the 0.110 release notes announced that Home Assistant could expose cameras to HomeKit.

The current HomeKit Bridge documentation goes further than a vague "camera support" bullet. It documents the actual camera-specific options Home Assistant exposes to Apple Home today:

  • mode: accessory for camera pairing, with a single entity per accessory.
  • linked_motion_sensor so the camera accessory can enable motion notifications.
  • linked_doorbell_sensor so a camera can also behave like a doorbell endpoint in Apple Home.
  • support_audio, plus stream tuning fields such as stream_source, stream_count, and codec settings.

That is real camera integration. But notice what the docs describe: streaming and accessory behavior. They do not describe the Apple-side recording role that Apple's HSV docs tie to iCloud+ and a home hub.

A local smart home camera review workflow that separates recording and viewing layers
Apple Home, Home Assistant, and a local NVR can coexist cleanly, but only if you decide which layer owns recording, alerts, and review instead of assuming one checkbox will do all three.

Choose the Right Architecture for the Goal

The practical mistake is trying to solve four different camera goals with one bridge setting. They are not the same problem.

If your real goal is... Better answer Why
See a Home Assistant camera in Apple Home for live view Home Assistant HomeKit Bridge in accessory mode The official HomeKit Bridge docs support this directly and document the camera-specific stream settings.
Get Apple Home motion or doorbell behavior from a Home Assistant camera Home Assistant HomeKit Bridge plus linked motion or doorbell sensors The docs explicitly support linked_motion_sensor and linked_doorbell_sensor for camera accessories.
Get Apple's encrypted ten-day recording timeline and HSV experience Keep the camera on a native HSV path or bridge it with Scrypted Apple documents HSV as an iCloud+ and home-hub recording flow, and Scrypted explicitly documents HSV support for imported cameras.
Keep recordings, retention, and automation review local Use a local NVR path such as Frigate and optionally expose live view to Apple Home separately Frigate documents local install/storage behavior and a separate HomeKit exposure path through go2rtc.

Path 1: Use Home Assistant HomeKit Bridge When Live View in Apple Home Is Enough

This is the cleanest answer when the camera already integrates well with Home Assistant and your Apple requirement is mostly family-facing convenience.

The official docs are clear that cameras must be paired in accessory mode, not buried inside a general bridge with dozens of other entities. That is not a cosmetic recommendation. It is how Home Assistant expects camera accessories to behave in Apple Home.

What you do get

  • Camera live view inside Apple Home.
  • Optional audio if the stream and config support it.
  • Motion and doorbell behaviors when you link the appropriate Home Assistant entities.
  • A local-first path when the camera itself is already in Home Assistant through ONVIF, vendor RTSP, UniFi Protect, Frigate, or another local integration.

What you do not get

Do not confuse the Apple Home camera tile with HomeKit Secure Video. A stream tile is not the same as Apple's recording pipeline, timeline, or camera analysis path. If what you really wanted was the Apple recording history with person, pet, or vehicle analysis on the Apple side, this path alone does not deliver that.

When this path is right

Use this when Home Assistant is already the operational source of truth and Apple Home is just the viewing surface the household prefers. It is especially reasonable when a separate local recorder already exists and you simply want the camera in the Home app next to the rest of the house.

Path 2: Keep the Camera Native to Apple Home When HSV Is Non-Negotiable

If the actual requirement is "I want HomeKit Secure Video exactly as Apple ships it," the clean answer is to keep the camera on a native Apple-compatible path.

Apple's HSV docs describe the product clearly: with iCloud+, you can store camera footage in iCloud, view the last 10 days of activity, and rely on a home hub such as a HomePod or Apple TV for analysis and recording behavior.

Apple also makes the plan limits explicit in the current docs:

  • 50 GB iCloud+: one camera.
  • 200 GB iCloud+: up to five cameras.
  • 2 TB and above: unlimited cameras.

That is useful because it tells you something architectural: HSV is not just a codec setting. It is part of Apple's own storage, home-hub, and Home-app behavior. If that experience is the product you want, keep the camera on that product path.

Tara's camera rule: if a household depends on the Apple camera timeline, treat Apple Home as the recorder. If the household depends on local retention and Home Assistant automations, treat the local NVR as the recorder. Do not pretend one tile means both layers are now the same thing.

Path 3: Use Scrypted When the Camera Is Not Native HSV, but the Apple Experience Still Matters

This is why Scrypted keeps appearing in every serious camera-plus-Apple thread.

Scrypted's own HomeKit docs explicitly say that cameras imported into Scrypted can be streamed to the Home app including support for HomeKit Secure Video. The same docs also say that HSV requires a HomePod or Apple TV, and that each camera is typically paired in accessory mode.

That makes Scrypted a very different answer from Home Assistant's built-in HomeKit Bridge. Home Assistant is exposing a Home Assistant entity to Apple Home. Scrypted is presenting the camera to Apple Home in a way that is specifically designed around Apple's camera expectations.

Why people pick Scrypted

  • They want non-HomeKit cameras to behave more like real HSV cameras.
  • They care about Apple TV pop-ups, iPhone camera review, or the Apple Home camera UX.
  • They already pay for iCloud+ and want to use that spend instead of buying another cloud camera subscription.

The Scrypted tradeoff

It is another moving part. It has its own camera-prep rules, its own plugin layer, and its own operational surface. That is why some Home Assistant users resist it. But the reason the community keeps recommending it is also obvious: it is purpose-built for the camera-to-Apple gap Home Assistant itself does not fully close.

Path 4: Keep Recording Local When Local Review Matters More Than Apple's Timeline

If your actual priority is privacy, retention ownership, AI review, or long-term event history under your own hardware, a local NVR path is usually the more coherent answer.

Frigate's docs describe two relevant pieces for this conversation:

  • Frigate can be installed as a Docker container or as a Home Assistant App.
  • Frigate cameras can also be exposed to Apple HomeKit through go2rtc.

That means Apple Home does not have to be the recorder just because it is the viewer. You can keep recordings, exports, and review on local storage while still giving Apple Home a live-view surface if the household likes it.

This split is often the best Tara-style architecture: local NVR for ownership, Apple Home for convenience, Home Assistant for automations and cross-system logic.

The Rough Edges That Still Matter

1. Same-LAN discovery and networking still matter

HomeKit pairing is still boring-network technology. The HomeKit Bridge docs say the pairing iPhone needs to be on the same local network as Home Assistant. Frigate's HomeKit docs also require the iOS device to be on the same network as Frigate. If you run segmented VLANs or container isolation, do not assume this will be plug-and-play.

2. Accessory mode is not optional for cameras

Home Assistant's docs require cameras in accessory mode. Scrypted also recommends accessory-style pairing for cameras and explains why: HomeKit bridges serialize requests in a way that can make camera interactions slower. If the camera looks wrong in Apple Home, this is one of the first places to check.

3. Notifications and recording are different layers

You can absolutely make Apple Home feel more camera-aware by linking motion and doorbell sensors from Home Assistant. That still does not mean recording ownership moved to Home Assistant or that the camera now has HSV. Motion notifications, live view, and recording are separate concerns. Treat them that way.

4. Decide which system is the system of record

If a security incident matters, where will the clip come from? Apple Home? Frigate? The vendor NVR? The Home Assistant stream entity? Decide that now. A mixed camera stack is fine. A mixed stack where nobody knows which timeline is authoritative is not.

Tara's Take

If a homeowner asks, "Can Home Assistant use HomeKit Secure Video?" the honest answer is: not directly in the built-in HomeKit Bridge path I could verify on June 22, 2026.

What Home Assistant can do very well is expose a camera to Apple Home, attach motion or doorbell behaviors, and let Apple remain the family-facing app when that helps. What it does not do is erase the difference between a camera stream and Apple's HSV recording pipeline.

If the Apple camera experience is the requirement, plan for Apple-native or Scrypted. If local control, local recording, and Home Assistant automations are the requirement, plan for a local NVR and expose Apple view separately if useful.

If this question is really about Apple coexistence, local camera ownership, or how to separate viewing from recording cleanly, these are the next useful reads.

FAQ

Can Home Assistant expose a camera to Apple Home?

Yes. The HomeKit Bridge docs support exposing cameras to Apple Home, but cameras must be paired in accessory mode rather than inside a general multi-device bridge.

Can Home Assistant itself provide HomeKit Secure Video recordings?

Not directly based on the current official feature surface I could verify on June 22, 2026. The Home Assistant docs describe camera streaming and event hooks for Apple Home. Apple's HSV docs describe an iCloud+ recording flow with a home hub. Home Assistant does not currently document a built-in HSV recording role.

Can I still get Apple Home motion or doorbell alerts without HSV?

Yes. Home Assistant's HomeKit Bridge docs support linked_motion_sensor and linked_doorbell_sensor on camera accessories, which lets Apple Home behave more like a proper camera endpoint even when recording lives somewhere else.

What does HomeKit Secure Video itself require?

Apple's current docs require iCloud+, a home hub such as a HomePod or Apple TV, and a compatible camera path. Apple currently says the 50 GB plan supports one camera, the 200 GB plan supports up to five, and 2 TB and above support unlimited cameras.

Should I use Scrypted or Frigate?

Use Scrypted when the Apple Home and HSV experience is the primary requirement. Use Frigate or another local NVR path when local recording, Home Assistant automations, and locally controlled review are the primary requirement, and expose live view to Apple Home separately if desired.