[Config Support]: MSE not available for one camera

[MrKohli]

Describe the problem you are having

Hey everyone!

I have spent most of the weekend trying to solve this issue but I just can't find what is causing this behavior.
My problem is the following: I have set up 3 cameras Fisch, Einfahrt and Garten.
All 3 are set up to run through go2rtc which also works perfectly fine for Fisch and Garten, but Einfahrts stream is still running over jsmpeg instead of MSE.

The stream coming out of go2rtc works perfectly in VLC, ffplay or the go2rtc web interface.

Thanks in advance for any help!

Version

0.16.2-4d58206

Frigate config file

mqtt:
  enabled: true
  host: 192.x.x.x
  user: frigate_user
  password: frigate_password

detectors:
  onnx:
    type: onnx

model:
  model_type: yolox
  width: 640
  height: 640
  input_tensor: nchw
  input_dtype: float_denorm
  path: /config/model_cache/yolox_l.onnx
  labelmap_path: /labelmap/coco-80.txt
  attributes_map:
    person:
      - face
    car:
      - license_plate

objects:
  track:
    - person
    - cat
    - car

lpr:
  enabled: true
  known_plates:
    car1:
      - 'licence plate'
    car2:
      - 'licence plate'

go2rtc:
  streams:
    fisch:
      - ffmpeg:rtsp://192.x.x.51/ch0_0.h264#video=h264#hardware#audio=aac
    einfahrt1:
      - ffmpeg:rtsp://Camera1User:[email protected]:88/videoMain#video=copy#hardware
    garten:
      - ffmpeg:rtsp://Camera2User:[email protected]:554/h264Preview_01_main#video=h264#hardware#audio=aac
  webrtc:
    candidates:
      - stun:8555

cameras:
# --- Fisch Kamera ---
  fisch: # <------ Name the camera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/fisch  # <----- The stream you want to use for detection
          input_args: preset-rtsp-restream
          roles:
            - record
            - detect
      hwaccel_args: preset-nvidia
    detect:
      enabled: true # <---- disable detection until you have a working camera feed
    lpr:
      enabled: false
    record:
      enabled: true
      retain:
        days: 3
        mode: motion
      alerts:
        retain:
          days: 30
          mode: motion
      detections:
        retain:
          days: 30
          mode: motion
    motion:
      threshold: 40
      contour_area: 50
      lightning_threshold: 0.8
      improve_contrast: true
      mask:
        - 0.025,0.053,0.263,0.048,0.263,0.088,0.026,0.087
        - 0.572,0,0.591,0.706,0.866,0.694,0.876,0.676,0.998,0.663,0.987,0.328,0.935,0
  einfahrt: # <------ Name the camera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/einfahrt1  # <----- The stream you want to use for recording
          input_args: preset-rtsp-restream
          roles:
            - record
            - detect
#        - path: rtsp://127.0.0.1:8554/einfahrt2  # <----- The stream you want to use for detection
#          input_args: preset-rtsp-restream
#          roles:
#            - detect
      hwaccel_args: preset-nvidia
    detect:
      enabled: true # <---- disable detection until you have a working camera feed
    motion:
      threshold: 30
      contour_area: 30
      improve_contrast: true
      mask:
        - 0.241,0.043,0,0.04,0,0,0.241,0
        - 0.487,0.002,0.492,0.133,0.819,0.158,0.83,0
        - 0,0.153,0.123,0.101,0.118,0.04,0,0.039
    zones:
      Einfahrt:
        coordinates: 0.471,0.134,0.509,0.998,0.998,0.999,1,0,0.832,0,0.819,0.159
        loitering_time: 0
        inertia: 3
      Tuere:
        coordinates: 
          0.053,1,0.502,1,0.484,0.45,0.274,0.48,0.053,0.525,0.036,0.408,0,0.145,0,0.854
        loitering_time: 0
        objects:
          - cat
          - person
      Garten:
        coordinates: 
          0.056,0.534,0.166,0.499,0.119,0.002,0.001,0.001,0,0.14,0.033,0.425,0.041,0.442
        loitering_time: 0
    record:
      enabled: true
      retain:
        days: 3
        mode: motion
      alerts:
        retain:
          days: 30
          mode: motion
      detections:
        retain:
          days: 30
          mode: motion
    objects:
      mask:
        - 0.492,0.129,0.817,0.159,0.828,0.001,0.486,0.002
        - 0,0.152,0.126,0.098,0.122,0,0,0
      track:
        - cat
        - person
        - car
# --- Garten ---
  garten: # <------ Name the camera
    enabled: true
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/garten  # <----- The stream you want to use for detection
          input_args: preset-rtsp-restream
          roles:
            - record
            - detect
      hwaccel_args: preset-nvidia
    lpr:
      enabled: false
    detect:
      enabled: true
    onvif:
      host: 192.x.x.8
      user: Camera2User
      password: Camera2Password
    motion:
      mask:
        - 0.29,0.032,0.291,0,0,0,0,0.03
        - 0.2,0.391,1,0.58,1,0.334,0.459,0.211,0,0.257,0.002,0.453
      threshold: 30
      contour_area: 20
      improve_contrast: true
    record:
      enabled: true
      retain:
        days: 3
        mode: motion
      alerts:
        retain:
          days: 30
          mode: motion
      detections:
        retain:
          days: 30
          mode: motion
    objects:
      mask: 0.2,0.391,1,0.58,1,0.334,0.459,0.211,0,0.257,0.002,0.453
    zones:
      Pool:
        coordinates: 
          0.019,0.533,0.162,0.697,0.281,0.813,0.48,0.966,0.616,0.808,0.728,0.651,0.739,0.517,0.2,0.39,0.007,0.455
        loitering_time: 0
        objects:
          - cat
          - person
      Garten:
        coordinates: 
          0.73,0.653,0.739,0.519,1,0.582,1,1,0,1,0,0.459,0.007,0.459,0.019,0.536,0.147,0.682,0.285,0.818,0.479,0.971,0.635,0.784
detect:
  enabled: true
semantic_search:
  enabled: true
  model_size: large
face_recognition:
  enabled: true
  model_size: large
classification:
  bird:
    enabled: false
version: 0.16-0

Relevant Frigate log output

2025-10-19 18:20:17.020159420  [INFO] Preparing Frigate...
2025-10-19 18:20:17.679427873  [INFO] Starting Frigate...
2025-10-19 18:20:21.853759975  [2025-10-19 18:20:21] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-10-19 18:20:21.920609902  [2025-10-19 18:20:21] frigate.util.config            INFO    : frigate config does not need migration...
2025-10-19 18:20:23.446648666  [2025-10-19 18:20:23] frigate.util.services          INFO    : Automatically detected nvidia hwaccel for video decoding
2025-10-19 18:20:41.067269276  [2025-10-19 18:20:41] frigate.app                    INFO    : Starting Frigate (0.16.2-4d58206)
2025-10-19 18:20:41.089954609  [2025-10-19 18:20:41] peewee_migrate.logs            INFO    : Starting migrations
2025-10-19 18:20:41.092036313  [2025-10-19 18:20:41] peewee_migrate.logs            INFO    : There is nothing to migrate
2025-10-19 18:20:41.332972045  [2025-10-19 18:20:41] frigate.app                    INFO    : Recording process started: 850
2025-10-19 18:20:41.335266417  [2025-10-19 18:20:41] frigate.app                    INFO    : Review process started: 857
2025-10-19 18:20:41.342168768  [2025-10-19 18:20:41] frigate.app                    INFO    : go2rtc process pid: 128
2025-10-19 18:20:41.380044881  [2025-10-19 18:20:41] detector.onnx                  INFO    : Starting detection process: 875
2025-10-19 18:20:41.392623126  [2025-10-19 18:20:41] frigate.detectors.plugins.onnx INFO    : ONNX: loaded onnxruntime module
2025-10-19 18:20:41.394089038  [2025-10-19 18:20:41] frigate.detectors.plugins.onnx INFO    : ONNX: loading /config/model_cache/yolox_l.onnx
2025-10-19 18:20:41.394692846  [2025-10-19 18:20:41] frigate.app                    INFO    : Embedding process started: 882
2025-10-19 18:20:41.416500721  [2025-10-19 18:20:41] frigate.app                    INFO    : Output process started: 910
2025-10-19 18:20:41.632792311  [2025-10-19 18:20:41] frigate.app                    INFO    : Camera processor started for fisch: 966
2025-10-19 18:20:41.649265567  [2025-10-19 18:20:41] frigate.app                    INFO    : Camera processor started for einfahrt: 969
2025-10-19 18:20:41.653684576  [2025-10-19 18:20:41] frigate.app                    INFO    : Camera processor started for garten: 980
2025-10-19 18:20:41.671130713  [2025-10-19 18:20:41] frigate.app                    INFO    : Capture process started for fisch: 991
2025-10-19 18:20:41.706151384  [2025-10-19 18:20:41] frigate.app                    INFO    : Capture process started for einfahrt: 1011
2025-10-19 18:20:41.727005709  [2025-10-19 18:20:41] frigate.app                    INFO    : Capture process started for garten: 1021
2025-10-19 18:20:42.013195173  [2025-10-19 18:20:42] frigate.api.fastapi_app        INFO    : Starting FastAPI app
2025-10-19 18:20:42.423818723  [2025-10-19 18:20:42] frigate.detectors.plugins.onnx INFO    : ONNX: /config/model_cache/yolox_l.onnx loaded
2025-10-19 18:20:42.430543280  [2025-10-19 18:20:42] frigate.api.fastapi_app        INFO    : FastAPI started
2025-10-19 18:20:44.865722182  loading data from : /config/model_cache/facedet/landmarkdet.yaml

Relevant go2rtc log output

2025-10-19 18:20:17.534226896  [INFO] Preparing new go2rtc config...
2025-10-19 18:20:18.144958831  [INFO] Starting go2rtc...
2025-10-19 18:20:18.270027905  18:20:18.269 INF go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
2025-10-19 18:20:18.270035651  18:20:18.269 INF config path=/dev/shm/go2rtc.yaml
2025-10-19 18:20:18.270974736  18:20:18.270 INF [api] listen addr=:1984
2025-10-19 18:20:18.270981171  18:20:18.270 INF [rtsp] listen addr=:8554
2025-10-19 18:20:18.271894898  18:20:18.271 INF [webrtc] listen addr=:8555
2025-10-19 18:20:26.874956431  [INFO] Starting go2rtc healthcheck service...

Frigate stats

No response

Operating system

Other Linux

Install method

Docker Compose

docker-compose file or Docker CLI command

services:
  frigate:
    container_name: frigate
    privileged: true
    restart: unless-stopped
    stop_grace_period: 30s
    image: ghcr.io/blakeblackshear/frigate:stable-tensorrt
    shm_size: "8gb"
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /mnt/data/Docker/frigate/config:/config
      - /mnt/data/Docker/frigate/storage:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "8971:8971"
      - "5000:5000" # Internal unauthenticated access. Expose carefully.
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp
      - "1984:1984"
    environment:
      - FRIGATE_RTSP_PASSWORD="UKidW8ig0316"
      - NVIDIA_VISIBLE_DEVICES=all
      - NVIDIA_DRIVER_CAPABILITIES=compute,video,utility
    devices:
      - /dev/nvidia-uvm
      - /dev/nvidia-uvm-tools
      - /dev/nvidia-modeset
      - /dev/nvidiactl
      - /dev/nvidia0
    network_mode: bridge
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: all
              capabilities: [gpu]

Object Detector

Other

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

The camera causing problems is a FOSCAM FI9902P.
The other two are a Reolink E1 Outdoor (Garten) and a Yi Home y211ga (Fisch) which is running the yi-hack-Allwinner-v2.

[inkeep-ai-assistant[bot]]

Your issue with the "einfahrt" camera not showing MSE as an option is likely related to your go2rtc stream configuration. Looking at your config, there are a few potential issues:

1. Stream name mismatch: Your go2rtc stream is named einfahrt1 but your camera references einfahrt1 in the path. This should work, but let's verify the configuration is correct (1).

2. Video codec compatibility: Your einfahrt camera uses #video=copy while the other working cameras use #video=h264. If the camera stream works in go2rtc but not in your browser, the video codec might be unsupported (1). If using H265, you should switch to H264 (1).

3. Browser compatibility: MSE requires compatible video codecs. If the stream format is incompatible, Frigate falls back to jsmpeg (1).

To troubleshoot:

Check the go2rtc web interface: Navigate to port 1984 in your browser to access go2rtc's web interface and click stream for the specific camera to see if the camera's stream is being received (1).

Try forcing H264 encoding: Update your einfahrt stream configuration to:

go2rtc:
  streams:
    einfahrt1:
      - ffmpeg:rtsp://Camera1User:[email protected]:88/videoMain#video=h264#hardware

(1)

Check for transcoding needs: If the stream format is different or incompatible, you may need to re-encode the video using FFmpeg parameters (1):

go2rtc:
  streams:
    einfahrt1:
      - rtsp://Camera1User:[email protected]:88/videoMain
      - "ffmpeg:einfahrt1#video=h264#hardware"

(1)

The fact that your stream works in VLC and go2rtc's web interface but not as MSE in Frigate suggests a codec compatibility issue with your browser. When Frigate falls back to low bandwidth mode (jsmpeg), it's because MSE cannot decode the stream properly (2).

📚 Sources:

1. Configuring go2rtc
2. Live View

---

Have another question? Just tag @inkeep.

[MrKohli]

Yes it does, sort of. The errors in the go2rtc logs are now gone, but the stream still runs though jsmpeg. To me it looks like the camera is now not running though ffmpeg at all anymore:

2025-10-20 22:02:19.616079074  [INFO] Preparing new go2rtc config...
2025-10-20 22:02:20.263105213  [INFO] Starting go2rtc...
2025-10-20 22:02:20.643532128  22:02:20.643 INF go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
2025-10-20 22:02:20.643541586  22:02:20.643 INF config path=/dev/shm/go2rtc.yaml
2025-10-20 22:02:20.644611671  22:02:20.644 INF [api] listen addr=:1984
2025-10-20 22:02:20.648566035  22:02:20.648 INF [rtsp] listen addr=:8554
2025-10-20 22:02:20.657032158  22:02:20.656 INF [webrtc] listen addr=:8555
2025-10-20 22:02:27.681374223  [INFO] Starting go2rtc healthcheck service...
2025-10-20 22:02:35.698393514  22:02:35.698 DBG [exec] run rtsp args=["/usr/lib/ffmpeg/7.0/bin/ffmpeg","-hide_banner","-v","error","-hwaccel","cuda","-hwaccel_output_format","cuda","-allowed_media_types","video+audio","-fflags","nobuffer","-flags","low_delay","-timeout","5000000","-user_agent","go2rtc/ffmpeg","-rtsp_flags","prefer_tcp","-i","rtsp://192.x.x.51/ch0_0.h264","-c:v","h264_nvenc","-g","50","-bf","0","-profile:v","high","-level:v","auto","-preset:v","p2","-tune:v","ll","-c:a","aac","-user_agent","ffmpeg/go2rtc","-rtsp_transport","tcp","-f","rtsp","rtsp://127.0.0.1:8554/f63a468e62e242813403d2b77d3dcaa7"]
2025-10-20 22:02:39.075869081  22:02:39.075 DBG [exec] run rtsp launch=3.377390622s
2025-10-20 22:02:41.252575012  22:02:41.252 DBG [exec] run rtsp args=["/usr/lib/ffmpeg/7.0/bin/ffmpeg","-hide_banner","-v","error","-hwaccel","cuda","-hwaccel_output_format","cuda","-allowed_media_types","video+audio","-fflags","nobuffer","-flags","low_delay","-timeout","5000000","-user_agent","go2rtc/ffmpeg","-rtsp_flags","prefer_tcp","-i","rtsp://Camera2User:[email protected]:554/h264Preview_01_main","-c:v","h264_nvenc","-g","50","-bf","0","-profile:v","high","-level:v","auto","-preset:v","p2","-tune:v","ll","-c:a","aac","-user_agent","ffmpeg/go2rtc","-rtsp_transport","tcp","-f","rtsp","rtsp://127.0.0.1:8554/f992acacca0b6265c2b1cfd481183a66"]
2025-10-20 22:02:45.409847245  22:02:45.409 DBG [exec] run rtsp launch=4.15724136s
2025-10-20 22:02:46.923223655  22:02:46.923 DBG [exec] run rtsp args=["/usr/lib/ffmpeg/7.0/bin/ffmpeg","-hide_banner","-v","error","-hwaccel","cuda","-hwaccel_output_format","cuda","-allowed_media_types","video+audio","-fflags","nobuffer","-flags","low_delay","-timeout","5000000","-user_agent","go2rtc/ffmpeg","-rtsp_flags","prefer_tcp","-i","rtsp://192.x.x.51/ch0_0.h264","-c:v","h264_nvenc","-g","50","-bf","0","-profile:v","high","-level:v","auto","-preset:v","p2","-tune:v","ll","-c:a","aac","-user_agent","ffmpeg/go2rtc","-rtsp_transport","tcp","-f","rtsp","rtsp://127.0.0.1:8554/f63a468e62e242813403d2b77d3dcaa7"]
2025-10-20 22:02:46.938471433  22:02:46.938 DBG [exec] run rtsp args=["/usr/lib/ffmpeg/7.0/bin/ffmpeg","-hide_banner","-v","error","-hwaccel","cuda","-hwaccel_output_format","cuda","-allowed_media_types","video+audio","-fflags","nobuffer","-flags","low_delay","-timeout","5000000","-user_agent","go2rtc/ffmpeg","-rtsp_flags","prefer_tcp","-i","rtsp://Camera2User:[email protected]:554/h264Preview_01_main","-c:v","h264_nvenc","-g","50","-bf","0","-profile:v","high","-level:v","auto","-preset:v","p2","-tune:v","ll","-c:a","aac","-user_agent","ffmpeg/go2rtc","-rtsp_transport","tcp","-f","rtsp","rtsp://127.0.0.1:8554/f992acacca0b6265c2b1cfd481183a66"]
2025-10-20 22:02:51.222638369  22:02:51.222 DBG [exec] run rtsp launch=4.28413597s
2025-10-20 22:02:52.353687278  22:02:52.353 DBG [exec] run rtsp launch=5.430350564s

[hawkeye217]

Right, it's not using ffmpeg anymore. I was hopeful that the MSE player in your browser might detect an AAC audio stream from go2rtc and play back that, but it didn't seem to.

It would be interesting to see a screenshot of your browser's network devtools pane as the MSE player is starting up and before it flips to jsmpeg. If you could examine the websocket's response when you open Live view, that will give us more information.

Open your browser dev tools to the Network pane, select the WS option to only view websockets, and look for a ws?src=einfahrt1 entry. Click on that entry, and then choose the "Response" tab in the inspector pane.

This is Chrome, but other browsers will be similar.

[hawkeye217]

One other thing I thought of to ask - when you view the einfahrt1 stream in the go2rtc dashboard, does the overlay text say "MSE" or "RTC"?

[MrKohli]

One other thing I thought of to ask - when you view the einfahrt1 stream in the go2rtc dashboard, does the overlay text say "MSE" or "RTC"?

It says "RTC"

Right, it's not using ffmpeg anymore. I was hopeful that the MSE player in your browser might detect an AAC audio stream from go2rtc and play back that, but it didn't seem to.

It would be interesting to see a screenshot of your browser's network devtools pane as the MSE player is starting up and before it flips to jsmpeg. If you could examine the websocket's response when you open Live view, that will give us more information.

Open your browser dev tools to the Network pane, select the WS option to only view websockets, and look for a ws?src=einfahrt1 entry. Click on that entry, and then choose the "Response" tab in the inspector pane.

This is Chrome, but other browsers will be similar.

I tried to get a screenshot of that, but for some reason, the ws?src=einfahrt1 doesn't show up for this specific camera. I can just see an entry called "einfahrt" containing a bunch of binary data. I assume that's just the camera stream. It looks like this for me:

I also tried it with Firefox to sanity check myself and got the same result. I also noticed that sometimes a websocket error shows up int he browser console. I haven't been able to consistently recreate that though.

When I do the same thing for any of the other two cameras, I get the exact entry you mentioned which looks like this:

[hawkeye217]

So the fact that the go2rtc player is using RTC instead of MSE points to the issue being your camera's codec (likely its advertising of an audio codec when it doesn't have any audio, as you indicated).

Because we can't get it to work with ffmpeg in go2rtc (which allows you to remove the audio thereafter, and thus be compatible with MSE, which Frigate's live view uses), I think you're out of luck on this one. Might want to reach out on the go2rtc GitHub repo to see if they have any ideas as to why the camera won't work with the ffmpeg module.