re: Update pg 3 - 43" bar information home assistant display now in beta!

quote:

---

really? this wont improve performance at all?

---

quote:

---

are there known issues with getting reolink cameras/home assistant/frigate all wired up and running smothly?

Yes. In fact, Reolink and Frigate is a notoriously finicky combination. Frigate developers have historically recommended against Reolink because of their non-standard streaming implementations.
GitHub

However, with the integration of go2rtc into Frigate and some specific configurations, you can build a rock-solid setup. If you just plug the RTSP URLs into Frigate like a standard camera, you will face dropped frames, ffmpeg crashes, and video smearing.

Here is exactly what breaks and how to engineer around it.

1. The Broken RTSP Implementation
Reolink's native RTSP streams are famously buggy. They frequently drop frames and stutter, which wreaks havoc on Frigate's object detection and causes the stream to constantly disconnect.
Reddit

The Fix: Abandon standard RTSP. Reolink's HTTP-FLV stream (which is essentially RTMP wrapped in HTTP) is significantly more reliable. When defining the camera in Frigate, point it to the HTTP stream and use the Reolink-specific input arguments:

input_args: preset-http-reolink

2. The 4K / H.265 Trap
If you are running 8MP/4K Reolink cameras (like the 810A, 820A, or Trackmix), Reolink forces H.265 encoding on the main stream. There is no toggle to switch back to H.264 for the high-res feed.

The Fix:

For Detection: Always use the camera's lower-resolution sub-stream (which is H.264) for Frigate's detect role.

For Recording/Restreaming: Ensure your Frigate server's hardware (like an Intel iGPU) supports H.265 decoding, and explicitly configure go2rtc to handle the H.265 HTTP-FLV feed.

3. I-Frame Interval Mismatches
Frigate relies on keyframes (I-frames) matching the frame rate so it can efficiently decode the stream for the Coral TPU or CPU to process. Reolink defaults to dynamic or mismatched intervals, which causes CPU spikes and missed detections.

The Fix: You have to log directly into the camera's web UI (the desktop client or app usually hides this). Under the stream settings, hardcode the Interframe Space to 1x. If your frame rate is 15 FPS, your I-frame interval must be 15.
Reddit

4. Overloading the Camera's CPU
Reolink cameras have relatively weak internal processors. If Frigate pulls a stream, your Home Assistant dashboard pulls a stream, and you open the mobile app, the camera's CPU will max out and the feed will lock up.

The Fix: Funnel everything through go2rtc.

Configure go2rtc in Frigate to pull exactly one main stream and one sub-stream from the camera via HTTP.

Configure Frigate's detect and record roles to pull from that local go2rtc restream (rtsp://127.0.0.1:8554/...).

Have Home Assistant pull the live view from the go2rtc WebRTC feed. This gives you near-zero latency on your dashboards without touching the camera itself.

Pro-tip: Even with this architecture, Reolinks are prone to memory leaks. It is highly recommended to enable the "Auto Reboot" feature in the camera's maintenance settings to restart the camera once a week at 3 AM.

5. Audio Desync Crashing ffmpeg
The audio stream from Reolinks can drift out of sync with the video or throw unsupported codec errors, causing the entire ffmpeg process for that camera to crash.

The Fix: If you don't absolutely need audio for recordings, strip it out in the stream arguments. If you do need it, you will likely need to configure go2rtc to transcode the audio to AAC (#audio=aac) to keep the pipeline stable.

---

quote:

---

I too am using that hurricane tracker card now lol.

---

quote:

---

Cad I’m sorry I just saw your question. Honestly I downloaded the app on my phone, set the cameras up and then told my claw what I was using the cameras for and let it go to work on the settings. But they work good for me. If there are better options I’d love to hear them tho.

---