[Support]: Erroneous HA notifications

[Jacobb5179]

Describe the problem you are having

I am running Frigate in a docker container as well as a Linux Home Assistant VM - they are both running off the same hardware but each have separate IP addresses on my network. I have linked Frigate to HA to notify me of events using the frigate template and MQTT, it appears to work great but often sends me notifications of events that haven't happened. Looking into it closer it seems when there is movement but no object detected there is still a notification triggered which points to an event which doesn't exist. If I click on the notification I get a 502 bad gateway error and no preview or thumbnail. Is it possible that frigate is broadcasting on MQTT even if there is no event? Apologies I'm very much new to this and trying to teach myself as I go!

Any help on further debugging or solutions would be very much welcomed!

Version

0.15.0-cea210d

What browser(s) are you using?

No response

Frigate config file

mqtt:
  enabled: true
  host: 111.222.333.444
  user: USER
  password: PW
tls:
  enabled: false

detectors:
  tensorrt:
    type: tensorrt
    device: 0

model:
  path: /config/model_cache/tensorrt/8.5.3/yolov7-640.trt
  input_tensor: nchw
  input_pixel_format: rgb
  width: 640
  height: 640

cameras:
  front:
    review:
      alerts:
        required_zones:
          - detect_front
      detections:
        required_zones:
          - detect_front
    enabled: true
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://USER:PW@111.222.333.444.1:554/h264Preview_01_main # <----- The stream you want to use for detection
          roles:
            - detect
            - record
    motion:
      mask: 
        0.228,0.662,0.191,0.416,0.571,0.2,0.733,0.528,0.759,0.466,0.773,0.397,0.784,0.352,1,0.294,1,0,0,0,0,0.997,0.029,0.997
    zones:
      detect_front:
        coordinates: 
          0.027,1,0.23,0.663,0.192,0.419,0.571,0.196,0.732,0.533,0.759,0.483,0.786,0.356,0.998,0.297,1,1
        loitering_time: 0
    objects:
      filters:
        person:
          mask: 
            0.028,0.992,0.227,0.665,0.194,0.408,0.571,0.196,0.736,0.524,0.758,0.469,0.783,0.356,1,0.301,0.998,0.001,-0.001,0,0,1
  back:
    review:
      alerts:
        required_zones:
          - detect_back
      detections:
        required_zones:
          - detect_back
    enabled: true
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://USER:PASSWORD@123.456.789.10:554/h264Preview_01_main # <----- The stream you want to use for detection
          roles:
            - detect
            - record

    detect:
      enabled: true
    motion:
      mask:
        - 0.062,0.117,0.072,0.257,0.161,0.219,0.158,0.085
        - 0.206,0.079,0.22,0.329,0.279,0.301,0.271,0.07
        - 0.324,0.097,0.321,0.001,0.888,0,0.922,0.045,0.91,0.092,1,0.159,0.991,0.294,0.629,0.186,0.633,0.109
      threshold: 25
      contour_area: 10
      improve_contrast: true
    zones:
      detect_back:
        coordinates: 0,0,0,1,1,1,1,0.305,0.626,0.188,0.625,0.113,0.327,0.102,0.314,0
        loitering_time: 0
    objects:
      filters:
        person:
          mask:
            - 0.325,0.099,0.323,0.001,0.887,0.001,0.919,0.038,0.914,0.087,0.998,0.159,0.989,0.291,0.631,0.182,0.632,0.108
            - 0.059,0.122,0.16,0.094,0.163,0.22,0.071,0.256
            - 0.208,0.073,0.271,0.071,0.281,0.302,0.221,0.327
objects:
  # Optional: list of objects to track from labelmap.txt (default: shown below)
  track:
    - person

record:
  enabled: true
  retain:
    days: 6
    mode: all
  alerts:
    retain:
      days: 30
  detections:
    retain:
      days: 30
snapshots:
  enabled: true
version: 0.15-1
semantic_search:
  enabled: false
  reindex: false
  model_size: large

Relevant Frigate log output

2025-02-27 11:38:11.977648221  [INFO] Preparing Frigate...
2025-02-27 11:38:12.094244664  [INFO] Starting Frigate...
2025-02-27 11:38:14.278487103  [2025-02-27 11:38:14] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-02-27 11:38:14.300066511  [2025-02-27 11:38:14] frigate.util.config            INFO    : frigate config does not need migration...
2025-02-27 11:38:15.603141454  [2025-02-27 11:38:15] frigate.util.services          INFO    : Automatically detected nvidia hwaccel for video decoding
2025-02-27 11:38:20.657802893  [2025-02-27 11:38:20] frigate.app                    INFO    : Starting Frigate (0.15.0-cea210d)
2025-02-27 11:38:20.681071848  [2025-02-27 11:38:20] peewee_migrate.logs            INFO    : Starting migrations
2025-02-27 11:38:20.681326295  [2025-02-27 11:38:20] peewee_migrate.logs            INFO    : There is nothing to migrate
2025-02-27 11:38:21.718564941  [2025-02-27 11:38:21] frigate.app                    INFO    : Recording process started: 445
2025-02-27 11:38:21.718731894  [2025-02-27 11:38:21] frigate.app                    INFO    : Review process started: 454
2025-02-27 11:38:21.721098343  [2025-02-27 11:38:21] frigate.app                    INFO    : go2rtc process pid: 112
2025-02-27 11:38:21.734662732  [2025-02-27 11:38:21] detector.tensorrt              INFO    : Starting detection process: 461
2025-02-27 11:38:21.749765165  [2025-02-27 11:38:21] frigate.app                    INFO    : Output process started: 478
2025-02-27 11:38:21.786081225  [2025-02-27 11:38:21] frigate.app                    INFO    : Camera processor started for front: 492
2025-02-27 11:38:21.797688716  [2025-02-27 11:38:21] frigate.app                    INFO    : Camera processor started for back: 493
2025-02-27 11:38:21.797913595  [2025-02-27 11:38:21] frigate.app                    WARNING : The current SHM size of 256.0MB is too small, recommend increasing it to at least 342MB.
2025-02-27 11:38:21.810034925  [2025-02-27 11:38:21] frigate.app                    INFO    : Capture process started for front: 499
2025-02-27 11:38:21.827718410  [2025-02-27 11:38:21] frigate.app                    INFO    : Capture process started for back: 508
2025-02-27 11:38:21.928415047  [2025-02-27 11:38:21] frigate.api.fastapi_app        INFO    : Starting FastAPI app
2025-02-27 11:38:22.081291960  [2025-02-27 11:38:22] frigate.api.fastapi_app        INFO    : FastAPI started
2025-02-27 11:38:22.274047200  [2025-02-27 11:38:22] frigate.detectors.plugins.tensorrt INFO    : Loaded engine size: 186 MiB
2025-02-27 11:38:22.407728564  [2025-02-27 11:38:22] frigate.detectors.plugins.tensorrt INFO    : [MemUsageChange] Init cuBLAS/cuBLASLt: CPU +6, GPU +8, now: CPU 353, GPU 268 (MiB)
2025-02-27 11:38:22.412381003  [2025-02-27 11:38:22] frigate.detectors.plugins.tensorrt INFO    : [MemUsageChange] Init cuDNN: CPU +1, GPU +10, now: CPU 354, GPU 278 (MiB)
2025-02-27 11:38:22.416722091  [2025-02-27 11:38:22] frigate.detectors.plugins.tensorrt INFO    : [MemUsageChange] TensorRT-managed allocation in engine deserialization: CPU +0, GPU +189, now: CPU 0, GPU 189 (MiB)
2025-02-27 11:38:22.423291976  [2025-02-27 11:38:22] frigate.detectors.plugins.tensorrt INFO    : [MemUsageChange] Init cuBLAS/cuBLASLt: CPU +0, GPU +8, now: CPU 168, GPU 273 (MiB)
2025-02-27 11:38:22.423842202  [2025-02-27 11:38:22] frigate.detectors.plugins.tensorrt INFO    : [MemUsageChange] Init cuDNN: CPU +0, GPU +8, now: CPU 168, GPU 281 (MiB)
2025-02-27 11:38:22.423871093  [2025-02-27 11:38:22] frigate.detectors.plugins.tensorrt INFO    : [MemUsageChange] TensorRT-managed allocation in IExecutionContext creation: CPU +0, GPU +116, now: CPU 0, GPU 305 (MiB)
2025-02-27 11:43:26.257573868  [2025-02-27 11:43:26] frigate.comms.dispatcher       INFO    : Setting motion threshold for back: 30
2025-02-27 11:43:26.267003018  [2025-02-27 11:43:26] frigate.comms.dispatcher       INFO    : Setting motion contour area for back: 10
2025-02-27 11:43:32.808234702  [2025-02-27 11:43:32] frigate.comms.dispatcher       INFO    : Setting motion threshold for back: 31
2025-02-27 11:43:32.909601446  [2025-02-27 11:43:32] frigate.comms.dispatcher       INFO    : Setting motion threshold for back: 30
2025-02-27 11:43:33.194621394  [2025-02-27 11:43:33] frigate.comms.dispatcher       INFO    : Setting motion threshold for back: 29
2025-02-27 11:43:33.390627218  [2025-02-27 11:43:33] frigate.comms.dispatcher       INFO    : Setting motion threshold for back: 28
2025-02-27 11:43:33.584315147  [2025-02-27 11:43:33] frigate.comms.dispatcher       INFO    : Setting motion threshold for back: 27
2025-02-27 11:43:33.971966209  [2025-02-27 11:43:33] frigate.comms.dispatcher       INFO    : Setting motion threshold for back: 26
2025-02-27 11:43:34.264778154  [2025-02-27 11:43:34] frigate.comms.dispatcher       INFO    : Setting motion threshold for back: 25
2025-02-27 11:43:36.727314855  [2025-02-27 11:43:36] frigate.util.services          INFO    : Automatically detected nvidia hwaccel for video decoding
2025-02-27 11:46:13.437721280  [2025-02-27 11:46:13] frigate.api.media              ERROR   : Event not found: 1740656758.698508-8b3zvu
2025-02-27 11:55:35.000271354  [2025-02-27 11:55:34] frigate.api.media              ERROR   : Event not found: 1740657009.719325-bvx4vw

Relevant go2rtc log output

2025-02-27 11:38:11.977168203  [INFO] Preparing new go2rtc config...
2025-02-27 11:38:12.420826845  [INFO] Starting go2rtc...
2025-02-27 11:38:12.512401995  11:38:12.512 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2025-02-27 11:38:12.512421604  11:38:12.512 INF config path=/dev/shm/go2rtc.yaml
2025-02-27 11:38:12.512722932  11:38:12.512 INF [api] listen addr=:1984
2025-02-27 11:38:12.512821215  11:38:12.512 INF [rtsp] listen addr=:8554
2025-02-27 11:38:12.512954275  11:38:12.512 INF [webrtc] listen addr=:8555/tcp
2025-02-27 11:38:21.978292978  [INFO] Starting go2rtc healthcheck service...

FFprobe output from your camera

-

Frigate stats

No response

Install method

Docker CLI

docker-compose file or Docker CLI command

Using Unraid, unsure I can get the docker compose file.

Object Detector

TensorRT

Network connection

Wired

Camera make and model

Reolink RCL520

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

No response

[hawkeye217]

What is the "frigate template"?

Most likely these are just false positives and you just need to filter before notifying.

[hawkeye217]

Since you're using Frigate 0.15, you'll want to be on the beta version of the blueprint and you'll want to be using the reviews topic.

[Jacobb5179]

I'll give this a go, however I was previously using version 14 and had the same issue. I updated recently in the hope it would fix it... I will try the beta version of the blueprint anyway - thanks!

[hawkeye217]

Using the reviews topic (rather than the events topic) will solve the issue if it's false positives that you are being notified on.

[Jacobb5179]

Hmm...friagte/reviews no longer triggers the automation at all. Any ideas? Thanks for your help so far!!

[hawkeye217]

You'll want to reach out on the sgtbatten github for help with the blueprint.