[Config Support]: High CPU usage and detection in blacked out area

[cdn4lf]

Describe the problem you are having

I'm having very high CPU usage and regularly seeing snapshots for detected objects where the motion mask and zones are set to not observe.

Version

0.13.2-6476f8a

Frigate config file

# yaml-language-server: $schema=http://192.168.18.138:15000/api/config/schema.json

detectors:
  coral:
    type: edgetpu
    device: usb
#    device: cpu

mqtt:
  host: ******.138
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: *******
  password: *******
  stats_interval: 60

birdseye:
  enabled: True
  mode: continuous

ffmpeg:
  hwaccel_args:
  - -hwaccel
  - vaapi
  - -hwaccel_device
  - /dev/dri/renderD128
  - -hwaccel_output_format
  - yuv420p




record:
  enabled: true
  retain:
    days: 30
    mode: motion
  events:
    retain:
      default: 60
      mode: motion

snapshots:
  enabled: true
  retain:
    default: 30
  timestamp: false
  bounding_box: false
  crop: false
  required_zones:
  - coverage_area
  - vestibule
  - doorbell_area
  - driveway_zone


audio:
  enabled: false
  max_not_heard: 30
  min_volume: 500
  listen:
  - bark
  - fire_alarm
  - scream
  - speech
  - yell

  filters:
    speech:
      threshold: 0.8

objects:
  # Optional: list of objects to track from labelmap.txt (default: shown below)
  track:
  - person
  - car
  - bicycle
  - truck

cameras:
  driveway:
    detect:
      width: 1280
      height: 720
      fps: 5
    ffmpeg:
      inputs:
      - path: rtsp://*******.104:8554/360p?mp4
        roles:
        - record
        - detect
    motion:
      mask:
      - 406,269,120,298,0,687,0,720,0,0,1280,0,1280,247

    zones:
      driveway_zone:
        coordinates: 0,720,376,188,847,155,1087,225,1280,437,1280,720
      stationary_zone:
        coordinates: 1018,182,462,189,191,650,0,650,0,0,913,0,1280,0,1280,430
    objects:
      track:
      - person
      - car
      - bicycle
      - motorcycle
      - bus


  walkway:
    detect:
      width: 1280
      height: 720
      fps: 5
    ffmpeg:
      inputs:
      - path: rtsp://*******.140:8554/1080p?mp4
        roles:
        - record
        - detect
    motion:
      mask:
      - 647,228,691,266,771,315,819,307,876,62,889,0,418,0,283,0,314,280,441,266
    objects:
      track:
      - person
      filters:
        person:
          mask:
          - 368,0,401,308
    zones:
      coverage_area:
        coordinates: 
          389,102,460,97,481,127,587,114,753,231,779,0,1280,80,1280,720,0,720,0,135,216,46,369,0
        objects:
        - person
    mqtt:
      required_zones:
      - coverage_area


  front_door:
    ffmpeg:
      hwaccel_args: preset-vaapi
      inputs:
      - path: rtsp://*******@******.102/11
        roles:
        - record
        - detect
    detect:
      width: 1536
      height: 1536
      fps: 5
    objects:
      track:
      - person
    snapshots:
      enabled: true
      timestamp: false
      bounding_box: true
      retain:
        default: 15
    record:
      enabled: true
      retain:
        days: 15
      events:
        retain:
          default: 15
    zones:
      doorbell_area:
        coordinates: 0,1536,1536,1536,1536,0,0,0
        objects:
        - person
    birdseye:
      enabled: False

##########################################################################

go2rtc:
  streams:
                    ## CHANGE RTSP USERNAME AND PASSWORD
    front_door:

    - rtsp://*****@*******.102:554/H.264
    - isapi://********@1*******.102:80/
  
  candidates:
  - *******.138:8555
  - stun:8555



## THIS PREVENTS THE AUDIO COMING OUT FROM THE DOORBELL SOUNDING MUFFLED
  ffmpeg:
    bin: ffmpeg
    volume: -af "volume=30dB"

##########################################################################

Relevant log output

2024-06-09 20:59:07.137799742  [INFO] Preparing Frigate...
2024-06-09 20:59:07.150894701  [INFO] Starting Frigate...
2024-06-09 20:59:08.151136401  [2024-06-09 20:59:08] frigate.app                    INFO    : Starting Frigate (0.13.2-6476f8a)
2024-06-09 20:59:08.193960311  [2024-06-09 20:59:08] peewee_migrate.logs            INFO    : Starting migrations
2024-06-09 20:59:08.217567390  [2024-06-09 20:59:08] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-06-09 20:59:08.227165574  [2024-06-09 20:59:08] frigate.app                    INFO    : Recording process started: 728
2024-06-09 20:59:08.229126504  [2024-06-09 20:59:08] frigate.app                    INFO    : go2rtc process pid: 89
2024-06-09 20:59:08.253157409  [2024-06-09 20:59:08] detector.coral                 INFO    : Starting detection process: 738
2024-06-09 20:59:08.257103924  [2024-06-09 20:59:08] frigate.app                    INFO    : Output process started: 740
2024-06-09 20:59:10.927961427  [2024-06-09 20:59:08] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2024-06-09 20:59:10.933340067  [2024-06-09 20:59:10] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found
2024-06-09 20:59:23.587081784  [2024-06-09 20:59:23] frigate.app                    INFO    : Camera processor started for driveway: 787
2024-06-09 20:59:23.617503123  [2024-06-09 20:59:23] frigate.app                    INFO    : Camera processor started for walkway: 789
2024-06-09 20:59:23.628526308  [2024-06-09 20:59:23] frigate.app                    INFO    : Camera processor started for front_door: 791
2024-06-09 20:59:23.639270108  [2024-06-09 20:59:23] frigate.app                    INFO    : Capture process started for driveway: 793
2024-06-09 20:59:23.639898304  [2024-06-09 20:59:23] frigate.app                    INFO    : Capture process started for walkway: 796
2024-06-09 20:59:23.651060413  [2024-06-09 20:59:23] frigate.app                    INFO    : Capture process started for front_door: 800
2024-06-09 21:00:44.217213780  [2024-06-09 21:00:44] frigate.video                  ERROR   : front_door: Unable to read frames from ffmpeg process.
2024-06-09 21:00:44.217443923  [2024-06-09 21:00:44] frigate.video                  ERROR   : front_door: ffmpeg process is not running. exiting capture thread...
2024-06-09 21:00:53.693994780  [2024-06-09 21:00:53] watchdog.front_door            ERROR   : Ffmpeg process crashed unexpectedly for front_door.
2024-06-09 21:00:53.694268227  [2024-06-09 21:00:53] watchdog.front_door            ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2024-06-09 21:00:53.694365942  [2024-06-09 21:00:53] ffmpeg.front_door.detect       ERROR   : [rtsp @ 0x55d059cdb2c0] Missing PPS in sprop-parameter-sets, ignoring
2024-06-09 21:00:53.694662579  [2024-06-09 21:00:53] ffmpeg.front_door.detect       ERROR   : [segment @ 0x55d059cfb440] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

Coral version

USB

Any other information that may be helpful

Front Door = ezviz db1
Walkway and Garage = Wyze V3

[hawkeye217]

Motion masks are not designed to stop detected objects from creating events. The docs have all the details on how they work: https://docs.frigate.video/configuration/masks/

You should use required_zones at the camera level if you want to include/exclude specific items from being tracked and saved as events.

To lower CPU usage, you could lower your detect resolution for the front_door camera. The detect resolution does not need to match your camera's output resolution - only its aspect ratio. For starters, try cutting it in half. That should reduce your CPU usage significantly.

If that camera has a substream, you could use that for the detect role and use the main stream for record.

Additionally, you could check the debug view and watch for red motion boxes. If you have excess motion, tweak your motion detection settings. The docs have all the details - search for "tuning motion".

[cdn4lf]

I'm using required zones. They still aren't being respected. The sidewalk is outside of the required zone and is often being captured by the walkway camera. Cameras don't have substreams. I eesearc and tried that already. I'll try the other two suggestions.

…

On Sun, Jun 9, 2024, 9:45 p.m. Josh Hawkins ***@***.***> wrote: Motion masks are not designed to stop detected objects from creating events. The docs have all the details on how they work: https://docs.frigate.video/configuration/masks/ You should use required_zones at the camera level if you want to include/exclude specific items from being tracked and saved as events. To lower CPU usage, you could lower your detect resolution for the front_door camera. The detect resolution does not need to match your camera's output resolution - only its aspect ratio. For starters, try cutting it in half. That should reduce your CPU usage significantly. If that camera has a substream, you could use that for the detect role and use the main stream for record. Additionally, you could check the debug view and watch for red motion boxes. If you have excess motion, tweak your motion detection settings. The docs have all the details - search for "tuning motion". — Reply to this email directly, view it on GitHub <#11840 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL4QL4MKYEDQNE2C57GQY63ZGUAMHAVCNFSM6AAAAABJBLL2VCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TOMRSGA4DC> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

Can you be more specific about what camera you're seeing unwanted events on? And are you seeing unwanted snapshots, unwanted events, or both?

[cdn4lf]

I'm seeing the events on the camera titled walkway. I'm seeing snapshots, recordings and events. I can send screenshots and snapshots tomorrow of the zones as configured.

…

On Sun, Jun 9, 2024, 9:52 p.m. Josh Hawkins ***@***.***> wrote: Can you be more specific about what camera you're seeing unwanted events on? And are you seeing unwanted snapshots, unwanted events, or both? — Reply to this email directly, view it on GitHub <#11840 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL4QL4OGL6OJSHSOYFKXLCDZGUBF3AVCNFSM6AAAAABJBLL2VCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TOMRSGEYTK> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[hawkeye217]

You haven't set required_zones for the walkway camera correctly to exclude events from being saved in Frigate. What you've set is the mqtt option so that only objects that appear in the coverage_area zone are sent over MQTT.

Read the docs on zones to cause events to only be saved for the coverage_area zone: https://docs.frigate.video/configuration/zones

[cdn4lf]

Fixed. Motion masks around timestamps and trees resolved the issue. The timestamp was creating the motion event which then saw the person and reported. Still going to go through and update my zones to eliminate stationary objects. Thanks for pointing me in the right direction.

[hawkeye217]

Great! Happy to help.