[Config Support]: Do zone parameters have priority over camera ones?

[jiiins]

Describe the problem you are having

For a camera I have these settings:

    objects:
      filters:
        person:
          min_score: 0.60
          threshold: 0.67
    zones:
      zone_1:
        coordinates: 927,112,285,205,424,450,966,422
        filters:
          person:
            min_score: 0.60
            threshold: 0.67
            max_area: 5000

I would expect persons with size above 5000 to be excluded from zone_1, but they get detected anyway. What is the right way to accomplish this?

Version

13.2

Frigate config file

not relevant

Relevant log output

not relevant

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]

all that does is decide if the object is considered part of that zone, the zone filters are not used when determining if the object is a true positive or not

[NickM-27]

Currently there isn't

[jiiins]

Do you know any workaround to be able to filter out false positives, when the camera has a far view?

[NickM-27]

would be good to see an example

[jiiins]

This is the same imagine I used in another conversation a while ago:

The problem is that if I limit the max_area on the entire camera, a person closer to the camera will be excluded as it will be larger because of the shorter distance. In the zone where this false positive occurs, a person's max size is 5,000, while in the middle of the yard is about 20,000.

[NickM-27]

yeah that's a tough one, seems like one that would be difficult to filter out. A more accurate model might be the most straightforward way to reduce that

[jiiins]

I managed to split the camera's view in 2 separate feeds. What's the best approach? Shall I treat them as different cameras using a common zone, and enable recording on the original (complete) feed?