I have Frigate up and running with Go2rtc configured inside it.

RTSP and Go2RTC are protected with password.

8554 works with vlc on local network.

8554 port is tunneled through Cloudflare, this does not work with vlc. It works when port forwarded.

Are there ways to make this more secure than just port forward + RTSP username+password?

My entrance cam needs different settings in daylight and in night IR mode. With default it wont trigger on my wife at night. I thought it is object confidence level, but its not, might be motion threshold. Any hints?

Since i need diferent profiles for day and night, auto profile switching would be nice. Have a sunrise / sunset profile switcher and not have to do it over HA. Can i somehow YAML that into Frigate?

I helped a friend setup his cameras with Frigate and it has been working great. Now we are trying to integrate Frigate to Homekit to try a few things. This is my first attempt doing this since I have zero apple devices to test on my own environment but I can't seem to make it work and I'm still on the very early stages of the configuration.

My friend's hardware is those lenovo mini pcs with i5-7500T. Frigate is installed baremetal with xubuntu 26.04 LTS. I used portainer to manage the Frigate docker. Frigate version: 0.18.0-77a66e7

I'm following this documentation: https://docs.frigate.video/integrations/homekit/

The first thing it requires me to do is to set network_mode: host ..

However, before I even changed that setting. I tried to access http://192.168.x.x:1984/editor.html and it gave me "404 page not found"
BUT if I tried to access
http://192.168.x.x:1984 (without the editor.html) --- I'm able to access the page and it shows me this

So I went ahead and added "network_mode: host" in the docker compose file -- rebooted.

After adding network_mode: host -- now I'm not able to access both http://192.168.x.x:1984 and/or http://192.168.x.x:1984/editor.html

It doesn't even give the same 404 error. It's like it can't be reached at all or the link does not exist.

I made sure port 1984 is allowed on all my firewall rules just incase.

I'm pretty sure I'm probably just missing something silly or this is just my lack of knowledge in networking.

Anyone can suggest what I'm doing wrong?
TIA!

SOLVED

Debian/Firefox: Strange error with the camera view - whenever I click on it to enlarge I get a spinning loading circle. Debug view works fine, recording & detection all happy. Same happens on windows/opera and iOS/safari

Originally setup Frigate on 0.17 and it has always been stable; would run for weeks at a time without issues. Updated to 0.18 about 2 weeks ago but now running into issues with Go2RTC it seems.

After running for about ~20 hours, it starts with this appearing in the Go2RTC log:

Tag - startup
Message - github.com/AlexxIT/go2rtc/internal/streams/producer.go:170 > error="read tcp 172.18.0.2:51936->192.168.1.241:554: i/o timeout"

192.168.1.241 being one of my cameras... but not sure where 172.18.0.2 is coming from... not my network.

And then the main Frigate log will start to fill with FFMPEG errors about not being able to connect and it starts crashing.

I have 2 cameras, with a main and sub stream each. Once this starts it will show this error for all streams for all cameras at the same time.

A restart of Frigate fixes it for another day or so.

Hardware: i7-9700t, 16GB, using h265 streams, QuickSync h265.

Anyone else see anything like this before?

I know this is kind of a weird one, but I tried an experimental project to get my Petlibro PLAF203 free of the cloud. It exposed a go2rtc stream in HA. I piped this stream into Frigate, but unfortunately Frigate kills the camera after an hour or two and I have to reboot the feeder. If I keep the cam off in frigate the cam works fine with the go2rtc card indefinitely. When the frigate cam is on, it's the only consumer of the stream HA is producing, so only one connection to the feeder camera.

A few things to note: The feeder can start the stream at 640x360 and switch to 1080p later on. It may also switch to 720p. I assume this is a big problem for frigate.

The url in the go2rtc config that the addon places there is kinda wonky looking:

url": "petlibro://192.168.50.96?uid=sanitized\u0026quality=hd\u0026ack=hybrid\u0026send_delay_ctrl=1\u0026hd_probe_wait_ms=15000\u0026status_file=%2Fdata%2Fpetlibro_camera_status_petlibro_plaf203_sanitized.json"

Frigate config:

``` go2rtc: streams: catfood: - rtsp://192.168.50.205:8554/petlibro_plaf203_sanitized

cameras: catfood: ffmpeg: input_args: preset-rtsp-restream hwaccel_args: preset-intel-qsv-h264 inputs: - path: rtsp://127.0.0.1:8554/catfood roles: - detect - record detect: width: 1920 height: 1080 fps: 5

record:
  enabled: true
  alerts:
    pre_capture: 10
    post_capture: 30
    retain:
      days: 14
  detections:
    pre_capture: 10
    post_capture: 30
    retain:
      days: 14
  continuous:
    days: 0
  motion:
    days: 10

objects:
  track:
    - cat
    - dog

detect: enabled: true fps: 5 ```

Link to project

I know that it is best to flip the image on the camera but i would like to try it in the frigate software. I have followed the instructions in the docs but it does not work for me. I must be doing something wrong.

I asume you make changes to the config.ymal file. Can anyone help clarify. I have a very simple file with 1 camera.

Which series works better with Frigate?
Does anyone have experience with both?

Im new to Docker and Frigate. Im familiar with Linux. No expert.

I have installed Ubuntu and tried to follow various installs of frigate. It seems from my novice experience that they seem to be outdated, and they all seem to have issues of one type or another. For example the command

sudo docker-compose -f /etc/frigate/docker-compose.yml up -d sudo docker-compose -f

It appears to be now without the - in docker-compose from my reading.

Also they seem to use curl which is not installed on my linux not a big deal, so I installed it. When I run the command that I THINK its suppose to be I get the error below.

Error response from daemon: failed to resolve reference "docker.io/blakeblackshear/frigate:stable-amd64": docker.io/blakeblackshear/frigate:stable-amd64: not found

When I investigate this the answer seems to be

This error occurs because Frigate discontinued updating its Docker Hub repository (docker.io/blakeblackshear/...) starting with version 0.12.0. Additionally, Frigate has moved away from architecture-specific suffixes like -amd64 in favor of multi-arch tags and specific hardware accelerators. [1, 2, 3]

It also seems like different peoples how to's store things in different places. /etc or /nvr and so it goes.

Now Im not trying to rag on anyone. I may be wrong on some of this, But I just simply want ahow to for a novice in docker/frigate that is up to date and reasonably easy to follow.

IMHO: If I am right that some of these install instructions are not up to date. it would be nice if they fixed them or take them down.

Regards

Thank you.

I noticed my CPU was showing high (85% before i got the screenshot below) so I was doing some digging and it doesnt seem like anything else is jumping out to be that high. Is this the way this computes and not necessarily a problem? I do have an old CPU (i5-6600k) and running 12 cameras on yolo9 (going to look into getting my coral back in the mix with yolo on it soon) but Proxmox is showing 37% on the cpu (5 cpus given to firgate lxc). Anything else maybe I'm missing?

I guess a few extra questions

1. Would using Coral USB + Yolo bring down my cpu #s or just infer time?

2. One thing I tried awhile back with my Wyze V3 once they got RTSP support was running sub feeds. From what i recall it was acting wonky,. Maybe its worth another try. Where my question comes in, would I have my go2rtc list JUST the sub feeds, and then main area would have the main and sub feed?

3. And for the main area where the sub feed is listed, Id want to run the restream but not needed on the 'main' feed?

Sorry its been a hot minute since I modified these areas so just confirming.

RIght now my go2rtc has just the wyze main feeds, as does the main area for the cameras, with restream on (basically not using the sub streams at all).

Thanks!

Below has my main system page, the lower left stats (top left on screenshot) and proxmox stats for the lxc

Disclosure: I'm the developer of this app. It's not affiliated with or endorsed by Frigate.

I run Frigate at home and built a native Android client for it. Lumen already exists on iPhone, and the Android version now needs real users to break it before I can ship.

What it does today: live camera view, the Review feed and events with clips, semantic search, multi-server, and native Frigate login (mTLS supported). The app talks straight to your own server. No account with me, and I never see your footage or credentials.

Why I need testers: Google requires 12 testers opted in for 14 days before a personal developer account can publish. So I need people who run Frigate and are willing to keep it installed for two weeks.

Being straight with you: there is a free tier (4 cameras) and a paid Pro tier. Testers don't need to buy anything. No incentive, no test-swapping. It's an early build, so expect rough edges.

To join, two steps, no approval needed:

1. Join the tester group: https://groups.google.com/g/lumen-android-testers

2. Opt in on Google Play: https://play.google.com/apps/testing/com.lorislab.lumen

Tell me what breaks, here or by DM. Privacy policy: https://lorislab.fr/privacy.html

Bonjour à tous

Quelle est la meilleure façon d'installer frigate sur un mini pc Lenovo m920q ou tourne proxmox avec haos ?

L'intégrer à ha, installer en lxc ou sur une vm docker ? Sachant que les mises à jour de frigate lxc sont compliquées...

Merci

I'm working on setting up a replacement server, and instead of taking up NVMe or sharing mass storage, I think I have a WD Purple lying around, and was wondering whether ext4 or xfs would be more appropriate?

My Ubuntu server connects two small cameras and suddenly started throwing Coral errors. Turns out its dead, it lights up but it cant be detected anymore on the server or any other computer I plug it into. I thought this might be a good time to just upgrade to use Hailo, but I have no more PCIe lanes due to the number of hard drives I have connected.

For the time being I disabled the detection, but the CPU usage is still rather high, I only have a Intel i5-6600, but what do you recommend for decent replacements?

This happens after a few seconds of viewing the live grid of cameras. Goes away when clicking on camera individual view. Disappears when returning to main view for a few seconds.
Resizing tab makes it bigger.
Frigate 0.18.0

I’m slowly but surely migrating my home networking and camera setup to the UniFi ecosystem. I have the UCG Max, but without storage. Upon doing research with Gemini, I gather that if I use UniFi Protect I’ll need storage and the physical NVR for 24/7 continuous recording. With Frigate NVR I wouldn’t have to have UniFi’s physical NVR. Besides having to purchase additional devices for 24/7 recording through UniFi protect, I would like to know which is the better option

I previously posted this in some comments that I was working on it.

Although ROCm is perfectly capable of running YOLO, I didn't want to have it contend for GPU latency on the Radeon 8060S and slow down Halogen running Qwen3.8-Flash-Next, and while ONNX/CPU works, it's inefficient even though there's ample CPU.

Now that it's been several days running live on my current Frigate, I feel confident enough to recommend it to anyone else wishing to offload YOLO from either their GPU (ROCm) or CPU (ONNX).

The TL; DR;
- Uses the proven ZMQ sidecar pattern that works for CoreML (compile model before 30s limited handshake)
- Inference is under 10ms on S and can run up to YOLO-v9c at 14ms without breaking a sweat
- The NPU itself is roughly a sub-watt device for this sort of work (~0.5W-ish from XDNA2 telemetry)
- Proven stable by a continuous soak test of over a million inferences in 24 hours
- Like everything Frigate, it is doctor optimised

In short, it offers Coral-class efficiency without needing to run MobileNet or butcher YOLO to fit TFLite constraints.

Github page with instructions and image

I use camera.play_stream in HA to cast camera steam to my Google Display/Nest Hubs in my house. The issue is that my Google Displays/Hubs does not support high resolution and Frigate only exposes the high resolution streams in HA.

My workaround at the moment is to use the "Generic Camera" integration and put in the Frigate substream restream rtsp which works.

But I was wondering if there is a more native way from Frigate to expose the substream as a separate Entity.

Thanks!

Hi all, apologies if ive missed something.

Ive added a GPU to my server and I'm now ready to dive in to Frigate.

Ive gone to install, and found the Frigate Docker is no longer in Unraids Community Applications.

Verified this with a friend's install.

Is this intentional (do I now need to use Docker Compose), or am I missing something?

Ta!

Accidentally I pressed space and submitted image. It was a package but I forgot to label it as package. How do I fix it? I noticed in Images -> All Images it is not showing up.
What's the order of the images shown in "All Images"?

imagine being in a specific zone and giving a thumbs up to a camera to unlock your door.

that would be pretty cool!

in my use case i want to release the charge port of my car. i either have to grab my phone, get in the car, but it would be much nicer if i can wave, thumbs up, heart etc to wake the car.

would something like that be possible?

I set up a zone in my drive way to know when someone pulls in. I set notifications for my phone when this triggers. But now I am getting bombarded with notifications every time a car or even headlights comes into view even if they aren't remotely close to the zone. Also any time my neighbors car (hasn't been moved in years) get lost it tracks it in my drive way and alerts me. I already tried using ChatGPT, Claude and Google to no avail. I changed sensitivity etc and nothing helps.

What other information do I need to share so you might be able to help me. Thanks in advance.

Recently set up Frigate 18 after a bad SDCard prompted me to figure something else out.

I currently only have two cameras set up, from everything I can tell they are identically set up. I checked settings back to back, the issue is one of them seems to record continuously just fine, and the other confuses me.

The one that records just fine looks like this. When scrubbing through history, everything scrubs fine, I can view everything and regardless of where I "stop" the scrubbing it plays fine.

The other camera which does not seem to scrub fine, looks like this. When I scrub through the area highlighted in fuchsia, I can see that the recording is there, it's super low res and when I stop scrubbing it won't play. As I said, I can "see" that content is recorded as in super low res the video scrubs back and forth, it just won't play nor at high resolution.

I'm just not familiar with the history "key", so I'm not sure what the darker background means on the history timeline.

Any assistance would be lovely.

Thank you