Ubiquity - Protect Issues in Frigate

[johandijkstra]

Describe the problem you are having

Hi all,

The problem I have is that my 2 Ubiquity camera's are going offline so now and then.
I have 3 other camera's from EZViz which work flawlessly.

Version

0.16.1-e664cb2

What browser(s) are you using?

Google Chrome 140.0.7339.80

Frigate config file

detectors: # <---- add detectors
  coral:
    type: edgetpu
    device: usb

cameras:
  front_door:
    ffmpeg:
      inputs:
        - path: rtsp://10.0.0.1:7447/CLlQTT2wvHvPgJ0E
          roles:
            - detect
            - record
      output_args:
        record: preset-record-ubiquiti
    detect:
      width: 640
      height: 360
      fps: 5
    motion:
      mask: 0,33,0,0,148,0,129,22
    zones:
      zone_0:
        coordinates: 640,360,640,182,540,0,475,40,0,284,0,360
    record:
      enabled: true
      alerts:
        retain:
          days: 10
      detections:
        retain:
          days: 10
    objects:
      track:
        - person
        - cat
        - car

    snapshots:
      # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
      # This value can be set via MQTT and will be updated in startup based on retained value
      enabled: true
      # Optional: print a timestamp on the snapshots (default: shown below)
      timestamp: true
      # Optional: draw bounding box on the snapshots (default: shown below)
      bounding_box: false
      # Optional: crop the snapshot (default: shown below)
      crop: false
      # Optional: height to resize the snapshot to (default: original size)
      height: 180
      # Optional: Restrict snapshots to objects that entered any of the listed zones (default: no required zones)
      required_zones: []
      # Optional: Camera override for retention settings (default: global values)
      retain:
        # Required: Default retention days (default: shown below)
        default: 10
        # Optional: Per object retention days
        objects:
          person: 15
          cat: 15

    review:
      alerts:
        required_zones: zone_0
      detections:
        required_zones: zone_0
  garagepad:
    ffmpeg:
      inputs:
        - path: rtsp://10.0.0.1:7447/yKxXRF2SL4WmEfWq
          roles:
            - detect
            - record
      output_args:
        record: preset-record-ubiquiti
    detect:
      width: 640
      height: 360
      fps: 5
    objects:
      track:
        - person
        - cat
        - car
      filters:
        car:
          mask: 0.529,0.507,0.974,0.475,0.932,0.988,0.485,0.993
    record:
      enabled: true
      alerts:
        retain:
          days: 10
      detections:
        retain:
          days: 10
    motion:
      mask: 0,0,126,0,125,21,0,32
    snapshots:
      # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
      # This value can be set via MQTT and will be updated in startup based on retained value
      enabled: true
      # Optional: print a timestamp on the snapshots (default: shown below)
      timestamp: true
      # Optional: draw bounding box on the snapshots (default: shown below)
      bounding_box: false
      # Optional: crop the snapshot (default: shown below)
      crop: false
      # Optional: height to resize the snapshot to (default: original size)
      height: 180
      # Optional: Restrict snapshots to objects that entered any of the listed zones (default: no required zones)
      required_zones: []
      # Optional: Camera override for retention settings (default: global values)
      retain:
        # Required: Default retention days (default: shown below)
        default: 10
        # Optional: Per object retention days
        objects:
          person: 15

Relevant Frigate log output

| 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [swscaler @ 0x7f1520015340] deprecated pixel format used, make sure you did set range correctly
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [aost#0:1/aac @ 0x55a98714fb00] Non-monotonic DTS; previous: 230085, current: 229493; changing to 230086. This may result in incorrect timestamps in the output file.
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [swscaler @ 0x7f1520015340] deprecated pixel format used, make sure you did set range correctly
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [aac @ 0x55a987157540] Queue input is backward in time
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [aost#0:1/aac @ 0x55a98714fb00] Non-monotonic DTS; previous: 240594, current: 240056; changing to 240595. This may result in incorrect timestamps in the output file.
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [aac @ 0x55a987157540] Queue input is backward in time
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [aost#0:1/aac @ 0x55a98714fb00] Non-monotonic DTS; previous: 247721, current: 246984; changing to 247722. This may result in incorrect timestamps in the output file.
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [aost#0:1/aac @ 0x55a98714fb00] Non-monotonic DTS; previous: 247722, current: 247127; changing to 247723. This may result in incorrect timestamps in the output file.
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [aac @ 0x55a987157540] Queue input is backward in time
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [aost#0:1/aac @ 0x55a98714fb00] Non-monotonic DTS; previous: 260047, current: 259309; changing to 260048. This may result in incorrect timestamps in the output file.
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [aac @ 0x55a987157540] Queue input is backward in time
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [aost#0:1/aac @ 0x55a98714fb00] Non-monotonic DTS; previous: 267376, current: 267156; changing to 267377. This may result in incorrect timestamps in the output file.
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [aac @ 0x55a987157540] Queue input is backward in time
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [aost#0:1/aac @ 0x55a98714fb00] Non-monotonic DTS; previous: 286489, current: 285752; changing to 286490. This may result in incorrect timestamps in the output file.
error | 2025-09-09 12:27:50 | ffmpeg.front_door.detect | [in#0/rtsp @ 0x55a9870c9080] Error during demuxing: Connection timed out
info  | 2025-09-09 12:27:50 | watchdog.front_door      | Restarting ffmpeg...

Relevant go2rtc log output

info | 2025-09-08 12:04:45 | startup | Preparing new go2rtc config...
info | 2025-09-08 12:04:45 | startup | Starting go2rtc...
info | 2025-09-08 12:04:45 | startup | go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
info | 2025-09-08 12:04:45 | startup | config path=/dev/shm/go2rtc.yaml
info | 2025-09-08 12:04:45 | api     | listen addr=:1984
info | 2025-09-08 12:04:45 | rtsp    | listen addr=:8554
info | 2025-09-08 12:04:45 | webrtc  | listen addr=:8555
info | 2025-09-08 12:04:54 | startup | Starting go2rtc healthcheck service...

FFprobe output from your camera

-

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

Object Detector

Coral

Network connection

Wired

Camera make and model

Ubiquity G3 Flex & Ubiquity G4 Bullet

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

So the strange thing is, in the past when I used Frigate on Home Assistant, the Ubiquity camera's where rock solid. The EZViz camera's where offline often.

Now, on a NUC Client with 16GB RAM dedicated for Frigate, the EZVIZ works flawless, but the Ubiquity is a pain according to the logs.

Any thoughts?

[inkeep-ai-assistant[bot]]

Based on the logs showing "Non-monotonic DTS" errors and connection timeouts with your Unifi Protect cameras, there are several configuration adjustments you can try.

For Unifi Protect cameras, the documentation recommends using rtspx streams with go2rtc and specific output arguments (1). Your current configuration connects directly to the RTSP stream, but Unifi cameras work better with go2rtc restreaming.

Here's the recommended configuration structure for Unifi Protect cameras:

go2rtc:
  streams:
    front_door:
      - rtspx://10.0.0.1:7447/CLlQTT2wvHvPgJ0E
    garagepad:
      - rtspx://10.0.0.1:7447/yKxXRF2SL4WmEfWq

(1)

Then update your camera inputs to use the restream:

cameras:
  front_door:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/front_door
          input_args: preset-rtsp-restream
          roles:
            - detect
            - record
      output_args:
        record: preset-record-ubiquiti

(1), (2)

The documentation also notes that "In the Unifi 2.0 update Unifi Protect Cameras had a change in audio sample rate which causes issues for ffmpeg. The input rate needs to be set for record if used directly with unifi protect" (1). The preset-record-ubiquiti output args you're already using should handle this.

Additionally, consider using separate streams for detect and record roles to reduce the load on each camera connection (2). This approach creates only one connection to each camera while supporting both detection and recording.

The connection timeout errors suggest network connectivity issues between Frigate and your Unifi Protect system. Check your network stability and consider adjusting the retry_interval setting if timeouts persist (3).

📚 Sources:

1. Camera Specific Configurations
2. Restream
3. Full Reference Config

---

Have another question? Just tag @inkeep.