search

blakeblackshear / frigate

NVR with realtime local object detection for IP cameras
https://frigate.video
MIT License
19.19k stars 1.75k forks source link

[HW Accel Support]: Frigate on intel N100 #6008

Closed Allkorolev closed 1 year ago

Allkorolev commented 1 year ago

Describe the problem you are having

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.

Version

12.0

Frigate config file

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

ffmpeg:
  hwaccel_args: preset-intel-qsv-h264
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

docker-compose file or Docker CLI command

-

Relevant log output

2023-04-12 03:27:23.796820626 [2023-04-12 11:27:23] frigate.app INFO : Starting Frigate (0.12.0-da3e197)
2023-04-12 03:27:23.808970413 [2023-04-12 11:27:23] frigate.config WARNING : Customizing more than a detector model path is unsupported.
2023-04-12 03:27:23.810240190 [2023-04-12 11:27:23] frigate.app INFO : Creating directory: /tmp/cache
2023-04-12 03:27:23.811576110 [2023-04-12 11:27:23] peewee_migrate INFO : Starting migrations
2023-04-12 03:27:23.814917966 [2023-04-12 11:27:23] peewee_migrate INFO : There is nothing to migrate
2023-04-12 03:27:23.840431613 [2023-04-12 11:27:23] frigate.app INFO : Output process started: 299
2023-04-12 03:27:23.840521880 [2023-04-12 11:27:23] frigate.comms.dispatcher INFO : Turning on snapshots for cam_1
2023-04-12 03:27:23.846325636 [2023-04-12 11:27:23] frigate.app INFO : Camera processor started for cam_1: 304
2023-04-12 03:27:23.847463591 [2023-04-12 11:27:23] frigate.app INFO : Capture process started for cam_1: 305
2023-04-12 03:27:23.852433086 [2023-04-12 11:27:23] detector.ov INFO : Starting detection process: 298
2023-04-12 03:27:23.872424255 [2023-04-12 11:27:23] frigate.video ERROR : cam_1: Unable to read frames from ffmpeg process.
2023-04-12 03:27:23.872427849 [2023-04-12 11:27:23] frigate.video ERROR : cam_1: ffmpeg process is not running. exiting capture thread...
2023-04-12 03:27:24.060263913 [2023-04-12 11:27:24] frigate.detectors.plugins.openvino INFO : Model Input Shape: {1, 300, 300, 3}
2023-04-12 03:27:24.060518461 [2023-04-12 11:27:24] frigate.detectors.plugins.openvino INFO : Model Output-0 Shape: {1, 1, 100, 7}
2023-04-12 03:27:24.060521274 [2023-04-12 11:27:24] frigate.detectors.plugins.openvino INFO : Model has 1 Output Tensors
2023-04-12 03:27:43.875075299 [2023-04-12 11:27:43] watchdog.cam_1 ERROR : Ffmpeg process crashed unexpectedly for cam_1.
2023-04-12 03:27:43.875437749 [2023-04-12 11:27:43] watchdog.cam_1 ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
2023-04-12 03:27:43.875841682 [2023-04-12 11:27:43] ffmpeg.cam_1.detect ERROR : [AVHWDeviceContext @ 0x558e9881c7c0] No VA display found for device -hwaccel_output_format.
2023-04-12 03:27:43.876167761 [2023-04-12 11:27:43] ffmpeg.cam_1.detect ERROR : Device creation failed: -22.
2023-04-12 03:27:43.876577907 [2023-04-12 11:27:43] ffmpeg.cam_1.detect ERROR : Failed to set value '-hwaccel_output_format' for option 'qsv_device': Invalid argument
2023-04-12 03:27:43.876610516 [2023-04-12 11:27:43] ffmpeg.cam_1.detect ERROR : Error parsing global options: Invalid argument
2023-04-12 03:27:43.899548807 [2023-04-12 11:27:43] frigate.video ERROR : cam_1: Unable to read frames from ffmpeg process.
2023-04-12 03:27:43.899858168 [2023-04-12 11:27:43] frigate.video ERROR : cam_1: ffmpeg process is not running. exiting capture thread...

FFprobe output from your camera

-

Operating system

HassOS

Install method

HassOS Addon

Network connection

Wired

Camera make and model

-

Any other information that may be helpful

No response

NickM-27 commented 1 year ago

I was helping over on reddit, still finding it quite odd. But if your system has a GPU which the specs say it does, then it should have a render node.

Can you again try

ffmpeg:
  hwaccel_args: preset-vaapi

environment_vars:
  LIBVA_DRIVER_NAME: i965

and paste the logs?

Allkorolev commented 1 year ago 
2023-04-13 03:39:36.692084176  [2023-04-13 11:39:36] frigate.app                    INFO    : Starting Frigate (0.12.0-da3e197)
2023-04-13 03:39:36.704426326  [2023-04-13 11:39:36] frigate.config                 WARNING : Customizing more than a detector model path is unsupported.
2023-04-13 03:39:36.705853142  [2023-04-13 11:39:36] frigate.app                    INFO    : Creating directory: /tmp/cache
2023-04-13 03:39:36.707235571  [2023-04-13 11:39:36] peewee_migrate                 INFO    : Starting migrations
2023-04-13 03:39:36.710261256  [2023-04-13 11:39:36] peewee_migrate                 INFO    : There is nothing to migrate
2023-04-13 03:39:36.720831996  [2023-04-13 11:39:36] frigate.app                    INFO    : Output process started: 303
2023-04-13 03:39:36.731056181  [2023-04-13 11:39:36] detector.ov                    INFO    : Starting detection process: 301
2023-04-13 03:39:36.732099055  [2023-04-13 11:39:36] frigate.app                    INFO    : Camera processor started for cam_1: 306
2023-04-13 03:39:36.738755159  [2023-04-13 11:39:36] frigate.app                    INFO    : Capture process started for cam_1: 307
2023-04-13 03:39:36.820515797  [2023-04-13 11:39:36] frigate.comms.dispatcher       INFO    : Turning on snapshots for cam_1
2023-04-13 03:39:36.864980727  [2023-04-13 11:39:36] frigate.comms.dispatcher       INFO    : Turning off detection for cam_1
2023-04-13 03:39:36.970459921  [2023-04-13 11:39:36] frigate.detectors.plugins.openvino INFO    : Model Input Shape: {1, 300, 300, 3}
2023-04-13 03:39:36.970463299  [2023-04-13 11:39:36] frigate.detectors.plugins.openvino INFO    : Model Output-0 Shape: {1, 1, 100, 7}
2023-04-13 03:39:36.970467130  [2023-04-13 11:39:36] frigate.detectors.plugins.openvino INFO    : Model has 1 Output Tensors
2023-04-13 03:39:38.340873357  [2023-04-13 11:39:38] frigate.video                  ERROR   : cam_1: Unable to read frames from ffmpeg process.
2023-04-13 03:39:38.341407533  [2023-04-13 11:39:38] frigate.video                  ERROR   : cam_1: ffmpeg process is not running. exiting capture thread...
2023-04-13 03:39:42.175380457  [2023-04-13 11:39:42] frigate.util                   ERROR   : Unable to poll intel GPU stats: No device filter specified and no discrete/integrated i915 devices found
2023-04-13 03:39:56.762348213  [2023-04-13 11:39:56] watchdog.cam_1           ERROR   : Ffmpeg process crashed unexpectedly for cam_1.
2023-04-13 03:39:56.762591390  [2023-04-13 11:39:56] watchdog.cam_1           ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2023-04-13 03:39:56.763466286  [2023-04-13 11:39:56] 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-13 03:39:56.763478216  [2023-04-13 11:39:56] ffmpeg.cam_1.detect      ERROR   : Error parsing options for output file vaapi.
2023-04-13 03:39:56.763483398  [2023-04-13 11:39:56] ffmpeg.cam_1.detect      ERROR   : Error opening output files: Invalid argument
2023-04-13 03:39:58.388002996  [2023-04-13 11:39:58] frigate.video                  ERROR   : cam_1: Unable to read frames from ffmpeg process.
2023-04-13 03:39:58.388578279  [2023-04-13 11:39:58] frigate.video                  ERROR   : cam_1: ffmpeg process is not running. exiting capture thread...
NickM-27 commented 1 year ago

yeah, I'm thinking this is an issue with the newer hardware and HA OS not having the iHD driver installed unfortunately

NickM-27 commented 1 year ago

Can you go to frigate_ip:5000/api/config and paste it here? That should give some info about the ffmpeg commands being used.

Allkorolev commented 1 year ago

This issue can be considered closed. It was about the drivers, after updating the Home Assistant OS, the drivers were added and everything worked stably.

SergiCEES commented 1 year ago

This issue can be considered closed. It was about the drivers, after updating the Home Assistant OS, the drivers were added and everything worked stably.

Hi Allkorolev, I'm considering the new Q12, but I need it to be able to manage 8 cameras on frigate. As you have it, could you help me to decide? Thanks!

Allkorolev commented 1 year ago

Hello, what can't be done?

Griddz commented 1 year ago

Hi @Allkorolev,I am also using the N100 Intel CPU for the HassOS system. However, I have been unable to utilize the GPU on the N100. Could you please share your detailed configuration file with me? Thank you very much!

kanocz commented 1 year ago

@Griddz you just need to make sure that your linux kernel version is 5.17 or better.... just tried with 6.4.4 and everything works, with 5.15 it was no /dev/dri/renderD128 device in system

osnwt commented 1 year ago

Confirming... Used Proxmox hypervisor v7 with old kernel 5.x, there was no such devices in LXC container with Frigate docker. After Promox was upgraded to v8 which uses kernel 6.x, everything started to work as it should.

dagbdagb commented 10 months ago

Looking at similar hw. What is the inference latency for the N100 using Openvino?

NickM-27 commented 10 months ago

Some users have reported 15-20ms

MaBeniu commented 10 months ago

image 8 cameras

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

it is gmktec g3 unit with Intel N100 overal load for all 4 cores is around 10-20%

dagbdagb commented 10 months ago

@MaBeniu 8 cameras, gpu at 7%, cpu at 10-20% ? That's impressive, I think.

bobloadmire commented 7 months ago

I'm having issues on proxmox. I'm running Frigate on LXC and preset-vaapi works fine, but QSV does not. I also have a Plex LXC installed, and QSV works fine on that, so it should have access to the same resources as that LXC. Where should I look to see whats wrong? Logs only show:

[2024-04-17 06:32:05] frigate.video ERROR : kitchen: Unable to read frames from ffmpeg process. [2024-04-17 06:32:05] frigate.video ERROR : kitchen: ffmpeg process is not running. exiting capture thread... [2024-04-17 06:32:15] watchdog.kitchen ERROR : Ffmpeg process crashed unexpectedly for kitchen. [2024-04-17 06:32:15] watchdog.kitchen ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2024-04-17 06:32:15] ffmpeg.kitchen.detect ERROR : [AVHWDeviceContext @ 0x581a3c41df00] Error setting child device handle: -17

NickM-27 commented 7 months ago

that is expected for qsv on the n100 for the version of ffmpeg that frigate uses. There is no advantage to qsv so I'd recommend just using vaapi

bobloadmire commented 7 months ago

that is expected for qsv on the n100 for the version of ffmpeg that frigate uses. There is no advantage to qsv so I'd recommend just using vaapi

it is? n100 QSV works great with plex LXC, so I just assumed it should work just fine with Frigate as well.

NickM-27 commented 7 months ago

frigate uses ffmpeg 5.0, alder lake generation needs ffmpeg 6.0+ to work with qsv. But there's no real benefit to doing that anyway since vaapi works better in some situations

bobloadmire commented 7 months ago

frigate uses ffmpeg 5.0, alder lake generation needs ffmpeg 6.0+ to work with qsv. But there's no real benefit to doing that anyway since vaapi works better in some situations

Thanks for the info. I was reading the QSV further reduces cpu overhead, and on the n100, everthing counts. is ffmpeg6+ on the frigate roadmap out of curiosity? I think you are also helping me on reddit. Thanks for your help.

NickM-27 commented 7 months ago

I was reading the QSV further reduces cpu overhead, and on the n100,

that is not the case for frigate's usecase. I have done many comparisons on a similar cpu to n100 and the CPU usage is identical. VAAPI also supports some features that qsv does not which makes it preferable

is ffmpeg6+ on the frigate roadmap out of curiosity?

a future version of frigate (not the next version) will likely move to ffmpeg 7.0 due to its change to support multithreading on filters and complex filters which will reduce cpu usage considerably

GroteGehaktBal commented 7 months ago

I am having problems with the n100. I can use vaapi just fine with cpu as detectors, but when I try changing detectors to openvino I'm getting errors. I am running home assistant os supervised and I can see /dev/dri/renderD128 in the container.

2024-04-17 20:12:48.200394016  22:12:48.200 INF go2rtc version 1.8.4 linux/amd64
2024-04-17 20:12:48.200831390  22:12:48.200 INF [api] listen addr=:1984
2024-04-17 20:12:48.200952244  22:12:48.200 INF [rtsp] listen addr=:8554
2024-04-17 20:12:48.201178582  22:12:48.201 INF [webrtc] listen addr=:8555
2024-04-17 20:12:49.197933718  [2024-04-17 22:12:49] frigate.app                    INFO    : Starting Frigate (0.13.2-6476f8a)
2024-04-17 20:12:49.198085050  [2024-04-17 22:12:49] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-04-17 20:12:49.217625270  [2024-04-17 22:12:49] frigate.config                 WARNING : Customizing more than a detector model path is unsupported.
2024-04-17 20:12:49.225926214  [2024-04-17 22:12:49] peewee_migrate.logs            INFO    : Starting migrations
2024-04-17 20:12:49.231070559  [2024-04-17 22:12:49] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-04-17 20:12:49.238372852  [2024-04-17 22:12:49] frigate.app                    INFO    : Recording process started: 308
2024-04-17 20:12:49.238817006  [2024-04-17 22:12:49] frigate.app                    INFO    : go2rtc process pid: 95
2024-04-17 20:12:49.261266884  [2024-04-17 22:12:49] frigate.app                    INFO    : Output process started: 320
2024-04-17 20:12:49.264942223  [2024-04-17 22:12:49] detector.ov                    INFO    : Starting detection process: 318
2024-04-17 20:12:49.287905630  [2024-04-17 22:12:49] frigate.app                    INFO    : Camera processor started for test: 325
2024-04-17 20:12:49.290421577  [2024-04-17 22:12:49] frigate.app                    INFO    : Capture process started for test: 327
2024-04-17 20:12:49.347843993  Abort was called at 349 line in file:
2024-04-17 20:12:49.347847584  ./shared/source/os_interface/linux/drm_neo.cpp
2024-04-17 20:12:49.347915449  Fatal Python error: Aborted
2024-04-17 20:12:49.347916706  
2024-04-17 20:12:49.347948363  Thread 0x00007f783ce806c0 (most recent call first):
2024-04-17 20:12:49.348238826    File "/usr/lib/python3.9/threading.py", line 312 in wait
2024-04-17 20:12:49.348657569    File "/usr/lib/python3.9/multiprocessing/queues.py", line 233 in _feed
2024-04-17 20:12:49.348957155    File "/usr/lib/python3.9/threading.py", line 892 in run
2024-04-17 20:12:49.349844013    File "/usr/lib/python3.9/threading.py", line 954 in _bootstrap_inner
2024-04-17 20:12:49.349846577    File "/usr/lib/python3.9/threading.py", line 912 in _bootstrap
2024-04-17 20:12:49.349850547  
2024-04-17 20:12:49.349851537  Current thread 0x00007f78667fd740 (most recent call first):
2024-04-17 20:12:49.349853284    File "/usr/local/lib/python3.9/dist-packages/openvino/runtime/ie_api.py", line 399 in compile_model
2024-04-17 20:12:49.349854858    File "/opt/frigate/frigate/detectors/plugins/openvino.py", line 32 in __init__
2024-04-17 20:12:49.349855983    File "/opt/frigate/frigate/detectors/__init__.py", line 18 in create_detector
2024-04-17 20:12:49.349874916    File "/opt/frigate/frigate/object_detection.py", line 53 in __init__
2024-04-17 20:12:49.349876369    File "/opt/frigate/frigate/object_detection.py", line 102 in run_detector
2024-04-17 20:12:49.349877632    File "/usr/lib/python3.9/multiprocessing/process.py", line 108 in run
2024-04-17 20:12:49.349878720    File "/usr/lib/python3.9/multiprocessing/process.py", line 315 in _bootstrap
2024-04-17 20:12:49.349900670    File "/usr/lib/python3.9/multiprocessing/popen_fork.py", line 71 in _launch
2024-04-17 20:12:49.349901964    File "/usr/lib/python3.9/multiprocessing/popen_fork.py", line 19 in __init__
2024-04-17 20:12:49.349913747    File "/usr/lib/python3.9/multiprocessing/context.py", line 277 in _Popen
2024-04-17 20:12:49.349914990    File "/usr/lib/python3.9/multiprocessing/context.py", line 224 in _Popen
2024-04-17 20:12:49.349916190    File "/usr/lib/python3.9/multiprocessing/process.py", line 121 in start
2024-04-17 20:12:49.349917310    File "/opt/frigate/frigate/object_detection.py", line 183 in start_or_restart
2024-04-17 20:12:49.349918638    File "/opt/frigate/frigate/object_detection.py", line 151 in __init__
2024-04-17 20:12:49.349919582    File "/opt/frigate/frigate/app.py", line 453 in start_detectors
2024-04-17 20:12:49.349920524    File "/opt/frigate/frigate/app.py", line 683 in start
2024-04-17 20:12:49.349933114    File "/opt/frigate/frigate/__main__.py", line 17 in <module>
2024-04-17 20:12:49.349934303    File "/usr/lib/python3.9/runpy.py", line 87 in _run_code
2024-04-17 20:12:49.349935325    File "/usr/lib/python3.9/runpy.py", line 197 in _run_module_as_main
2024-04-17 20:12:57.662447606  [INFO] Starting go2rtc healthcheck service...
2024-04-17 20:13:09.406189271  [2024-04-17 22:13:09] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting Frigate...
NickM-27 commented 7 months ago

looks like a driver issue or something. Given that you are running HA OS I am not sure there is much you can do

GroteGehaktBal commented 7 months ago

looks like a driver issue or something. Given that you are running HA OS I am not sure there is much you can do

I have now installed the docker image and hardware accel is now working as expected. Thank you.

cjcr commented 6 months ago

I am having problems with the n100. I can use vaapi just fine with cpu as detectors, but when I try changing detectors to openvino I'm getting errors. I am running home assistant os supervised and I can see /dev/dri/renderD128 in the container.

2024-04-17 20:12:48.200394016  22:12:48.200 INF go2rtc version 1.8.4 linux/amd64
2024-04-17 20:12:48.200831390  22:12:48.200 INF [api] listen addr=:1984
2024-04-17 20:12:48.200952244  22:12:48.200 INF [rtsp] listen addr=:8554
2024-04-17 20:12:48.201178582  22:12:48.201 INF [webrtc] listen addr=:8555
2024-04-17 20:12:49.197933718  [2024-04-17 22:12:49] frigate.app                    INFO    : Starting Frigate (0.13.2-6476f8a)
2024-04-17 20:12:49.198085050  [2024-04-17 22:12:49] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-04-17 20:12:49.217625270  [2024-04-17 22:12:49] frigate.config                 WARNING : Customizing more than a detector model path is unsupported.
2024-04-17 20:12:49.225926214  [2024-04-17 22:12:49] peewee_migrate.logs            INFO    : Starting migrations
2024-04-17 20:12:49.231070559  [2024-04-17 22:12:49] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-04-17 20:12:49.238372852  [2024-04-17 22:12:49] frigate.app                    INFO    : Recording process started: 308
2024-04-17 20:12:49.238817006  [2024-04-17 22:12:49] frigate.app                    INFO    : go2rtc process pid: 95
2024-04-17 20:12:49.261266884  [2024-04-17 22:12:49] frigate.app                    INFO    : Output process started: 320
2024-04-17 20:12:49.264942223  [2024-04-17 22:12:49] detector.ov                    INFO    : Starting detection process: 318
2024-04-17 20:12:49.287905630  [2024-04-17 22:12:49] frigate.app                    INFO    : Camera processor started for test: 325
2024-04-17 20:12:49.290421577  [2024-04-17 22:12:49] frigate.app                    INFO    : Capture process started for test: 327
2024-04-17 20:12:49.347843993  Abort was called at 349 line in file:
2024-04-17 20:12:49.347847584  ./shared/source/os_interface/linux/drm_neo.cpp
2024-04-17 20:12:49.347915449  Fatal Python error: Aborted
2024-04-17 20:12:49.347916706  
2024-04-17 20:12:49.347948363  Thread 0x00007f783ce806c0 (most recent call first):
2024-04-17 20:12:49.348238826    File "/usr/lib/python3.9/threading.py", line 312 in wait
2024-04-17 20:12:49.348657569    File "/usr/lib/python3.9/multiprocessing/queues.py", line 233 in _feed
2024-04-17 20:12:49.348957155    File "/usr/lib/python3.9/threading.py", line 892 in run
2024-04-17 20:12:49.349844013    File "/usr/lib/python3.9/threading.py", line 954 in _bootstrap_inner
2024-04-17 20:12:49.349846577    File "/usr/lib/python3.9/threading.py", line 912 in _bootstrap
2024-04-17 20:12:49.349850547  
2024-04-17 20:12:49.349851537  Current thread 0x00007f78667fd740 (most recent call first):
2024-04-17 20:12:49.349853284    File "/usr/local/lib/python3.9/dist-packages/openvino/runtime/ie_api.py", line 399 in compile_model
2024-04-17 20:12:49.349854858    File "/opt/frigate/frigate/detectors/plugins/openvino.py", line 32 in __init__
2024-04-17 20:12:49.349855983    File "/opt/frigate/frigate/detectors/__init__.py", line 18 in create_detector
2024-04-17 20:12:49.349874916    File "/opt/frigate/frigate/object_detection.py", line 53 in __init__
2024-04-17 20:12:49.349876369    File "/opt/frigate/frigate/object_detection.py", line 102 in run_detector
2024-04-17 20:12:49.349877632    File "/usr/lib/python3.9/multiprocessing/process.py", line 108 in run
2024-04-17 20:12:49.349878720    File "/usr/lib/python3.9/multiprocessing/process.py", line 315 in _bootstrap
2024-04-17 20:12:49.349900670    File "/usr/lib/python3.9/multiprocessing/popen_fork.py", line 71 in _launch
2024-04-17 20:12:49.349901964    File "/usr/lib/python3.9/multiprocessing/popen_fork.py", line 19 in __init__
2024-04-17 20:12:49.349913747    File "/usr/lib/python3.9/multiprocessing/context.py", line 277 in _Popen
2024-04-17 20:12:49.349914990    File "/usr/lib/python3.9/multiprocessing/context.py", line 224 in _Popen
2024-04-17 20:12:49.349916190    File "/usr/lib/python3.9/multiprocessing/process.py", line 121 in start
2024-04-17 20:12:49.349917310    File "/opt/frigate/frigate/object_detection.py", line 183 in start_or_restart
2024-04-17 20:12:49.349918638    File "/opt/frigate/frigate/object_detection.py", line 151 in __init__
2024-04-17 20:12:49.349919582    File "/opt/frigate/frigate/app.py", line 453 in start_detectors
2024-04-17 20:12:49.349920524    File "/opt/frigate/frigate/app.py", line 683 in start
2024-04-17 20:12:49.349933114    File "/opt/frigate/frigate/__main__.py", line 17 in <module>
2024-04-17 20:12:49.349934303    File "/usr/lib/python3.9/runpy.py", line 87 in _run_code
2024-04-17 20:12:49.349935325    File "/usr/lib/python3.9/runpy.py", line 197 in _run_module_as_main
2024-04-17 20:12:57.662447606  [INFO] Starting go2rtc healthcheck service...
2024-04-17 20:13:09.406189271  [2024-04-17 22:13:09] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting Frigate...

I can confirm the same problem with a N100 (Beelink Mini S ). With LXC container it works, but with HA OS it not. There is any solution for this? I will like to run the frigate inside the HAOS addons system.

joaofgf commented 6 months ago

is there a solution for this problem?

Emilef22 commented 1 month ago

someone found a solution?