Local baby monitor setup with Frigate and RTSP

A baby monitor is one of the most justified reasons to keep video off the cloud. Pairing an RTSP camera with Frigate and Home Assistant gives you a private monitor whose footage never leaves your network. This guide covers a realistic setup, the hardware that actually works, and where the tradeoffs are.

Why Frigate and RTSP for a local baby monitor

Frigate is an open-source NVR with built-in object detection that runs on your own hardware and integrates tightly with Home Assistant (if you’re new to it, start with how to build a Frigate NVR from scratch). It pulls video from IP cameras over RTSP (Real-Time Streaming Protocol), records it locally, and can fire events into Home Assistant.

The payoff is privacy and control: the feed stays on your LAN, you decide retention, and you’re not trusting a vendor’s cloud with a camera pointed at your child.

The honest tradeoffs:

• Frigate takes some setup, and real-time object detection benefits from a hardware accelerator (a Google Coral, or an Intel iGPU/NVIDIA GPU). For a single low-resolution baby-room feed the demands are modest, but don’t expect zero configuration.
• Not every camera supports RTSP. Many cloud-first consumer cameras (and several battery models) deliberately don’t expose it. You must pick a camera that does.
• Frigate’s “motion/object” detection is general-purpose computer vision. It is not a medical or breathing monitor and should not be relied on as a safety device. Treat it as a convenient way to watch and get presence/motion alerts, not as a substitute for supervision.

Hardware: pick a camera that really does RTSP

For a baby monitor you want solid night vision, two-way or at least one-way audio, and reliable RTSP. Good options:

• A wired PoE or Wi-Fi IP camera that speaks RTSP/ONVIF. Amcrest and Reolink both make affordable indoor cameras and pan/tilt models in this category that work well with Frigate. A wired camera is the right call for an always-on monitor — you don’t want a battery dying overnight. See the best PoE cameras for Home Assistant for wired models that pair well with Frigate.
• The Amcrest AD110 / AD410 doorbells expose RTSP and could be repurposed, but a plain indoor camera with pan/tilt and good low-light performance is a better fit for a nursery than a doorbell.

A few buying cautions, since this is where misinformation is common:

• Battery-powered Wi-Fi cameras frequently do not expose RTSP. If a listing doesn’t explicitly say “RTSP” or “ONVIF,” assume it can’t stream to Frigate.
• Verify the exact model’s RTSP support on the manufacturer’s spec sheet before buying — RTSP availability varies even within a brand’s lineup.

Setting up Frigate with Home Assistant

1. Install Frigate. Run it as a Home Assistant add-on or in Docker on a machine with a bit of headroom; a small hardware detector (Coral or iGPU) helps if you enable object detection.
2. Find your camera’s RTSP URL. Each brand has its own format; enable RTSP/ONVIF in the camera’s settings first.
3. Configure the camera in Frigate. A minimal example:

   cameras:
     baby_room:
       ffmpeg:
         inputs:
           - path: rtsp://USER:PASSWORD@192.168.1.100:554/stream1
             roles:
               - detect
               - record
       detect:
         width: 1280
         height: 720
         fps: 5

   (Lower detection fps keeps CPU/accelerator load down; you can record at full frame rate while detecting at a lower one.)
4. Add the Frigate integration in Home Assistant to view the live feed and surface events.
5. Build automations — e.g. a notification or a light when motion is detected in the room — using Frigate’s events as triggers.

A realistic alternative for non-Frigate setups

If running an NVR feels like too much, you can still keep things local by viewing an RTSP camera directly through Home Assistant’s generic camera integration (with go2rtc for low-latency live view) and skipping continuous recording. You lose recorded history and smart detection, but you keep a private live feed with very little setup.

What about HomeKit and Hubitat?

• HomeKit: Use a camera that supports HomeKit Secure Video if you want to view it in the Apple Home app, but be clear that HKSV is not local storage. Clips are end-to-end encrypted and stored in iCloud, not on any device in your house, and recording requires a paid iCloud+ plan (50 GB covers one camera, 200 GB up to five, 2 TB unlimited). Apple keeps roughly the last 10 days of events, and HKSV clips do not count against your iCloud storage quota. A HomePod or Apple TV is required as the home hub and it does the motion analysis locally, but note clearly: an Apple HomePod or HomePod mini is a speaker/hub, not a camera. It cannot capture or store the video, and there is no option to keep recordings on it instead of iCloud.
• Hubitat: Hubitat is not a video platform. You can use it for the automation side — e.g. a Zigbee motion sensor in the nursery triggering a light or a notification — while a separate RTSP camera + Frigate handles the actual video.

Quick verdict

For a private baby monitor, an RTSP/ONVIF camera (wired, with good night vision) plus Frigate and Home Assistant is the strongest local-first option. Confirm RTSP support on the exact model before buying, prefer wired power for an always-on feed, and remember Frigate is a surveillance tool, not a safety/breathing monitor. HomeKit Secure Video is a simpler but cloud-backed alternative, and no smart speaker can act as the camera.