Replies: 4 comments 3 replies
-
Yes i do agree with you. |
Beta Was this translation helpful? Give feedback.
-
Here is something in line with this issue for reference. Running the dev code (from 2021.06.10) There is a defined mask here. But it still detects (what it thinks is) a person. |
Beta Was this translation helpful? Give feedback.
-
Rather than a mask, I created a region and a label for "person" and "trigger_recorder: false". This will do for now. |
Beta Was this translation helpful? Give feedback.
-
I just pushed a new version of |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
In the README, it says about a Mask:
Masks are used to exclude certain areas in the image from triggering motion.
But what about detection? If it excludes areas from triggering motion, should it also exclude from detection?
As you know I'm using the dev branch - updated as of yesterday - but it will detect objects and record a snapshot and video, when the objects are in my mask area. The workaround - which worked but isn't feasible - is to create a zone (instead of a mask) and have it only record when there is a kangaroo detected (I'm exaggerating) or something that you wouldn't see in that zone. Yet I think a mask is the appropriate place to have a "not detect nor record" rule. Do you agree?
Thank you
Beta Was this translation helpful? Give feedback.
All reactions