Frigate on intel N100

Hardware
1

Good afternoon.
Has anyone managed to run Frigate normally on an Intel N100 processor
I have a Beeline mini PC with this processor and a HassOS system.
I can’t figure out the Frigate settings, namely

ffmpeg:
hwaccel_args:

There is a feeling that this processor does not have render.
Thanks.

Errors:
I waited a bit and got an error from the accelerator:

2023-04-11 14:55:02.634208631 [2023-04-11 22:55:02] [frigate.video](https://frigate.video/) ERROR : cam_1: Unable to read frames from ffmpeg process.
2023-04-11 14:55:02.634588133 [2023-04-11 22:55:02] [frigate.video](https://frigate.video/) ERROR : cam_1: ffmpeg process is not running. exiting capture thread...
2023-04-11 14:55:05.478806093 [2023-04-11 22:55:05] frigate.util ERROR : Unable to poll intel GPU stats: No device filter specified and no discrete/integrated i915 devices found
2023-04-11 14:55:09.266620115 [INFO] Starting go2rtc healthcheck service...
2023-04-11 14:55:20.366241795 [2023-04-11 22:55:20] watchdog.cam_kalitka ERROR : Ffmpeg process crashed unexpectedly for cam_kalitka.
2023-04-11 14:55:20.366571933 [2023-04-11 22:55:20] watchdog.cam_kalitka ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2023-04-11 14:55:20.367170572 [2023-04-11 22:55:20] ffmpeg.cam_1.detect ERROR : Guessed Channel Layout for Input Stream #0.1 : mono
2023-04-11 14:55:20.367203098 [2023-04-11 22:55:20] ffmpeg.cam_1.detect ERROR : Option hwaccel (use HW accelerated decoding) cannot be applied to output url vaapi -- you are trying to apply an input option to an output file or vice versa. Move this option before the file it belongs to.
2023-04-11 14:55:20.367250338 [2023-04-11 22:55:20] ffmpeg.cam_1.detect ERROR : Error parsing options for output file vaapi.
2023-04-11 14:55:20.367493996 [2023-04-11 22:55:20] ffmpeg.cam_1.detect ERROR : Error opening output files: Invalid argument
2023-04-11 14:55:22.620891817 [2023-04-11 22:55:22] [frigate.video](https://frigate.video/) ERROR : cam_1: Unable to read frames from ffmpeg process.
2023-04-11 14:55:22.622328450 [2023-04-11 22:55:22] [frigate.video](https://frigate.video/) ERROR : cam_1: ffmpeg process is not running. exiting capture thread...

my config:

mqtt:
  host: core-mosquitto
  user: mqtt
  password: mqttpsw

ffmpeg:
  hwaccel_args: preset-vaapi
detectors:
  ov:
    type: openvino
    device: AUTO
    model:
      path: /openvino-model/ssdlite_mobilenet_v2.xml

model:
  width: 300
  height: 300
  input_tensor: nhwc
  input_pixel_format: bgr
  labelmap_path: /openvino-model/coco_91cl_bkgr.txt
  
go2rtc:
  streams:
    rtsp_cam_1:
      - rtsp://10.10.0.49:554/user=admin_password=tlJwpbo6_channel=1_stream=0.sdp?real_stream
      - "ffmpeg:rtsp_cam_1#video=h264"

cameras:
  cam_1:
    ffmpeg:
      inputs:
        - path: rtsp://10.10.0.49:554/user=admin_password=tlJwpbo6_channel=1_stream=0.sdp?real_stream
          roles:
            - detect
    detect:
      width: 768
      height: 432
      fps: 3
    objects:
      track:
        - person
        - cat
        - dog
        - car
    motion:
      mask:
        - 768,0,619,0,627,54,627,155,615,262,598,392,586,432,768,432
    live:
      stream_name: rtsp_cam_1
2

I guess it is quite new still, maybe support will get there, eventually.
I am looking for new HW to run HA on, and the Beelink with N100 caught my interest. But Frigate is still a dealbreaker, it must work

3

I’m curious; have you guys had luck running Frigate on the N100 yet?

1 Like
4

Yes everything works fine for several months

1 Like
5

I got the same errors as you on top of this thread.
I am running the N100 on proxmox
How did you mange to solve it?

6

I recently installed Frigate on HAOS+ Proxmox and I have the same error. Have you solved the problem?

7

Any update on this one? Same config here: Proxmox, HAOS (VM), Frigate as HACS integration running on NUC N100

8

Have you guys tried to run Frigate separately from HA creating a dedicated Proxmox LXC container for frigate? The installation is very easy using tteck’s script which can be found here: https://helper-scripts.com/scripts?id=Frigate

After doing that you can add the frigate custom component via HACS which connects HA to Frigate running in the LXC.

Personally I have frigate running in a docker container on a separate Debian 12 host also connected to HA using the custom component. I have not tried the LXC on Proxmox yet because it is not recommended. Still there are installations on Proxmox that seem to run fine.

1 Like
9

Got it running. HAOS as VM, Frigate as Addon w. HACS.
I did one mistake, I forget to paththrough the GPU (Proxmox GUI, Hardware. add PCI Device, select GPU). With the additional config above everything is running well.

1 Like
10

I have HA on proxmox as VM. And I added the Frigate to HA. I try to add PCI and GPU.
Any of options to configure HW decoding don’t work for me.
I tried all option listen in documentation Hardware Acceleration | Frigate