Quick answer: Frigate, a local NVR, watches your camera streams, detects people and cars with AI running on your own hardware, and publishes every event to MQTT — which Node-RED turns into real automations. The NVR side is solved software; the hard part is the camera. It needs an RTSP stream, wired power, usable night vision, and no cloud lock-in.
What Frigate does — and why the camera is the hard part
Frigate is an open-source network video recorder built around one idea: detection happens locally, on your hardware, against your camera streams. It documents support for CPU detection, OpenVINO on Intel, and accelerators like the Google Coral, and it publishes everything it sees over MQTT. Footage and events stay in your house. For anyone who has read a smart camera's privacy policy and then unplugged the camera, that is the whole pitch.
But Frigate can only work with what the camera hands it. A camera that refuses to share its video — cloud-only models that stream to a vendor's servers and offer no local RTSP — is a paperweight in this setup. That is why camera choice matters more than NVR tuning, and why "will it cooperate?" is the first question, not the last.
The camera checklist for Frigate duty
Four things decide whether a camera will play well, in order of importance:
- RTSP or equivalent local stream access. Non-negotiable. Frigate's camera setup docs assume you can point it at a stream URL. If the spec sheet doesn't mention RTSP or ONVIF, assume it doesn't cooperate.
- Wired power, ideally wired network. Frigate wants a continuous stream to analyze. A camera that sleeps to save battery and wakes on motion is structurally wrong for this job — it is asleep exactly when you need it watching.
- Night vision that actually works. Most break-ins happen in the dark, and detection quality collapses if the camera can't see. Check the IR range or color night vision claim against a real spec, not a product-titel adjective.
- Resolution your hardware can swallow. A 4K main stream costs real decode horsepower. Frigate's docs recommend pulling a lower-resolution sub-stream for detection and saving the main stream for recording — which means the camera should expose both.
If you are shortlisting cameras, CompareSmartDevice's verified security camera specs page collects the specs that decide Frigate compatibility — stream access, power, night vision — so you can filter out the cloud-first models Frigate users want to avoid anyway.
If you buy through links on the sites we recommend, we may earn a small commission.
Old RTSP camera or purpose-built smart camera?
Both routes work. They fail differently.
The old or generic RTSP camera — a hand-me-down IP cam, a no-name ONVIF box — is often the cheapest way in. It streams, Frigate detects, done. Downsides: weak night vision, noisy sensors, and a web UI you will use exactly once. For a first Frigate install, that is a fine trade.
The purpose-built smart camera (Reolink and Tapo wired models are common picks in the self-hosted community) buys you better image sensors, real IR or color night vision, and sub-streams. The trap is that some models in the same product line are cloud-first or battery-powered — near-identical names, opposite behavior. Check the specific model, not the brand.
The battery cloud camera — the Blink/Ring/Wyze-battery category — is the wrong instrument for Frigate, full stop. No continuous stream, no local access, and a subscription where your automation should be. It is not a worse Frigate camera; it is not a Frigate camera.
The event flow: camera → Frigate → MQTT → Node-RED
Three hops, kept high-level — the Frigate docs cover the wiring.
1. Frigate watches the stream
You give Frigate each camera's stream URL and detection settings. Its detector — CPU, OpenVINO, or a Coral — labels objects per frame: person, car, cat. Motion regions and zones cut false positives before they become events; a zone that excludes the street is the difference between "car in the driveway" and forty notifications about traffic.
2. MQTT carries the events
Frigate publishes to documented topics: frigate/events for the full event record, frigate/<camera_name>/<object_name> for per-camera snapshots, and frigate/available for camera health. Any MQTT broker you already run for other devices picks these up for free — if you followed a Shelly or Tasmota setup, the broker is already there.
3. Node-RED reacts
An mqtt in node subscribes to frigate/events; a switch node filters by camera and object; the output drives whatever you already have. Porch person after dark → turn on the entry lights. Car in the driveway zone → notify the phones. Person in the backyard → siren and snapshot push. The pattern is identical to any other MQTT automation in Node-RED — the camera just became another sensor on the bus, which is exactly how it should feel. For the broader picture, the 2026 local smart home build shows where this sits in the architecture, and the sensors-and-relays guide covers the sensor-input pattern from the wired side.
Honest limits
- Continuous streaming is the price of admission. Wired power and preferably wired network. Wi-Fi cameras work; battery cameras do not.
- Detection quality is your hardware's quality. The "AI" label on a camera box means nothing here — Frigate does the detecting, and its accuracy depends on your detector, your stream settings, and camera placement.
- Local processing means local responsibility. Footage never leaves the house — that is the privacy win — but storage, retention, and backups are now your problem. Budget the disk before the cameras.
- It is an NVR, not a security service. Frigate records and detects; it does not call the police. Node-RED automations are notifications and switches, not a monitoring contract.
Frequently asked questions
Do I need a Google Coral?
No. Frigate documents CPU detection and OpenVINO alongside Coral and other accelerators. A Coral lowers CPU load and raises throughput; start without it and add one when the fans spin up.
Can I use Wi-Fi cameras?
Yes, with caveats: continuous Wi-Fi streaming wants good coverage and a camera on mains power. Battery-powered cameras — Wi-Fi or not — do not cooperate.
Does Frigate replace my cloud camera subscription?
For recording and detection, yes — that is the point. What it will not do is store video on someone else's servers for you. Your NVR disk is the cloud now.
Sources
- Frigate documentation — installation, concepts, supported detectors
- Frigate MQTT integration — topic reference (
frigate/events, per-camera topics) - Frigate camera setup — stream configuration, sub-stream guidance
- Frigate object detectors — CPU, OpenVINO, Coral detector options
- Frigate hardware docs — detector and accelerator requirements
- Node-RED official documentation
- MQTT — publish/subscribe messaging standard