Zone min_area configuration not being honored, maybe I did something wrong? #9870
Unanswered
airadier
asked this question in
Ask A Question
Replies: 2 comments 2 replies
-
If you want your zone to be enforced you need to make it required for events |
Beta Was this translation helpful? Give feedback.
0 replies
-
Zone filters limit when a zone is activated by an object. They are not a way to apply object filters in a specific area to avoid false positives. The behavior you are seeing is exactly the intended use. Objects smaller than the min_area do not have the zone. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I have defined a camera, and I want to set a min_area for the
near
zone, as from time to time I get false positives of cats being detected as person.This is the relevant configuration section:
As you can see, I have a zone "near" with a set of coordinates, and I define a filter for person with min_area 80000.
The zone, in debug, seems to be correct:
But then I still get events of "cats" being triggered with an area of 42000, and I see no zone attached to it:
The strange thing is that no zone is reported, while in other events I see "near" or "far", like in this example:
is there a problem with my configuration, or is this an issue? I understand that the more specific zone in near should override the general min_area for the camera (set to 30000?). But maybe the zone-specific "near" configuration filters out the detection, but then this is triggered at the camera configuration, which has a lower area threshold?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions