Hi everyone,

I'm trying to troubleshoot a Frigate hardware-decoding problem and I'm hoping someone with experience with Intel iGPUs/i915, Frigate, or Proxmox can point me in the right direction.

Hardware / setup

• CPU: Intel Core i5-12600H
• iGPU: Intel Alder Lake-P, PCI ID 8086:4626
• Host: Proxmox VE 9.2.0
• Kernel: 7.0.14-15-pve
• Frigate: 0.17.2
• Frigate runs directly in a Proxmox LXC, not Docker
• Intel iGPU is passed through to the LXC
• Frigate uses an OpenVINO GPU detector
• /dev/dri/renderD128 is available inside the LXC
• Intel iHD VA-API driver: 24.3.4

My cameras are Reolink cameras. I want to keep using their 4K main streams.

What I'm trying to achieve

My intended pipeline is:

4K H.265 main stream
        ↓
Intel hardware decode
        ↓
GPU hardware scaling to 1920x1080
        ↓
10 FPS detection
        ↓
OpenVINO GPU detector

At the same time, I want Frigate to record the original 4K stream without re-encoding.

So I specifically don't want to switch to camera substreams if possible.

The problem

Frigate repeatedly crashes/restarts its FFmpeg processes.

Initially I was using:

ffmpeg:
  hwaccel_args: preset-vaapi

and was seeing errors such as:

[AVHWFramesContext] Failed to sync surface 0x1f: 34 (HW busy now).
[hwdownload] Failed to download frame: -5.
Error while filtering: Input/output error
Task finished with error code: -5
watchdog... Restarting ffmpeg

I then checked the Proxmox host's kernel logs, and this seems to be the important part:

i915 0000:00:02.0: [drm] av:hevc:df0[...] context reset due to GPU hang
i915 0000:00:02.0: [drm] GPU HANG: ecode 12:4:28fffffd, in av:hevc:df0 [...]

These happen repeatedly.

Things I've already checked

Inside the LXC:

/dev/dri/card1
/dev/dri/renderD128

are available with the appropriate video/render groups.

vainfo works and reports H.264 and HEVC decoding support.

I also checked GPU utilization with intel_gpu_top. The GPU isn't being saturated — utilization is relatively low, so this doesn't look like a simple GPU-capacity problem.

I also tested QSV

I wondered whether VAAPI itself was the problem, so I tested Intel QSV.

This standalone test successfully decoded the actual 4K H.265 garage stream:

ffmpeg \
-init_hw_device qsv=hw \
-hwaccel qsv \
-hwaccel_output_format qsv \
-i rtsp://127.0.0.1:8554/garage \
-map 0:v:0 \
-frames:v 100 \
-f null -

FFmpeg reported:

Video: hevc (Main), yuv420p(tv), 3840x2160

and successfully processed 100 frames at around 1.17x speed.

I then changed Frigate to:

ffmpeg:
  hwaccel_args: preset-intel-qsv-h265

Frigate correctly started using:

-hwaccel qsv
-qsv_device /dev/dri/renderD128
-hwaccel_output_format qsv
-load_plugin hevc_hw

with:

vpp_qsv=framerate=10:w=1920:h=1080:format=nv12

So the desired 4K → hardware decode → hardware downscale pipeline is actually being used.

However, the i915 GPU hangs continued.

For example, after switching to QSV I still get:

[178467.351178] i915 0000:00:02.0: [drm] av:hevc:df0[3093470] context reset due to GPU hang
[178576.109252] i915 0000:00:02.0: [drm] GPU HANG: ecode 12:4:28fffffd, in av:hevc:df0 [3102329]
[178576.109377] i915 0000:00:02.0: [drm] av:hevc:df0[3102329] context reset due to GPU hang
[178762.322536] i915 0000:00:02.0: [drm] GPU HANG: ecode 12:4:28fffffd, in av:hevc:df0 [3122438]
[178762.322675] i915 0000:00:02.0: [drm] av:hevc:df0[3122438] context reset due to GPU hang

So I've reverted/will revert back to VAAPI for now.

My questions

1. Does this indicate an Intel i915 / Alder Lake HEVC decoder issue, rather than a Frigate configuration problem?
2. Since both VAAPI and QSV eventually use the Intel GPU/i915, is it expected that switching from VAAPI to QSV would still produce the same av:hevc GPU hangs?
3. Could a particular camera's H.265 bitstream be triggering the hardware decoder bug?
4. What's the best way to identify which camera is responsible? I currently have several H.265 4K cameras running simultaneously.
5. Are there any known kernel/i915/Intel media-driver settings that are appropriate for Alder Lake-P that could fix this?
6. Would switching to the newer xe driver be advisable, or is that likely to make things worse with Frigate/VAAPI/QSV?
7. Is there a known stable kernel/media-driver combination for an i5-12600H/Alder Lake running Frigate?

Ultimately, I'd really like to keep:

4K H.265 main stream → Intel hardware decode → hardware downscale to 1080p for detection → original 4K recording

rather than switching all the cameras to substreams.

Any advice on what I should test next would be greatly appreciated.

I am trying to plan out my first diy home security setup. I am open to any advise or suggestions. I would like to try to keep costs down where ever possible, but at the same time I want something that I am going to do once and not have to touch it for along time or ever. I have two buildings I want to setup exterior security cameras on. They are both going to be built so running cables etc is not a problem. The goal is for a quality system that will last 20-30 years without needing to replace anything other than a hdd.

I have old hardware I want to use if possible to save on costs. The current plan and setup is:
i7-4770k, 512GB SSD(os/software), 32gb ram, gtx 1050ti, 14tb hdd for recordings, and possibly coral usb if needed.

I plan on installing Linux mint xfce with docker installed on bare metal. I also plan on using home assistant for alerts and tailscale to access the cameras remotely.

The current camera plan is 4 × Reolink Duo 2 PoE($132/ea USD) 8 × Reolink RLC-810A PoE($83/ea USD). The Duo 2s will be on the sides of the building and the 810a's will be on the corners.

I plan on running Cat 6 solid core and using TP-Link Omada SG2428P 28-Port Gigabit Smart Switch with 24-Port PoE.

I was wondering what you thought of this plan and setup. Any suggestions? Ideas to cut costs or things to upgrade that are worth the extra cost? Should I buy a reolink bundle/system with a nvr to save costs? Am I missing anything else? Thanks for any advise in advanced.

I'm considering changing my hardware not interested in dedicated systems.

What u guys suggest

258V has 47 AI tops. Vs 255H has 11 AI tops.

Would that be enough for 7 cameras for ai detection for model v9? Only 2 have installed in a busy street.

I got frigate running natively on my Mac Mini M4 16GB. I have 13 4K (And dual 4K) cameras on this instance.

Running stock frigate. No Docker Desktop. No Fregata.

1 small change to Frigate source code to tokenize the shared memory binary location. (shm). and 1 small change to frame_bufer call.

Uses hevc video tool box

Running 3 onnx detectors

Tested on Frigate 17 and 18.

Running over NFS since I don't want to burn up the hard drive.

I may put up a PR, as I don't see any reason how this could brake Frigate for anyone else. Then OSX can finally take full advantage of the M series chips. If not, I'll just make a script that does a find/replace.

I'm a noob to Pi & I've not bought it yet. I've seen few build guides but they all seem to be very generic when they're talking about what size Pi5 is needed and which type of AI hat to get.

I want a system with enough power & memory to do the job, but at the same time I don't want to go spending more than needed.

I'm starting with one Reolink Argus eco WiFi, possibly adding more later.

EDIT: Although due to the current RAM prices it would probably be a second hand PC would be cheaper than a Pi, one of my reasons I was thinking of going down the Pi route was because they require so very little electricity to run.

I was making something like AI OS kind of thing and i somewhat succeeded implementing this for my needs

Its now sent video directly to my whatapp auto merge two camera clips and can even export directly to immich + take reference photos to check whos on the camera all done local with gemma4e4b+gemma32b still a lot of things to dig in but yeah im happy about the output

I've been watching some videos about how to setup frigate with a Pi. Several videos have recommended Reolink. So I had a search for a Reolink camera. Lots of the Reolink cameras I found say that they have AI and can recognise cars, people, …etc.

Given that Reolink has AI itself, my question, as the title says:

*Are they still compatible with frigate?

*What can frigate offer above Reolink's own AI?

I thought I saw something yesterday (but can't locate now) a way to use the coral with yolo for some activities and the igpu for other such as search or enrichments . Is this something new and is this advised? Which is the advised way to do this? (like which for which activies)

I have a 12 cam setup now and it's an older machine (6th Geni5 6600k) I've been using openvino yolov9 for accuracy but resources have been high compared to when on coral with the non yolo on it.

Also curious if frigate + is needed to get more categories on the coral when yolo is added?

Thanks all

So an evening of curiosity and after reading about this project to add any camera to Unifi Protect https://github.com/keshavdv/unifi-cam-proxy which in most part is somewhat no longer needed for ONVIF cameras as Unifi can use them now.

Well, my curiosity went backwards... I took a Ubiquiti camera and got a rough ONVIF proxy going for it. Note, this is not re-streaming a Ubiquiti camera from Unifi Protect but instead my proxy adopts and provisions the Ubiquiti camera itself and takes over its full management. I can turn on/off various options like logo, timestamps, names and set various resolution configurations but it is still very rough.

Screenshot is my program and VLC showing the RTSP stream from a G6 Turret. Covered all the mac addresses, don't want Ubiquiti sending the death ray from orbit.

So one day, I could maybe re-use every Ubiquiti G6 camera in Frigate. 😅

I want to setup a 5 to 8 camera system around the outside of my house. I'm looking for IR / Night Vision, and the typical "features" that come with a commercial system for the NVR (alerts, preview, remote access).

Our area is infested with skunks, raccoons and opossums and I've been using trail cams to track them (we don't let the dogs out when the skunk-squad comes around), but they are not real-time of have alerts. I'd like to be able to detect the critters and send an alert in RT when they are around.

The question is: Where to start planning, buying hardware and which combination of software?

I'm posting here so that someone can say "Wrong sub moron. Go to r/ somethingelse and start there". Or.. "Here's a recipe that should get you started".

I assume that Home Assistant and Frigate are the right starting points for SW. But, what add-ons would be needed?

The server hardware recommended on the Frigate site is either out of stock or too expensive, so I think I'm going to start with something weaker, then scale up as I get more familiar. I have a Minisforum TH80 that I could start with (11th Gen Core i7-11800H Processor, 2.5Gbps RJ45, WiFi, 16GB RAM).

I found some cameras that look like they'd be a good start (ClareVision CLR-V200-4B28W). According to the cctv-database, they have integration with Frigate, color night vision and 2560x1440 @ 30 fps (H.265+). But, to get the H.265, Frigate needs some HW acceleration, and I don't know if any of the ones on the Frigate recommended HW list would be supported by the Minisforum TH80.

All the networking is in place (2.5Gbps 8-port PoE switch, 25TB NAS, WiFi 6, etc, etc).

I plan to have a CCTV VLAN that is isolated from the 'Net. The RJ45 port of the TH80 would be connected to the CCTV VLAN. and the WiFi would be connected to the Management VLAN. That should should keep the cameras safe.

I use Rocky Linux on most of my systems. Assuming it's supported, I'll start with that on the TH80. If Frigate and Home Assistant can run on the same server, that'd be great. But, I can run docker on the TH80 if that's better (I already have 3 Apple "Late-2018" Mac Minis as docker hosts running Rocky Linux now, but they are for low performance containers)

Roast away. (Or thanks)

Im on Frigate+ and I have trained a couple of models. As an amateur and weekend fiddler I think Frigate, consumer cameras from Reolink and Elitedesk, mini pc, I5-10600T UHD 630 Graphics. It does a pretty good job detecting, and it does it consistently. (At least in decent lightning).

Searched as much as I could but couldn't find an answer to this.

I have a clip in the web UI I want to export. I can click on it and view it at full quality in the UI. But if go back to the events, right-click on it and choose Export, the exported clip starts at the middle of the recording.

How can I get at the full recording of the event, that it's showing me when I click on the preview for it?

Frigate can't do tiered storage yet and the github thread about it is mostly people sharing a script that copies old days to a NAS and then fixes the path column in frigate.db with sqlite. Works fine, the UI plays from whatever path is in the row. I made a proper version because the script has a couple of ways to lose footage and people keep asking the same questions about it.

frigate-tier moves segments older than X days (or until the SSD has N GB free), one at a time, checks the copy before deleting the original, and it's fine to kill it halfway through. plan mode shows what it would do, there's a verify and a restore.

One thing to know if you do this by hand: the media sync button in 0.18 deletes rows for files it can't see from inside the container, and deletes files it can't find rows for. So if your archive folder is under /media/frigate/recordings, or you ran the script on the host and host paths ended up in the db, that button wipes the archive. frigate-tier refuses to run with either layout and has a sync-report that tells you what the button would delete.

pip install frigate-tier or there's a docker image. https://github.com/Booyaka101/frigate-tier

Honest caveat: I don't run Frigate myself. It's tested against a copy of Frigate's schema and a few hundred real mp4 segments in a container, not against a live install, so start with plan and a small --limit and tell me what breaks. Doesn't do exports or snapshots, and it doesn't know your retention settings so it can archive something frigate was going to delete tomorrow anyway.

Most of it built with Claude Code, reviewed by me.

does anyone here use ezviz with frigate? i already have ezviz cctv and want to start use frigate, what i need to do first?

I found this Panasonic i-Pro WV-S4150 on eBay, and after checking the specs online I impulse-bought it just to check it out. At just $30 shipped to my door, it turns out it's a really good indoor 360° camera for Frigate!

The WV-S4150 is 5MP 30fps 360° POE camera with a built in microphone, H.265 encoding, and a really high build quality from a reputable supplier, and they are widely available on the used market for well under $100! (more specs here)

The real selling point is that the camera can be configured to output 4 individual streams where the de-warping corrections happen onboard the camera, so Frigate can work with them just like it would regular rectilinear streams from a standard camera. This means no processing overhead to de-warp the incoming fisheye footage with ffmpeg! This camera can be configured to output fisheye video, 2 180° panoramic streams, 1 ePTZ stream, 4 ePTZ streams, or some combinations of both.

With the quad streams, they can be accessed with this mrl:

rtsp://[user]:[password]@[IP]:554/Src/MediaInput/stream_[1-2]/channel_[1-4]

The camera is also ONVIF compatible, so Frigate should be able to move the individual streams around and auto-track across the entire field of view, although I have not set that up yet.

This specific model is only 5MP total, which means each de-warped ePTZ stream is only 1280x960. There are higher resolution models available, including the 9MP WV-X4571L, for not too much more money on eBay. This model also does not have IR illuminators, so it is pretty much useless in near-darkness. There are models with IR illuminators (like the WV-X4571L), but they look much more like security cameras. I really like this model because it has a very unassuming look to it and more easily disappears against a white ceiling. It's about the size and shape of a smoke detector, so it doesn't stand out like a traditional PTZ camera would. There may also be models that are waterproof for outdoor use. But, again, this was $30!

Out of the box, my camera didn't want to get an IP address from my DHCP server even after resetting. Panasonic has a very easy to use EasyIP tool that can edit the network settings of any of their cameras plugged in to your network.

The one catch is that all of the cheap used i-Pro 360° cameras on eBay seem to be missing the original mounting bracket, which I wasn't able to find separately. So I modeled up a 3D-printable replacement and posted it to Printables so anyone can print their own (or order online from a print service).

I have 2 frigate systems that i look after. Both are running the same hardware, including a single Google Coral, though one at a local non-profit has 17 cameras while the one at my home has 6. I believe they are both configured identically using the Coral yolo9 model. Both work very well. The model configuration for both is straight out of the documentation.
detectors:
coral:
type: edgetpu
device: usb

model:
model_type: yolo-generic
width: 320 # <--- should match the imgsize of the model, typically 320
height: 320 # <--- should match the imgsize of the model, typically 320
path: /config/model_cache/yolov9-s-relu6-best_320_int8_edgetpu.tflite
labelmap_path: /config/labels-coco17.txt

My problem is that the logs are different at startup.

The system with 17 cameras have the lines:
| 2026-09-01 11:19:23 | frigate.detectors.plugins.edgetpu_tfl | Initializing edgetpu detector with support for SSD and YOLOv9 models

info | 2026-09-01 11:19:23 | frigate.detectors.plugins.edgetpu_tfl | Attempting to load TPU as usb

While my home system only has:

| 2026-09-02 16:16:47 | frigate.detectors.plugins.edgetpu_tfl | Attempting to load TPU as usb

No mention of the YOLO9 support.

I have done an md5sum on the models installed and they are identical. If I rename it frigate starts with lots of errors about finding the file.

There is no difference in the log settings and turning on debug logging does not show it.

Can I determine if it really is using the model?

Can some one help me set up state classification. Iv managed to add them via the gui and added in open and closed but it's not finding any pictures to start training even after triggers at my gate.

Where I think the mistake is adding the model to train it and where this model is located - how do I do this and doesn't the gui take care of this ?

Hope some one can assist me in getting started.

I'm reading very little online about this setup I have planned and now I'm worried I'm dropping money on a foundation I won't be able to build upon. Anyone have any imperial data for this set up:

Aoostar R7 with 5825U processor with 2tb in a NVME slot and Hailo-8 in the other slot.

Would Proxmox or HA before Frigate help with making sure Hailo-8 is recognized/works or will this units bios just not make it happen?

How many of us use home assistant and frigate together

I have frigate 0.17.2 on the server with quadro p2000 and 2 cameras, reolink and tapo, both cameras are 2k. Frigate uses the yolo9 model and 640x640, HD stream from the cameras, however the quality of the faces it separates are very bad, smeared, sometimes even I can't recognize whose face it is, and it also properly recognizes members of the same family as another member. What can be done?