Cameras

Reolink in Frigate: No Frames, 404, Stream Setup

Diagnose Reolink no-frames, FFmpeg 404, disconnect recovery, and codec or playback failures in Frigate; then choose streams by camera model and generation.

Start here: Locate the failing layer

Read the first FFmpeg error before 'no frames'; note whether 404 targets the camera or local go2rtc, then test that exact source from Frigate's network.

Problem summary

Start with the failed layer, not a stream swap. For 'no frames', read the FFmpeg error immediately before it and test the source from Frigate's network. For a 404, distinguish a camera RTSP URL from the local go2rtc restream at 127.0.0.1:8554; the latter can fail because its producer disconnected. After a reconnect, verify recording and detection as well as live view. If go2rtc receives video but the browser is grey, inspect the codec and playback support. Only then choose HTTP-FLV or RTSP using Frigate's model-and-generation table. Reolink's conventional FLV guidance says H.264, while Frigate documents enhanced H.265 HTTP-FLV on certain newer cameras with FFmpeg 8. Results depend on camera hardware, firmware, and the installed Frigate and go2rtc versions.

Operator snapshotEvidence first

First proof

For 'no frames', read the FFmpeg error immediately before the capture warning and probe the exact source from Frigate's network.

Screen to open

ffprobe -v error -show_entries stream=codec_name,width,height -of default=noprint_wrappers=1 "rtsp://USER:PASS@CAMERA-IP:554/Preview_01_sub"

Expected signal

The source reports its video codec and dimensions; the go2rtc producer stays connected and receives frames.

Stop boundary

Stop before forwarding the camera's web, RTSP or FLV ports to the internet.

Layer path

1Treat 'no frames' as a failed video pipeline, not a diagnosis. The preceding FFmpeg or go2rtc log and the failing URL locate the layer: camera source, go2rtc producer, local restream, Frigate capture, or browser playback.

2A camera RTSP 404 and a local `rtsp://127.0.0.1:8554/<stream>` 404 are different. A camera may reject an unavailable path; a local restream can be missing because its name differs from the go2rtc key or its producer timed out. Dated issue reports demonstrate both cases, not a universal Reolink failure.

3Reolink's conventional FLV article describes H.264-only FLV, while Frigate documents enhanced H.265 HTTP-FLV for certain newer 6MP-plus cameras with FFmpeg 8. Frigate recommends HTTP-FLV for 5MP-and-lower cameras and RTSP for older 6MP-plus cameras. These are starting points to test against the camera's actual codec, hardware, firmware, and the installed Frigate and go2rtc versions.

4Frigate recommends 'On, fluency first' and 'Interframe Space 1x' where available, and a low-resolution detect stream. These may improve stream behavior but do not fix a bad URL, unreachable camera, unsupported codec, or stopped producer. After a disconnect, verify recording and detection have resumed even when live view returns.

Runbook

Step-by-step runbook

Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.

Locate the failing layer

Check: Read the first FFmpeg error before 'no frames'; note whether 404 targets the camera or local go2rtc, then test that exact source from Frigate's network.

Expected result: You know whether camera reachability, stream path, producer, capture, or browser playback needs the next check.

If not: If the source is unreachable, resolve auth, port, route, or camera availability before changing codecs or detection settings.

Identify the exact hardware and supported streams

Check: Record model, hardware number, firmware, resolution, main/sub codecs, enabled ports, and any Home Hub or NVR. Compare Reolink's protocol matrix with Frigate's Reolink transport table.

Expected result: The chosen source exists on this unit, and you know whether it is H.264 or H.265.

If not: For a missing option, check model and hardware support before considering firmware; download only firmware matched to that hardware version.

Select and prove main and detect sources

Check: For 5MP or lower, try Frigate's HTTP-FLV recommendation; for older 6MP-plus, try RTSP; for supported newer 6MP-plus, test RTSP or enhanced H.265 HTTP-FLV only with a capable FFmpeg 8 setup. Probe main and sub separately.

Expected result: Both sources return video at the expected codec and resolution; a lower-resolution H.264 substream is available for detection when supported.

If not: If the recommended source fails, inspect its error and test the documented alternative on the actual camera instead of assuming a brand-wide fix.

Connect go2rtc and Frigate roles

Check: Define main and sub streams in go2rtc with exact names, then use their local `rtsp://127.0.0.1:8554/<name>` URLs and `preset-rtsp-restream` in Frigate. Put record on main and detect on the working lower-resolution stream.

Expected result: go2rtc shows connected producers and Frigate receives record and detect frames.

If not: Use `preset-http-reolink` only when Frigate reads Reolink HTTP-FLV directly; it can crash an RTSP restream. Check role paths and logs before adjusting frame rate.

Check playback and a real reconnection

Check: Compare go2rtc stream info, browser live view, Frigate detect FPS, and fresh recording segments. Observe them again after a camera/network interruption.

Expected result: A supported codec plays in the chosen client and capture and recordings resume after reconnect.

If not: If only playback fails, test H.264 or Frigate's H.265 compatibility guidance; if capture stalls, preserve both logs and resolve the failing producer or FFmpeg process.

Tune and secure the working setup

Check: If stutter remains and controls exist, compare 'On, fluency first' and 'Interframe Space 1x' one at a time. Keep the camera off public port forwards and review a day of recordings for gaps.

Expected result: The camera stays reachable from Frigate and recordings remain continuous under normal operation.

If not: A gap still needs timestamped camera, go2rtc, FFmpeg, and network evidence; CBR and keyframe settings are recommendations, not guaranteed repairs.

Safe stop: Stop before forwarding the camera's web, RTSP or FLV ports to the internet.

Did this solve your problem?

Your answer helps us improve this page.

No account or personal details. We store the page, answer, optional reason and day with a 90-day retention period. A random reference in this browser prevents repeat votes. Feedback privacy

Decision tree

If: No frames, with a source timeout or authentication error before the FFmpeg capture warning.

Then: Camera, credentials, or network path to the source is failing.

Action: Probe the exact URL from inside Frigate's network; inspect camera port settings, routing, and go2rtc producer logs.

If: FFmpeg reports 404 from the camera's `:554` URL.

Then: The requested RTSP path or stream is unavailable on that camera or NVR channel.

Action: Check Reolink's main/sub RTSP format and test each path directly; a 2026 RLC-810A report requested an unavailable H.265 sub path.

If: FFmpeg reports 404 from `rtsp://127.0.0.1:8554/<stream>`.

Then: The requested go2rtc restream is unavailable, perhaps from a mismatched name or a failed camera-side producer.

Action: Compare the path with the exact go2rtc stream key and inspect that stream's producer and logs; do not assume 404 means only a typo.

If: Live view returns after a disconnect but recording or detection does not.

Then: The live producer and Frigate's capture/record path may have recovered differently.

Action: Compare go2rtc producers, detect FPS, new recording segments, and FFmpeg logs over the reconnect; preserve evidence before a restart.

If: go2rtc shows frames but only browser live view or playback is blank.

Then: The source is reachable; playback codec or client support is the next layer to test.

Action: Probe whether it is H.264 or H.265, try the H.264 substream, and check Frigate's live-view guidance before considering transcoding.

If: Sources work and you need to choose the transport.

Then: Frigate recommends HTTP-FLV for 5MP or lower, RTSP for older 6MP-plus, and enhanced H.265 HTTP-FLV with FFmpeg 8 or RTSP for certain newer 6MP-plus cameras.

Action: Test the recommended main and sub sources on the exact hardware; use go2rtc restreams with `preset-rtsp-restream` if that layout works.

If: The model needs a Home Hub/NVR for local protocols or has a hardware-specific exception.

Then: Standalone Frigate access depends on Reolink's support matrix, not the battery or Wi-Fi label alone.

Action: Confirm the exact hardware version and required hub/NVR channel; if Reolink lists the model as unsupported, choose another source or model.

Safe stop: Do not buy multiple units for Frigate until a local main and sub stream is proved.

Evidence

Evidence table

Symptom	Evidence to collect	Likely layer	Next action
'No frames have been received' follows an FFmpeg or go2rtc source error.	The first error, exact failing URL, and a source probe from Frigate's network.	Source, network, auth, codec, or producer; no-frames alone does not distinguish them.	Fix the first failing layer; compare with the same source outside Frigate only after testing from its network.
FFmpeg reports `404` on `rtsp://CAMERA-IP:554/...`.	Camera path, requested main/sub stream, port setting, and direct RTSP probe.	Camera or NVR stream path.	Use the stream path the unit exposes; a reported RLC-810A failure used an unavailable H.265 sub path.
FFmpeg reports `404` on `rtsp://127.0.0.1:8554/<stream>`.	Exact go2rtc key, producer status, and upstream go2rtc log at the same timestamp.	Local restream; the producer may have timed out even when the key matches.	Restore or rename the restream according to evidence, then check detect and record roles.
Live view returns after a disconnect, but recording or detection stays stopped.	Producer reconnection, capture/detect FPS, and timestamp of the newest recording segment.	Producer and Frigate capture/record paths may recover separately; an older report showed this symptom.	Probe the source and compare both logs before restarting; do not infer recovery from live view alone.
go2rtc receives a 4K stream but the browser view is grey or blank.	Source codec from ffprobe, go2rtc stream info, and whether the H.264 substream plays.	Playback compatibility can differ from source reception or Frigate decoding.	Use H.264 for compatible live view or assess a supported H.265 playback/transcoding path; verify FFmpeg 8 before enhanced FLV.
High CPU on the Frigate host with only a few cameras.	Which stream has the detect role and its resolution and fps.	Detection may be using a full-resolution stream or transcoding may be active.	Use a working lower-resolution detect stream around 5 fps; check decode and transcode load separately.
Person alerts in the Reolink app but no Frigate event, or vice versa.	Where each system detects: camera Smart Detection vs Frigate's detector and zones.	Two independent detectors with different zones and thresholds.	Tune Frigate's zones and min_score; the camera's AI does not feed Frigate.

Reference

Commands and settings paths

Probe the exact camera source from Frigate's network

ffprobe -v error -show_entries stream=codec_name,width,height -of default=noprint_wrappers=1 "rtsp://USER:PASS@CAMERA-IP:554/Preview_01_sub"

Where: Inside the Frigate container, or on a host with the same route and firewall access to the camera.

Expected: The requested video stream and codec are reported; repeat with the actual HTTP-FLV or main URL if that is the configured source.

Failure means: A timeout, 401, or 404 here points to the camera/network/auth/path before Frigate's capture role.

Safe next step: Check enabled ports and the exact model's main/sub path; redact credentials from any shared output.

Probe the configured HTTP-FLV source and codec

ffprobe -v error -show_streams "http://CAMERA-IP/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=USER&password=PASS"

Where: From the Frigate network with the camera's HTTP port enabled.

Expected: The actual main-stream codec and dimensions appear; repeat with `_ext` or `_sub` if that stream exists.

Failure means: A failed probe can reflect HTTP/auth/path/codec support; HEVC requires checking enhanced-FLV support in the installed FFmpeg and go2rtc versions.

Safe next step: Compare the model's Frigate table row and test RTSP where recommended; do not assume every 4K source can use enhanced FLV.

Compare the local restream name and producer

Frigate UI > Logs > go2rtc; go2rtc web interface at http://FRIGATE-IP:1984

Where: Browser on the Frigate LAN; expose port 1984 locally if your installation requires it.

Expected: The stream key exactly matches `rtsp://127.0.0.1:8554/<key>` and its producer receives frames.

Failure means: A local 404 may be a name mismatch or a producer timeout/disconnect.

Safe next step: Read the go2rtc error at the same timestamp and test that source before editing the Frigate input preset.

Verify recovery beyond live view

Frigate UI > System Metrics and Recordings; Frigate UI > Logs > FFmpeg and go2rtc

Where: Frigate UI after the camera or network connection returns.

Expected: Producer connected, detect FPS nonzero when enabled, and new recording segments appearing for the camera.

Failure means: A working live view can coexist with stalled capture or recording, as seen in an older issue report.

Safe next step: Compare pre- and post-disconnect logs and the source probe; restart only after preserving the failure evidence.

Confirm the camera is isolated from the internet

Router or firewall rules for the camera VLAN, plus `curl -m 5 https://1.1.1.1` from a host on that VLAN

Where: Your router UI and a test device on the camera VLAN.

Expected: Cameras reach Frigate and NTP only; the test to the internet fails.

Failure means: A camera VLAN with internet access can phone home and be reached if credentials leak.

Safe next step: Block the VLAN's WAN access; allow only Frigate and NTP.

Hardware boundary

Hardware and platform boundary

Change only when

Replace or add hardware only after the exact model's local-stream support and the failing layer are confirmed. Some battery models need a Home Hub, while the second-generation Battery Video Doorbell supports standalone protocols in wired-power mode; 4G LTE models are listed as unsupported.

Evidence that matters

Verified RTSP or HTTP source for the exact hardware version, a usable H.264 detect stream, a separate recording stream, and controllable frame rate and keyframe interval where available.

Evidence that does not matter

Megapixel count and camera-side AI marketing do not prove Frigate stream compatibility or detection quality.

Avoid

Avoid purchases based on a family name alone, assuming restreaming transcodes H.265, or exposing camera ports to the internet.

Related tool/calculator

Use the linked calculator or tool to turn this runbook into numbers for your exact setup.

Frigate hardware planner

Last reviewed

2026-09-18 · Reviewed by HomeTechOps. Reviewed 2026-09-18 against Frigate's camera-specific, go2rtc, FFmpeg preset and troubleshooting docs and Reolink's FLV, RTSP, firmware and protocol matrix. March, July and August 2026 Frigate reports illustrate direct-camera 404, failed go2rtc producers, no-frames, and a doorbell that worked over RTSP when HTTP-FLV did not. Those are individual reports, not verified fixes for all models or measured search volume. No camera was bench-tested for this page.

Sources/assumptions

Frigate's Reolink table and go2rtc and FFmpeg guidance were checked 2026-09-18. The table is a recommendation, not a per-model guarantee; verify the installed Frigate and go2rtc versions before using enhanced H.265 HTTP-FLV.
Reolink's FLV article describes conventional FLV as H.264-only. Frigate documents a newer enhanced H.265 path for some cameras. These sources cover different implementations, so inspect the actual stream codec before choosing one.
Reolink's current CGI/RTSP/ONVIF matrix distinguishes standalone support, Home Hub or NVR-dependent models, hardware-version exceptions, and unsupported LTE cameras. Confirm the exact hardware and firmware version before changing firmware.
The dated GitHub reports illustrate no-frames, 404, and reconnect symptoms. They are individual setups, not proof that one transport or setting fixes every Reolink camera.
Smart Detection categories (person on all cameras; vehicle on all except E1 Indoor and FE series; pet/animal by model and firmware; visitor and package on doorbells) are from Reolink's Smart Detection article. Frigate does not consume camera-side detections; it runs its own detector.
This page does not bench-test cameras or measure search volume.

Source-backed checks

HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.

Frigate Docs: Camera Specific Configurations (Reolink section)Primary source for the Reolink transport recommendations by resolution and generation, enhanced H.265 HTTP-FLV requiring FFmpeg 8, optional CBR and iframe settings, NVR channels, and the conditional two-way-talk layout.Frigate docs: Camera setupUsed for the detect-on-substream / record-on-main pattern and recommended stream roles.Frigate docs: FFmpeg presetsUsed for the preset-rtsp-* / preset-http-reolink presets and the go2rtc restream source (rtsp://127.0.0.1:8554).Frigate Docs: Configuring go2rtcUsed for separating source reception from browser codec support and for checking go2rtc logs and the stream web interface.Frigate Docs: RTSP troubleshooting FAQUsed for the VLC-versus-Frigate TCP/UDP distinction and the recommendation to test the actual transport before treating VLC playback as proof Frigate can read a stream.Reolink Support: Introduction to FLV StreamUsed for conventional FLV main/ext/sub URL formats, the port=1935 URL parameter, channel numbering from 0, NVR credentials, and Reolink's H.264-only statement. Frigate separately documents enhanced H.265 HTTP-FLV on certain newer cameras.Reolink Support: Which Reolink Products Support CGI/RTSP/ONVIFUsed for standalone, Home Hub/NVR-dependent, hardware-specific, wired-power, and unsupported CGI/RTSP/ONVIF cases; camera-family labels alone are insufficient.Reolink Support: How to download firmware for a Reolink deviceUsed for checking model, hardware number, and firmware version before selecting a matching firmware file; a firmware update is not a general stream fix.Reolink: Introduction to RTSPUsed for the Reolink RTSP URL format (main vs sub stream) as a representative per-vendor pattern.Reolink Support: Introduction to Reolink Smart DetectionUsed for the on-camera detection categories (person on all cameras; vehicle on all except E1 Indoor and FE series; pet/animal by model and firmware; visitor and package on Video Doorbells) that run on the camera independently of Frigate.Frigate GitHub issue #3235: Reolink stream reliability (http vs rtsp)The historical discussion Frigate cites when recommending HTTP video for some Reolink models; individual hardware and firmware still require testing.Frigate discussion #22248: Duo 3 no frames and upstream timeout (2026-03-04)A dated single-installation report: go2rtc could not reach the camera after a Frigate update; its local restream then returned 404. Not proof of a Frigate version regression.Frigate discussion #24037: Reolink doorbell timeout and restream 404 (2026-08-19)A dated single-installation report showing an upstream RTSP timeout, go2rtc producer disconnect, and later local restream 404; no universal recovery fix was established.Frigate issue #6502: capture stalled after disconnect (2023-05-15)Historical Frigate 0.12 report: live go2rtc playback returned while recording and detection stayed stopped. The primary camera was Amcrest, so this is pipeline symptom evidence, not a current Reolink-specific bug.Frigate discussion #22660: RLC-810A direct RTSP 404 (2026-03-26)A dated single-installation report of a camera-side 404 for an h265Preview_01_sub path; used to distinguish direct-camera 404 from local go2rtc 404.Frigate discussion #23660: PoE doorbell RTSP outcome (2026-07-10)A dated single-installation report where HTTP-FLV failed but RTSP played; a counterexample to treating Frigate's transport table as a per-unit guarantee.

Diagnostic rule

1. Check the simplest signal first.
2. Change one thing at a time.
3. Prove the stream/reachability before deep config.
4. Stop when the evidence says the risk moved.

FAQ

Which stream should I use for Reolink in Frigate: RTSP or HTTP FLV?

Frigate recommends HTTP-FLV for 5MP or lower, RTSP for older 6MP-plus models, and enhanced H.265 HTTP-FLV with FFmpeg 8 or RTSP for certain newer 6MP-plus models. Confirm the exact model, hardware, firmware, codec, and installed software versions. If the recommended source fails, test the alternative on that camera; a July 2026 PoE doorbell report found RTSP working while HTTP-FLV would not load. The FLV URL shape is `http://CAMERA-IP/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=USER&password=PASS`; `_ext` or `_sub` names a lower-resolution stream when the model exposes it. Reolink NVR channels start at 0 and use NVR credentials.

Why does my 4K Reolink show no frames or a grey stream in Frigate?

First separate capture from playback: inspect go2rtc's stream and Frigate's FFmpeg logs, then probe the source codec. Reolink says its conventional FLV stream is H.264-only, but Frigate documents enhanced H.265 HTTP-FLV for certain newer cameras with FFmpeg 8. Older high-resolution models are routed to RTSP in Frigate's table. If go2rtc receives H.265 but the browser is grey, test an H.264 substream or another supported playback path; restreaming alone does not convert H.265 to H.264.

What should I check when FFmpeg reports 404 or the feed stops after a disconnect?

Look at the URL in the error. A 404 from the camera's `:554` URL calls for checking its RTSP path and whether that stream exists. A 404 from `127.0.0.1:8554` calls for checking the exact go2rtc stream name and its producer logs; an upstream timeout can also make that restream unavailable. After a disconnect, verify that recording segments and detect FPS resume, even if live view works. Recent reports show both failure patterns, but do not establish a universal reconnect fix.

Will CBR, Interframe Space 1x, or a firmware update fix a dropout?

Frigate recommends 'On, fluency first' (CBR) and 'Interframe Space 1x' when those controls are available. They can improve stream behavior, but they do not repair a wrong URL, unreachable camera, failed go2rtc producer, or unsupported codec. Record the model, hardware version, and firmware version first; only install firmware matched to that hardware after reviewing Reolink's release details and the actual failure.

Reolink cameras now have their own AI. Do I still need Frigate's detection?

They do different jobs, and they coexist. Reolink Smart Detection runs on the camera and tells person from vehicle from pet or animal (and visitor or package on doorbells); it drives the Reolink app's alerts, the camera's own recording filters, and the sensors exposed by Home Assistant's Reolink integration. Frigate never reads those results; it decodes the sub stream and runs its own detector (OpenVINO on an Intel iGPU, Hailo, and so on), which gives you zones, object tracking, review items, snapshots and the Frigate+ models. Keep the camera's detection on if you use the Reolink app or its Home Assistant sensors; it costs Frigate nothing. If you only use Frigate, it does not matter either way.

Can I use two-way talk on a Reolink doorbell or camera through Frigate?

Some newer models support it. Frigate documents an HTTP-FLV video source plus a separate RTSP source for two-way audio on models that support the backchannel. That RTSP source must not be prefixed with `ffmpeg:`. Verify the feature on the exact camera and firmware before treating the example as a guarantee.

Do all Reolink cameras work with Frigate?

No. Check Reolink's current CGI/RTSP/ONVIF matrix for the exact model and hardware version. Many wired PoE and plug-in Wi-Fi models support local streams; battery Wi-Fi cameras generally require a Home Hub, NVR kit cameras require an NVR, and 4G LTE models are listed as unsupported. There are exceptions: the E1 Pro supports standalone RTSP, Lumus support varies by hardware, and the second-generation Battery Video Doorbell supports standalone protocols in wired-power mode. Confirm the required hub or NVR and test the local stream before buying several units.

Planning a purchase?

We keep a source-backed, price-free comparison so you can buy once and right. No star ratings, every spec cited.

Local Cameras: ONVIF vs UniFi vs Cloud →

Get the deal & firmware alerts

Home Stack Field Notes: NAS deals, firmware changes worth acting on, restore-test reminders, and new decision guides — plus the capacity & backup sizing cheatsheets from our calculators. Unsubscribe anytime.

Subscribe on beehiiv