Restricting events to specific zones not working

[asemev]

Describe the problem you are having

• I have a camera at my front door.
• At the end of the entrance, there is a pavement
• I configured a zone for only detecting persons entering my home entrance, walking towards my door. So anybody just walking past my home along the pavement should be ignored.
• I made sure the zone is very separated from the pavement and also added intertia=3.
• I also added required zone in the notification (0.12.0.2)
• Despite all my efforts for several hours, frigate still keeps sending me a notification whenever someone just walks on the pavement.
• Pls note that i dont want to mask the pavement area because then it half of the image of the person is blacked out when they start walking towards my door.
• I have read the instructions carefully and tried all the options
• I have also checked the github issues section in case someone else had the same issue but couldnt find anything.
• I posted a few screenshots so you can see my zone area and the people walking on the pavement
• i also get an error when i click on "View Clip or View Snapshot int he Android notification. Screenshot below.

Many thanks!

Version

0.13.2-6476F8A

Frigate config file

detectors:
  coral:
    type: edgetpu
    device: 'usb'
    num_threads: 4
mqtt:
  host: 192.168.178.125
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user:
  password: 
#ffmpeg:
#  hwaccel_args:
#    - '-c:v'
#    - h264_v4l2m2m

#ffmpeg:
#  hwaccel_args: preset-rpi-64-h264

cameras:
#  Garage:
#    ffmpeg:
#      inputs:
#        - path: 'rtsp:https://
#          global_args: '-hide_banner -loglevel error'
#          roles:
#            - detect
#            - record
#    detect:
#     width: 1920
#      height: 1080
#      fps: 5
#    motion:
#      mask: >-
#        -0,0,1920,0,1920,1080,1490,1080,1659,694,690,270,121,417,345,1080,0,1080
#    snapshots:
#      enabled: true
#      timestamp: true
#      bounding_box: true
#      crop: false
#      height: 175
#      retain:
#        default: 10
#        objects:
#          person: 10
#    mqtt:
#      enabled: true
#      timestamp: true
#      bounding_box: true
#      crop: true
#      height: 270
#    objects:
#      track:
#        - person
#
#      filters:
#        person:
#          min_area: 5000
#          max_area: 100000
#          min_score: 0.5
#          threshold: 0.7
#          mask: >-
#            -2,1,1920,0,1920,1080,1490,1080,1678,653,547,227,533,73,354,86,370,292,116,340,285,1012,680,1014,678,1080,0,1080
#    zones:
#      car:
#        coordinates: 343,1058,1477,1080,1654,683,776,252,123,394
#    record:
#      enabled: true
#      retain: 
#        days: 3
#        mode: motion 
#      events:
#        retain:
#          default: 3
#          mode: active_objects

  Package:
    ffmpeg:
      inputs:
        - path: 
          global_args: '-hide_banner -loglevel error'
          roles:
            - detect
            - record
    detect:
      width: 1920
      height: 1080
      fps: 5
    motion:
      mask:
        - 0,1080,1920,1080,1350,547,1408,891,1081,899,1105,544,1307,523,1920,1080,1920,0,0,0

    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      crop: false
      height: 175
      retain:
        default: 10
        objects:
          person: 10

    mqtt:
      enabled: true
      timestamp: true
      bounding_box: true
      crop: true
      height: 270
    objects:
      track:
        - person

    zones:
      box:
        coordinates: 1128,888,1408,891,1356,564,1073,535
    record:
      enabled: true
      retain: 
        days: 3
        mode: motion 
      events:
        retain:
          default: 3
          mode: active_objects

  Door:
    ffmpeg:
      inputs:
        - path: 
          global_args: '-hide_banner -loglevel error'
          roles:
            - detect
            - record
    detect:
      width: 1920
      height: 1080
      fps: 5
    motion:
    record:
      enabled: true
      retain: 
        days: 10
        mode: motion 
      events:
        required_zones:
          - entire_yard
        retain:
          default: 10
          mode: active_objects
    snapshots:
      required_zones:
        - zone_0
      enabled: true
      timestamp: true
      bounding_box: true
      crop: false
      height: 175
      retain:
        default: 10
        objects:
          person: 10
    mqtt:
      enabled: true
      timestamp: true
      bounding_box: true
      crop: true
      height: 270
    objects:
      track:
        - person
    zones:
      zone_0:
        coordinates: 235,1080,1920,1080,1734,387,502,324
        inertia: 3
        objects:
          - person
database:
  path: /media/frigate.db
logger:
  default: info
  logs:
    frigate.mqtt: error

Relevant log output

N/A

Frigate stats

No response

Operating system

HassOS

Install method

HassOS Addon

Coral version

USB

Any other information that may be helpful

No response

[NickM-27]

Like it says in the docs, presence in a zone is based on the bottom center of the bounding box. Most likely the bounding box is in the zone for a few frames https://docs.frigate.video/configuration/zones

You can use the timeline above the clips view to see what the box was when it was considered in the zone.

[asemev]

i cannot provide it because the event doesnt exist. Please see my above message.

[asemev]

pls have a look at the recordings screenshot. its not showing any events int he 17:00 slot:
While got the Android notification at 17:13.

[NickM-27]

I see what you're saying. This is not a bug and is working as intended. The /events topic is a raw topic which sends all data regardless of the config. It is your job as the user to use this information (in this case, current_zones or entered_zones) to decide when to send a notification.

[asemev]

I see what you're saying. This is not a bug and is working as intended. The /events topic is a raw topic which sends all data regardless of the config. It is your job as the user to use this information (in this case, current_zones or entered_zones) to decide when to send a notification.

Sorry sir, i do not agree with your statement and I would like to kindly ask another person's opnion.

1. I followed all the instructions very carefully (I have been using frigate for 4 years now since Blake personally helped me set it up)
2. I added this new camera and this is the first time i am seeing an issue with the zone settings. This is a new 5MP camnera and maybe this is causing an issue somehow.
3. Overall It is not working as intended. Despite the zone requirement and the big distance between the zone and the pavement, frigate is still sending a notification for any movement outside the zone area.

Thank you.

[NickM-27]

The fact that events are not being created in the UI means it is working as expected. Like I said, the data sent over /events on mqtt is more verbose so the fact that notifications are being sent means your automation is not correctly checking for the zones

[asemev]

i setup the notification to specifically only send notifications when there is motion inside the zone 0:

alias: Fridate - Door Person
description: ""
use_blueprint:
path: SgtBatten/Stable.yaml
input:
camera: camera.door
notify_device: e00c1c0945954b1f084708607893d66f
zones:
- zone_0
labels:
- person
cooldown: 10
silence_timer: 10

[NickM-27]

Then I'd suggest going to https://github.com/SgtBatten/HA_blueprints/ to debug this further. From the frigate perspective an event is not created so things are working as expected

[asemev]

Thank you, that makes sense. I will raise it there.