N150小主机+飞牛OS+创米双摄Q2部署frigate0.15+人脸识别Doubletake+Deepstack

hoshea · 发表于 3 天前

本帖最后由 hoshea 于 2025-7-4 10:36 编辑

受论坛大神对frigate的经验启发，打算将门口摄像头接入到frigate并增加人脸识别功能，最终实现MQTT接入HA中。

目前实现人脸识别的方法有：
1.基于 Frigate 使用 Double Take 和 DeepStack 对视频监控进行人脸识别
2.frigate 0.16 beta3 版本已加入对人脸识别的支持。

1.本文将用到：
N150小主机一台
飞牛OS 0.9.12 Linux内核 6.12
创米双摄Q2 这款摄像头支持接入米家+RTSP/ONVIF推流+PTZ控制
人脸识别使用deepstack + double take

1.使用frigate监控 N150的CPU开销30%，监测速度在10ms，实际体验不会延迟很多。
2.此处无GPU监控是因为开了SR-IOV，在0.16版本才支持。

1.MQTT部署就不细说了，网上教程都很详细。
2.部署frigate
使用飞牛OS应用中心安装frigate应用，飞牛中的版本为0.14，N150需要0.15以上的版本，需要部署后修改Docker Compose文件


services:
  frigate:
    container_name: frigate
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    cap_add:
      - CAP_PERFMON
    image: ghcr.io/blakeblackshear/frigate:0.15.1
    shm_size: "512mb" # update for your cameras based on calculation above
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128 # For intel hwaccel, needs to be updated for your hardware
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/apps/docker-frigate/shares/config:/config
      - /var/apps/docker-frigate/shares/storage:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "15000:5000"
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
    environment:
      FRIGATE_RTSP_PASSWORD: "${wizard_password}"

然后在frigate开启后在Config Editor中输以上配置，重启。建议先按照官方步骤，确认摄像头接入无误后再添加其他内容。参考文档：https://docs.frigate-cn.video/

ui:
  timezone: Asia/Shanghai

mqtt:    #如果需要联动HA,需要安装mqtt服务器，文末有介绍
  enabled: true
  host: 192.168.123.237
  user: frigate
  password: frigate
go2rtc:
  streams:
# camera2:
#    - onvif://admin:[email protected]:8080
camera:
   - rtsp://admin:[email protected]:555/main_stream1  #枪机

ffmpeg:
  hwaccel_args: preset-intel-qsv-h265
detectors:
  ov:                #intel GPU推理使用
type: openvino
device: GPU
model: ###openvino使用，此模型容器自带
  width: 300
  height: 300
  input_tensor: nhwc
  input_pixel_format: bgr
  path: /openvino-model/ssdlite_mobilenet_v2.xml
  labelmap_path: /openvino-model/coco_91cl_bkgr.txt

cameras:
#  camera2: # <------ Name the camera
# enabled: true
# ffmpeg:
#    output_args:
#       record: preset-record-generic
#    inputs:
#       - path: rtsp://127.0.0.1:8554/camera2
#       input_args: preset-rtsp-restream-low-latency
# onvif:
#    host: 192.168.123.135
#    port: 8080
#    user: admin
#    password: HosheaXu2025
  camera: # <------ Name the camera
enabled: true
ffmpeg:
   output_args:
      record: preset-record-generic-audio-copy
   inputs:
      - path: rtsp://127.0.0.1:8554/camera
      input_args: preset-rtsp-restream-low-latency
      roles:
         - detect
         - record

detect:
   enabled: true
   width: 1280
   height: 720
   fps: 10
   annotation_offset: -1000
objects:
   track: #声明可用于跟踪的对象
      - person
      - dog
   mask:
      - 0.001,0,0.26,0.002,0.236,0.152,0.08,0.215,0.105,0.588,0.113,0.776,0.159,0.78,0.221,0.986,0.003,0.989
      - 0.993,0.004,0.562,0.005,0.404,0.007,0.549,0.392,0.71,0.612,0.907,0.89,0.994,0.935
zones: #zone不使用代码配置，但也可以事先设定一个不符合实际的，方便添加一些不可以在web添加的参数，zone区域之后在web修改
   camera-person: #区域名称，自定义
      coordinates:
      0.119,0.595,0.234,0.966,0.876,0.922,0.539,0.412,0.389,0.02,0.292,0.052,0.357,0.481,0.258,0.536,0.244,0.421,0.105,0.486 #此为区域坐标，需要在web修改，这里预设了一些不符实际的，只是方便添加参数
      loitering_time: 0
      objects: person #只跟踪人
      inertia: 3
      #filters: #filters过滤参数，默认参数对检测躺着的人不准确，可以按需修改如下的ratio比例
      #person:
         #min_ratio: 0.3
         #max_ratio: 3.0

motion: #motion不使用代码配置，但也可以事先设定一个不符合实际的，之后在web修改
   threshold: 30
   contour_area: 30
   improve_contrast: true

review: #回放选项
   alerts:  #告警片段仅记录特定区域中的特定对象
      required_zones:
      - camera-person
      labels:
      - person
snapshots: #快照仅记录特定区域
   required_zones:
      - camera-person
record:
   enabled: true
   retain:
      days: 14
      mode: all #此为14天全时录制
   alerts:
      retain:
      days: 7
      mode: motion #带运动的片段保留7天

version: 0.15-1

3.部署Doubletake Doubletake支持多种人脸识别，Deepstack简单部署即可上手，识别精度需要通过训练调优。以下教程指引出处：Doubletake部署


services:
  double-take:
    container_name: double-take
    image: skrashevich/double-take
    restart: unless-stopped
    volumes:
      - ./data:/.storage
    ports:
      - 3000:3000

4.部署deepstack


services:
  deepstack:
    image: deepquestai/deepstack
    container_name: deepstack
    restart: unless-stopped
    environment:
      - VISION-FACE=True
    volumes:
      - ./data:/datastore
    ports:
      - "5002:5000"

5.doubletake中配置config


mqtt:
  host: 192.168.123.xxx
  user: xxx
  password: xxx
  
  topics:
    frigate: frigate/events
    matches: double-take/matches
    cameras: double-take/cameras

detect:
  match:
    save: true
    # 最低置信度
    confidence: 60
    # 保留时间，单位是小时
    purge: 168
  unknown:
    save: true # 保留未识别的

frigate:
  url: http://192.168.123.xxx:xxx #填写frigate地址
  # 识别对象
  labels:
    - person
# 使用 deepstack 识别
detectors:
  deepstack:
    url: http://192.168.123.xxx:5002
    timeout: 15

最后无问题的话在MQTT WEB中查看doubletake给MQTT发的信息中包含double-take/matches 主题的就是成功了，再通过HA中的MQTT的自动发现，就能接入了。

本文参考：
万字经验，一文带你入门frigate AI监控
https://bbs.hassbian.com/thread-29310-1-1.html
基于 Frigate 使用 Double Take 和 DeepStack 对视频监控进行人脸识别

ck3 · 发表于昨天 10:32

大佬，我的也是n150, 和你一样的docker-compose启动，只配置了摄像头，不知道为啥就是调用不了gpu
也试过把hwaccel_args: preset-intel-qsv-h265 改成和你一样的，也都不行

version: "3.9"
services:
  frigate:
    container_name: frigate
    privileged: true
    restart: unless-stopped
    cap_add:
      - CAP_PERFMON
    image: ghcr.io/blakeblackshear/frigate:0.15.1
    shm_size: "512mb"
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128   
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ./config:/config
      - ./storage:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "8971:8971"
      - "6066:5000"
      - "8554:8554" # RTSP feeds

mqtt:
  enabled: true
  host: 192.168.1.XXX
  topic_prefix: frigate
  client_id: frigate
  user: [USERNAME]
  password: [PASSWORD]  

cameras:
  baby_camera: # <------ Name the camera
    enabled: true
    ffmpeg:
      hwaccel_args: preset-vaapi
      inputs:
        - path: rtsp://[USERNAME]:[PASSWORD]@192.168.1.XXX:554/cam/realmonitor?channel=1&subtype=1 # <----- The stream you want to use for detection
          roles:
            - detect           
            - audio
    detect:
      enabled: true # <---- disable detection until you have a working camera feed
      width: 1280
      height: 720
    audio:
      enabled: True
      listen:
        - crying
  keting_camera: # <------ Name the camera
    enabled: true
    ffmpeg:
      hwaccel_args: preset-vaapi
      inputs:
        - path: rtsp://[USERNAME]:[PASSWORD]@192.168.1.XXX:554/stream2 # <----- The stream you want to use for detection
          roles:
            - detect
    detect:
      enabled: true # <---- disable detection until you have a working camera feed
      width: 1280
      height: 720

record:
  enabled: True
  retain:
    days: 0
    mode: all
  events:
    retain:
      default: 30
      mode: motion    
 
version: 0.14

2025-07-04 14:19:34.425541880  [INFO] Preparing Frigate...
2025-07-04 14:19:34.548116979  [INFO] Starting Frigate...
2025-07-04 14:19:36.059145229  [2025-07-04 14:19:36] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2025-07-04 14:19:36.059198055  [2025-07-04 14:19:36] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-07-04 14:19:36.071325955  [2025-07-04 14:19:36] frigate.util.config            INFO    : frigate config does not need migration...
2025-07-04 14:19:36.143900430  [2025-07-04 14:19:36] frigate.util.services          WARNING : Did not detect hwaccel, using a GPU for accelerated video decoding is highly recommended
2025-07-04 14:19:36.171011396  [2025-07-04 14:19:36] peewee_migrate.logs            INFO    : Starting migrations
2025-07-04 14:19:36.171819678  [2025-07-04 14:19:36] peewee_migrate.logs            INFO    : There is nothing to migrate
2025-07-04 14:19:36.297970494  [2025-07-04 14:19:36] frigate.app                    INFO    : Recording process started: 345
2025-07-04 14:19:36.307215044  [2025-07-04 14:19:36] frigate.app                    INFO    : Recording process started: 348
2025-07-04 14:19:36.316414713  [2025-07-04 14:19:36] frigate.app                    INFO    : go2rtc process pid: 106
2025-07-04 14:19:36.345889410  [2025-07-04 14:19:36] detector.cpu                   INFO    : Starting detection process: 374
2025-07-04 14:19:36.354641944  [2025-07-04 14:19:36] frigate.app                    INFO    : Output process started: 376
2025-07-04 14:19:36.355356212  [2025-07-04 14:19:36] frigate.detectors              WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
2025-07-04 14:19:36.377988795  [2025-07-04 14:19:36] frigate.app                    INFO    : Camera processor started for baby_camera: 391
2025-07-04 14:19:36.395685556  [2025-07-04 14:19:36] frigate.app                    INFO    : Camera processor started for keting_camera: 396
2025-07-04 14:19:36.395689597  [2025-07-04 14:19:36] frigate.app                    INFO    : Capture process started for baby_camera: 406
2025-07-04 14:19:36.405162790  [2025-07-04 14:19:36] frigate.app                    INFO    : Capture process started for keting_camera: 413
2025-07-04 14:19:36.414710685  [2025-07-04 14:19:36] frigate.app                    INFO    : Audio process started: 421
2025-07-04 14:19:37.713023067  [2025-07-04 14:19:37] frigate.video                  ERROR   : baby_camera: Unable to read frames from ffmpeg process.
2025-07-04 14:19:37.713029788  [2025-07-04 14:19:37] frigate.video                  ERROR   : baby_camera: ffmpeg process is not running. exiting capture thread...
2025-07-04 14:19:38.330364969  [2025-07-04 14:19:38] frigate.video                  ERROR   : keting_camera: Unable to read frames from ffmpeg process.
2025-07-04 14:19:38.330484279  [2025-07-04 14:19:38] frigate.video                  ERROR   : keting_camera: ffmpeg process is not running. exiting capture thread...
2025-07-04 14:19:49.693086496  [2025-07-04 14:19:49] frigate.util.services          ERROR   : Unable to poll vainfo: b"error: XDG_RUNTIME_DIR is invalid or not set in the environment.\nerror: can't connect to X server!\nlibva info: VA-API version 1.17.0\nlibva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so\nlibva info: Found init function __vaDriverInit_1_17\nlibva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed\nlibva info: va_openDriver() returns 1\nlibva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so\nlibva info: Found init function __vaDriverInit_1_8\nlibva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed\nlibva info: va_openDriver() returns -1\nvaInitialize failed with error code -1 (unknown libva error),exit\n"
2025-07-04 14:19:56.433568366  [2025-07-04 14:19:56] watchdog.baby_camera           ERROR   : Ffmpeg process crashed unexpectedly for baby_camera.
2025-07-04 14:19:56.433771927  [2025-07-04 14:19:56] watchdog.baby_camera           ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2025-07-04 14:19:56.433983789  [2025-07-04 14:19:56] ffmpeg.baby_camera.detect      ERROR   : [AVHWDeviceContext @ 0x56171aa766c0] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
2025-07-04 14:19:56.434135902  [2025-07-04 14:19:56] ffmpeg.baby_camera.detect      ERROR   : [AVHWDeviceContext @ 0x56171aa766c0] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
2025-07-04 14:19:56.434343084  [2025-07-04 14:19:56] ffmpeg.baby_camera.detect      ERROR   : [AVHWDeviceContext @ 0x56171aa766c0] Failed to initialise VAAPI connection: -1 (unknown libva error).
2025-07-04 14:19:56.434459047  [2025-07-04 14:19:56] ffmpeg.baby_camera.detect      ERROR   : Device creation failed: -5.
2025-07-04 14:19:56.434543248  [2025-07-04 14:19:56] ffmpeg.baby_camera.detect      ERROR   : [h264 @ 0x56171aa75040] No device available for decoder: device type vaapi needed for codec h264.
2025-07-04 14:19:56.434684369  [2025-07-04 14:19:56] ffmpeg.baby_camera.detect      ERROR   : Device setup failed for decoder on input stream #0:0 : Input/output error
2025-07-04 14:19:56.445066266  [2025-07-04 14:19:56] watchdog.keting_camera         ERROR   : Ffmpeg process crashed unexpectedly for keting_camera.
2025-07-04 14:19:56.445354835  [2025-07-04 14:19:56] watchdog.keting_camera         ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2025-07-04 14:19:56.445359973  [2025-07-04 14:19:56] ffmpeg.keting_camera.detect    ERROR   : [AVHWDeviceContext @ 0x562c4c634d00] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
2025-07-04 14:19:56.445546744  [2025-07-04 14:19:56] ffmpeg.keting_camera.detect    ERROR   : [AVHWDeviceContext @ 0x562c4c634d00] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
2025-07-04 14:19:56.445550510  [2025-07-04 14:19:56] ffmpeg.keting_camera.detect    ERROR   : [AVHWDeviceContext @ 0x562c4c634d00] Failed to initialise VAAPI connection: -1 (unknown libva error).
2025-07-04 14:19:56.445707466  [2025-07-04 14:19:56] ffmpeg.keting_camera.detect    ERROR   : Device creation failed: -5.
2025-07-04 14:19:56.445711289  [2025-07-04 14:19:56] ffmpeg.keting_camera.detect    ERROR   : [h264 @ 0x562c4c635340] No device available for decoder: device type vaapi needed for codec h264.
2025-07-04 14:19:56.445795025  [2025-07-04 14:19:56] ffmpeg.keting_camera.detect    ERROR   : Device setup failed for decoder on input stream #0:0 : Input/output error
2025-07-04 14:19:57.671752069  [2025-07-04 14:19:57] frigate.video                  ERROR   : baby_camera: Unable to read frames from ffmpeg process.
2025-07-04 14:19:57.672008844  [2025-07-04 14:19:57] frigate.video                  ERROR   : baby_camera: ffmpeg process is not running. exiting capture thread...
2025-07-04 14:19:58.382327894  [2025-07-04 14:19:58] frigate.video                  ERROR   : keting_camera: Unable to read frames from ffmpeg process.
2025-07-04 14:19:58.382477175  [2025-07-04 14:19:58] frigate.video                  ERROR   : keting_camera: ffmpeg process is not running. exiting capture thread...
2025-07-04 14:20:01.867101788  [2025-07-04 14:20:01] frigate.util.services          ERROR   : Unable to poll vainfo: b"error: XDG_RUNTIME_DIR is invalid or not set in the environment.\nerror: can't connect to X server!\nlibva info: VA-API version 1.17.0\nlibva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so\nlibva info: Found init function __vaDriverInit_1_17\nlibva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed\nlibva info: va_openDriver() returns 1\nlibva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so\nlibva info: Found init function __vaDriverInit_1_8\nlibva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed\nlibva info: va_openDriver() returns -1\nvaInitialize failed with error code -1 (unknown libva error),exit\n"
2025-07-04 14:20:06.449911295  [2025-07-04 14:20:06] watchdog.baby_camera           ERROR   : Ffmpeg process crashed unexpectedly for baby_camera.
2025-07-04 14:20:06.450184883  [2025-07-04 14:20:06] watchdog.baby_camera           ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2025-07-04 14:20:06.450383860  [2025-07-04 14:20:06] ffmpeg.baby_camera.detect      ERROR   : [AVHWDeviceContext @ 0x5632bd916480] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
2025-07-04 14:20:06.450550158  [2025-07-04 14:20:06] ffmpeg.baby_camera.detect      ERROR   : [AVHWDeviceContext @ 0x5632bd916480] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
2025-07-04 14:20:06.450722645  [2025-07-04 14:20:06] ffmpeg.baby_camera.detect      ERROR   : [AVHWDeviceContext @ 0x5632bd916480] Failed to initialise VAAPI connection: -1 (unknown libva error).
2025-07-04 14:20:06.450823403  [2025-07-04 14:20:06] ffmpeg.baby_camera.detect      ERROR   : Device creation failed: -5.
2025-07-04 14:20:06.450968661  [2025-07-04 14:20:06] ffmpeg.baby_camera.detect      ERROR   : [h264 @ 0x5632bd81d540] No device available for decoder: device type vaapi needed for codec h264.
2025-07-04 14:20:06.451098816  [2025-07-04 14:20:06] ffmpeg.baby_camera.detect      ERROR   : Device setup failed for decoder on input stream #0:0 : Input/output error
2025-07-04 14:20:06.468881779  [2025-07-04 14:20:06] watchdog.keting_camera         ERROR   : Ffmpeg process crashed unexpectedly for keting_camera.
2025-07-04 14:20:06.469008093  [2025-07-04 14:20:06] watchdog.keting_camera         ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2025-07-04 14:20:06.475011951  [2025-07-04 14:20:06] ffmpeg.keting_camera.detect    ERROR   : [AVHWDeviceContext @ 0x560aef126840] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
2025-07-04 14:20:06.475285146  [2025-07-04 14:20:06] ffmpeg.keting_camera.detect    ERROR   : [AVHWDeviceContext @ 0x560aef126840] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
2025-07-04 14:20:06.475444522  [2025-07-04 14:20:06] ffmpeg.keting_camera.detect    ERROR   : [AVHWDeviceContext @ 0x560aef126840] Failed to initialise VAAPI connection: -1 (unknown libva error).
2025-07-04 14:20:06.475448428  [2025-07-04 14:20:06] ffmpeg.keting_camera.detect    ERROR   : Device creation failed: -5.
2025-07-04 14:20:06.475615325  [2025-07-04 14:20:06] ffmpeg.keting_camera.detect    ERROR   : [h264 @ 0x560aef136a00] No device available for decoder: device type vaapi needed for codec h264.
2025-07-04 14:20:06.475632614  [2025-07-04 14:20:06] ffmpeg.keting_camera.detect    ERROR   : Device setup failed for decoder on input stream #0:0 : Input/output error
2025-07-04 14:20:07.870371187  [2025-07-04 14:20:07] frigate.video                  ERROR   : baby_camera: Unable to read frames from ffmpeg process.
2025-07-04 14:20:07.870495704  [2025-07-04 14:20:07] frigate.video                  ERROR   : baby_camera: ffmpeg process is not running. exiting capture thread...
2025-07-04 14:20:08.177229499  [2025-07-04 14:20:08] frigate.video                  ERROR   : keting_camera: Unable to read frames from ffmpeg process.
2025-07-04 14:20:08.177384176  [2025-07-04 14:20:08] frigate.video                  ERROR   : keting_camera: ffmpeg process is not running. exiting capture thread...
2025-07-04 14:20:16.465668904  [2025-07-04 14:20:16] watchdog.baby_camera           ERROR   : Ffmpeg process crashed unexpectedly for baby_camera.
2025-07-04 14:20:16.465674711  [2025-07-04 14:20:16] watchdog.baby_camera           ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2025-07-04 14:20:16.465678019  [2025-07-04 14:20:16] ffmpeg.baby_camera.detect      ERROR   : [AVHWDeviceContext @ 0x5640b5a6f140] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
2025-07-04 14:20:16.465680762  [2025-07-04 14:20:16] ffmpeg.baby_camera.detect      ERROR   : [AVHWDeviceContext @ 0x5640b5a6f140] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
2025-07-04 14:20:16.465683579  [2025-07-04 14:20:16] ffmpeg.baby_camera.detect      ERROR   : [AVHWDeviceContext @ 0x5640b5a6f140] Failed to initialise VAAPI connection: -1 (unknown libva error).
2025-07-04 14:20:16.465685636  [2025-07-04 14:20:16] ffmpeg.baby_camera.detect      ERROR   : Device creation failed: -5.
2025-07-04 14:20:16.466360610  [2025-07-04 14:20:16] ffmpeg.baby_camera.detect      ERROR   : [h264 @ 0x5640b591c100] No device available for decoder: device type vaapi needed for codec h264.
2025-07-04 14:20:16.466537270  [2025-07-04 14:20:16] ffmpeg.baby_camera.detect      ERROR   : Device setup failed for decoder on input stream #0:0 : Input/output error
2025-07-04 14:20:16.483099026  [2025-07-04 14:20:16] watchdog.keting_camera         ERROR   : Ffmpeg process crashed unexpectedly for keting_camera.
2025-07-04 14:20:16.483414735  [2025-07-04 14:20:16] watchdog.keting_camera         ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2025-07-04 14:20:16.483420102  [2025-07-04 14:20:16] ffmpeg.keting_camera.detect    ERROR   : [AVHWDeviceContext @ 0x558ba337bcc0] libva: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
2025-07-04 14:20:16.483667038  [2025-07-04 14:20:16] ffmpeg.keting_camera.detect    ERROR   : [AVHWDeviceContext @ 0x558ba337bcc0] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
2025-07-04 14:20:16.483672275  [2025-07-04 14:20:16] ffmpeg.keting_camera.detect    ERROR   : [AVHWDeviceContext @ 0x558ba337bcc0] Failed to initialise VAAPI connection: -1 (unknown libva error).
2025-07-04 14:20:16.483794376  [2025-07-04 14:20:16] ffmpeg.keting_camera.detect    ERROR   : Device creation failed: -5.
2025-07-04 14:20:16.483855590  [2025-07-04 14:20:16] ffmpeg.keting_camera.detect    ERROR   : [h264 @ 0x558ba337ec00] No device available for decoder: device type vaapi needed for codec h264.
2025-07-04 14:20:16.483996208  [2025-07-04 14:20:16] ffmpeg.keting_camera.detect    ERROR   : Device setup failed for decoder on input stream #0:0 : Input/output error
2025-07-04 14:20:17.423449705  [2025-07-04 14:20:17] frigate.util.services          ERROR   : Unable to poll vainfo: b"error: XDG_RUNTIME_DIR is invalid or not set in the environment.\nerror: can't connect to X server!\nlibva info: VA-API version 1.17.0\nlibva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so\nlibva info: Found init function __vaDriverInit_1_17\nlibva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed\nlibva info: va_openDriver() returns 1\nlibva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so\nlibva info: Found init function __vaDriverInit_1_8\nlibva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed\nlibva info: va_openDriver() returns -1\nvaInitialize failed with error code -1 (unknown libva error),exit\n"
2025-07-04 14:20:17.784376409  [2025-07-04 14:20:17] frigate.video                  ERROR   : baby_camera: Unable to read frames from ffmpeg process.
2025-07-04 14:20:17.784574030  [2025-07-04 14:20:17] frigate.video                  ERROR   : baby_camera: ffmpeg process is not running. exiting capture thread...
2025-07-04 14:20:18.750803535  [2025-07-04 14:20:18] frigate.video                  ERROR   : keting_camera: Unable to read frames from ffmpeg process.
2025-07-04 14:20:18.751066079  [2025-07-04 14:20:18] frigate.video                  ERROR   : keting_camera: ffmpeg process is not running. exiting capture thread...

slwl · 发表于昨天 13:59

frigate的ssl证书问题怎么解决呢25-07-05 05:59:06 error: An error occurred when recogniting file: frigate status error: self-signed certificate
25-07-05 05:59:10 error: An error occurred at Error: frigate status error: self-signed certificate

slwl · 发表于昨天 14:35

ssl问题解决了。关闭即可，但是认证失败了。现在的firgate是有webui的用户的。正确输入提示错误

itispip · 发表于 4 小时前

ck3 发表于 2025-7-5 10:32
大佬，我的也是n150, 和你一样的docker-compose启动，只配置了摄像头，不知道为啥就是调用不了gpu
也试过把 ...

同问。也是只能使用vaapi

		自动登录	找回密码
密码			立即注册

[进阶教程] N150小主机+飞牛OS+创米双摄Q2部署frigate0.15+人脸识别Doubletake+Deepstack