Currently Available: Need a skilled Software Developer for your next project?
Categories
Self-Hosting

How to Replace Cloud Doorbells and Cameras With a Self-Hosted NVR Like Frigate

To replace cloud cameras and doorbells with Frigate, choose models that send video over your local network. Then run Frigate on hardware you control to record and analyze that video. Frigate is self-hosted NVR software. An NVR, or network video recorder, stores and organizes footage from network-connected cameras. The main challenge is finding compatible cameras. A camera’s mobile app or smart-home integration does not show whether Frigate can access its video directly.

Cameras that provide an RTSP stream are easiest to connect. RTSP is a standard way to send live video over a network. ONVIF is a standard that helps compatible cameras and software find video streams and share information about camera features. After confirming that each camera provides a usable local stream, plan Frigate’s computer and storage, set recording rules, and decide which cloud features you still need.

Check camera compatibility before replacing anything

First, check the exact model, hardware revision, firmware, and power mode for each camera and doorbell. Look for documented RTSP or ONVIF support. If Frigate cannot discover a camera automatically, you can enter its RTSP address manually. A failed discovery attempt does not prove that a camera lacks a usable stream: incorrect login details or missing ONVIF support can also prevent discovery, according to Frigate’s camera setup documentation.

Check each feature separately. A working video stream does not mean the camera supports continuous recording, local doorbell-press events, a physical chime, or two-way audio, which lets you speak through the camera and hear its microphone. Confirm each feature for the exact model and firmware, then test it before relying on it.

Home Assistant’s Ring integration signs in to Ring’s cloud. It supports features such as live view, while playback of the last recording requires Ring Protect. That integration can help with smart-home controls, but it does not by itself establish that a particular Ring camera provides a local stream for Frigate. Verify local-stream support for the exact model before planning a full replacement.

For new hardware, look for explicit local-stream support rather than relying on a “smart” label. Reolink’s Video Doorbell PoE is one example of a wired doorbell whose product support materials list RTSP and ONVIF, along with two-way audio and continuous-recording options. Check the exact model and firmware: support can vary between models and power modes. For instance, Reolink says its second-generation battery doorbell supports RTSP and ONVIF in wired-power mode but not in battery mode, subject to its stated requirements in the model’s FAQ.

Plan Frigate’s computer, streams, and storage

Frigate connects to camera streams, records video, and analyzes selected frames for motion and objects. You can run Frigate in Docker, which runs software in an isolated container, or as a Home Assistant App. Frigate’s installation documentation favors Docker on bare-metal Debian-based hardware; a virtual machine can make hardware acceleration harder to access. Whichever option you choose, store Frigate’s settings and video on storage that keeps its data after a restart or container update. See the installation requirements before choosing how to deploy it.

Many cameras offer a high-resolution main stream and a lower-resolution substream. Frigate can record from the main stream and use the substream to detect objects. This keeps saved footage detailed while reducing the video Frigate must analyze. Frigate recommends a detection rate of 5 frames per second for most cameras and advises setting each stream close to the resolution and frame rate you need.

The stream’s encoding also affects playback. Frigate records the camera’s video directly without re-encoding it, which reduces processing work. H.264 video with AAC audio has broad playback support across browsers and Home Assistant. H.265 can use storage more efficiently, but some browsers do not play it. Choose camera settings based on the devices you will use to review footage, and test saved clips as well as live video.

Estimate storage from bitrate and retention time, not resolution alone. Bitrate is the amount of video data a camera sends each second. Retention time is how long Frigate keeps recordings. For continuous recording, use this estimate:

Storage per day ≈ bitrate in Mbps × 10.8 GB

At 4 Mbps, one camera produces about 43.2 GB per day, or 1.296 TB over 30 days, before overhead and reserve space. Four cameras at the same bitrate would require about 5.184 TB for 30 days. Actual use varies with camera settings and scene activity. Frigate’s installation planning guidance also identifies camera count, resolution, frame rate, recording mode, and retention period as storage factors.

Local disks simplify recording because the NVR can reach them without a network connection. Network-attached storage can also work, but continuous recording needs a reliable, fast network and a storage device that can handle the data. Check that Frigate writes to the intended disk and that its connection to the storage stays available. If that connection fails or points to the wrong place, recordings can go to the wrong location or footage can be missing.

Frigate also needs enough processing capacity to decode each camera’s video, turning the compressed stream into images it can analyze. A detection accelerator speeds up the search for objects, but it does not decode video. Frigate’s hardware guidance describes several accelerator options and says the Coral TPU is no longer recommended for most new installations, though it remains supported. Choose hardware based on the number and size of your streams, then check how it performs with your cameras. Published capacity examples are starting points, not guarantees for busy scenes or different configurations.

Set recording rules and rebuild the features you use

By default, Frigate does not keep continuous recordings indefinitely. Choose how long to keep footage and what to record: everything, motion, or events. Keeping all footage gives you a fuller timeline and uses the most storage. Motion-based or event-based recording saves space, but Frigate keeps footage only when its rules detect the activity you selected. Frigate’s recording settings describe these options. Its recording troubleshooting guidance also explains that turning on recording does not by itself keep footage continuously.

Before removing the old service, test each step: open a live stream, trigger motion, find the resulting footage, and check that the clip plays in the browser or on the phone you plan to use. Export important clips separately if you want to keep them outside normal retention; Frigate stores exported footage separately from recordings managed by the retention policy.

Home Assistant can add dashboards, notifications, and automations. Frigate’s Home Assistant integration uses MQTT, a lightweight messaging service that lets devices and software exchange events; many Frigate entities require MQTT to be enabled and shared between the two systems. A motion alert and a physical doorbell press are different events. Confirm that your doorbell exposes its button press to the local software, and test it directly rather than assuming that video support includes button events.

Two-way talk also needs a separate test. Frigate’s live-view documentation describes requirements involving go2rtc, a component that can restream camera video, and WebRTC, a technology for real-time audio and video communication. Two-way audio depends on the camera and client as well as the stream setup. RTSP support alone does not guarantee that the microphone and speaker will work through Frigate.

A local doorbell can keep some features working without keeping every cloud service. Reolink says its PoE doorbell can record locally and ring a connected chime without internet, while mobile alerts and mobile live view require internet access. That distinction is worth checking for any replacement: local recording, remote viewing, alerts, and calling are separate features.

Secure remote access and camera connections

Local recording means the camera does not need a vendor’s cloud to send footage to the NVR. It does not secure the cameras or NVR by itself. Give each camera a unique password, keep its firmware updated, and restrict network access to the NVR and other devices that need it. A separate camera network can limit exposure, but it must still allow Frigate to reach the cameras.

Pay attention to Frigate’s network ports. Its installation documentation identifies an internal, unauthenticated interface and says RTSP restreaming is unauthenticated by default unless configured. The interface and API also offer an authenticated access option, but without TLS encryption. Do not expose internal or unauthenticated ports directly to the internet; choose a secured remote-access method and follow Frigate’s deployment guidance. CISA’s IoT security guidance also recommends strong credentials and network segmentation for connected devices.

With local storage, you control the recordings and must manage updates, storage health, backups, and remote access. Cloud services bring their own privacy controls and dependencies. Ring, for example, describes encryption protections in its own security white paper; those statements describe Ring’s approach and are not an independent audit. Compare local custody and self-management with the convenience and vendor-managed controls of the service you use.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com

Email updates

Usually a new article and a few links I found interesting.

No spam. Unsubscribe with one click.

Leave a Reply

Your email address will not be published. Required fields are marked *