Local baby monitor setup with Frigate and RTSP

A camera pointed at a crib is the last feed I’d hand to a vendor 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.

A wired RTSP/ONVIF camera with good night vision, plus Frigate and Home Assistant, is the strongest local option. Confirm RTSP support on the exact model before buying, and remember Frigate is a surveillance tool, not a breathing or safety monitor.

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 tradeoffs: Frigate takes some setup, and real-time object detection benefits from a hardware accelerator (an Intel iGPU through OpenVINO, a Hailo-8 or 8L module, or an NVIDIA GPU, with a Coral now recommended mainly for low-power builds). For a single low-resolution baby-room feed the demands are modest, but don’t expect zero configuration. Not every camera supports RTSP, either; many cloud-first consumer cameras (and several battery models) deliberately don’t expose it, so you must pick a camera that does. And Frigate’s motion and 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 or 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, a small indoor body, and reliable RTSP. Mains power, not battery: an always-on monitor cannot die at 3am.

The cheap answer is the TP-Link Tapo C120. It is under $40, has color night vision and a microSD slot, and streams to Frigate over ONVIF/RTSP once you update its firmware and turn that on. It is Wi-Fi only, and the Tapo app nags about cloud features you can ignore. I haven’t run one; the pick rests on the spec sheet and what other Frigate users report.

If you already run UniFi Protect, which I do, use it. The UniFi G6 Instant is a small Wi-Fi indoor camera with 4K and on-device detection, and the UniFi G5 Flex is the cheaper 2K PoE version with desk and wall mounts in the box. Both record to your own Protect host and hand Frigate an RTSP stream if you want detection there too. The catch is that Protect needs a UniFi console, so this route only makes sense if you own one already.

Outside those, Amcrest and Reolink both sell indoor pan/tilt cameras with RTSP that suit a nursery; check the exact model’s spec sheet. Skip doorbells and outdoor bullets, even though they speak RTSP: the body is wrong for a shelf in a bedroom. For wired models that pair well with Frigate in general, see the best PoE cameras for Home Assistant.

Two 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. And verify the exact model’s RTSP support on the manufacturer’s spec sheet before buying, because 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 hardware detector helps if you enable object detection, with an Intel iGPU the usual starting point.
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.

Alerts beyond the camera

Frigate’s motion events are the wake-up signal; you do not need a separate motion sensor in the room for that. Two additions earn their place. A contact sensor on the nursery door, such as the Aqara Door and Window Sensor P2, tells Home Assistant when someone goes in, which is useful for pausing notifications while you are already there. And if you want an audible alert somewhere else in the house, the Aeotec Siren 6 on Z-Wave or the Heiman Zigbee Smart Siren on Zigbee are both fully local. Put the siren in the room where you sleep, never in the baby’s room. Tie it together with one automation: Frigate motion between the hours you choose, door closed, send a phone notification with the snapshot, and only fire the siren if nobody acknowledges within a minute.

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?

For HomeKit, use a camera that supports HomeKit Secure Video if you want to view it in the Apple Home app, but 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 it cannot capture or store the video, and there is no option to keep recordings on it instead of iCloud.

Hubitat is not a video platform. You can use it for the automation side, say a Zigbee motion sensor in the nursery triggering a light or a notification, while a separate RTSP camera plus Frigate handles the actual video.