[Beta Support]: 0.18.0 - importing detector runtime error

[pdawg17]

Describe the problem you are having

Over the last handful of beta versions, I have started getting this error. I know it's 0.18.0 and errors are expected but just seeing if this is a known issue or if there is anything I can do to fix.

Beta Version

0.18.0:e23a57d-tensorrt

Issue Category

Object Detection / Detectors

Frigate config file

mqtt:
  enabled: true
  host: 192.168.xx.xx
  user: xxxx
  password: xxxx

ffmpeg:
  #hwaccel_args: preset-intel-qsv-h264
  hwaccel_args: preset-vaapi

detectors:
  ov:
    type: openvino
    device: GPU

model:
  model_type: yolo-generic
  width: 320
  height: 320
  input_tensor: nchw
  input_dtype: float
  input_pixel_format: bgr
  path: /config/model_cache/yolov9-t-320.onnx
  labelmap_path: /labelmap/coco-80.txt

go2rtc:
  streams:
    front_doorbell_main:
      - rtsp://admin:amcrest17@192.168.xx.xx/cam/realmonitor?channel=1&subtype=0#backchannel=0
    front_doorbell_sub:
      - rtsp://admin:amcrest17@192.168.xx.xx/cam/realmonitor?channel=1&subtype=1#backchannel=0
    garage_main:
      - rtsp://pdawg17:tplink17@192.168.xx.xx:554/stream1
    garage_sub:
      - rtsp://pdawg17:tplink17@192.168.xx.xx:554/stream2

  webrtc:
    candidates:
      - 192.168.xx.xx:8555
      - 192.168.xx.xx:8555

audio:
  enabled: true

snapshots:
  enabled: true
  clean_copy: true
  quality: 95

record:
  enabled: true
  alerts:
    retain:
      days: 7
  detections:
    retain:
      days: 7

cameras:
  front_doorbell_main: # <------ Name the camera
    enabled: true
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://127.0.0.1:8554/front_doorbell_main
          input_args: preset-rtsp-restream
          roles:
            - record
            - detect
        - path: rtsp://127.0.0.1:8554/front_doorbell_sub
          input_args: preset-rtsp-restream
          roles:
            - audio

    record:
      enabled: true
    detect:
      enabled: true # <---- disable detection until you have a working camera feed
      width: 1280
      height: 960
    objects:
      track:
        - person
        - dog
        - cat
        - bird

    zones:
      detect_zone:
        coordinates: 0,0.58,1,0.58,1,1,0,1
        enabled: true
        loitering_time: 0
        friendly_name: Detect zone
  garage_main:
    enabled: true
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://127.0.0.1:8554/garage_main
          input_args: preset-rtsp-restream
          roles:
            - record

        - path: rtsp://127.0.0.1:8554/garage_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
            - audio
    record:
      enabled: true
    detect:
      enabled: true
      width: 1280
      height: 720
      fps: 15
      annotation_offset: 0
    objects:
      track:
        - person
        - dog

    audio:
      listen:
        - bark
 
detect:
  enabled: true
version: 0.18-0
semantic_search:
  enabled: true
  model_size: large
face_recognition:
  enabled: true
  model_size: large
lpr:
  enabled: true
objects:
  genai:
    enabled: true

review:
  genai:
    enabled: true
    alerts: true
    detections: true
    image_source: preview # Options: "preview" (default) or "recordings"

classification:
  bird:
    enabled: true

genai:
  default:
    base_url: http://192.168.68.69:11434
    model: qwen3-vl:4b-instruct
    provider: ollama
    roles:
      - tools
      - vision
      - embeddings
    provider_options:
      keep_alive: -1m
    runtime_options: {}
audio_transcription:
  enabled: true
  device: GPU

Relevant Frigate log output

Error importing detector runtime: No providers found. Please make sure you have installed one of the following: ['AxEngineExecutionProvider', 'AXCLRTExecutionProvider']

Relevant go2rtc log output (if applicable)

No response

Install method

Docker Compose

docker-compose file or Docker CLI command

?

Operating system

Home Assistant OS

CPU / GPU / Hardware

No response

Screenshots

No response

Steps to reproduce

No response

Any other information that may be helpful

No response

[hawkeye217]

Yes, this is a known issue and was caused by #22206