[Support]: Configuring loitering_time requires removing required_zones for some desired behaviors #11892
Unanswered
d-steve
asked this question in
General Support
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the problem you are having
This is exactly what I wanted out of loitering_time:
#11136 (reply in thread)
Unfortunately, behavior after setting loitering_zone for my config was that snapshots (in frigate+ page) and detections only existed once loitering_time had been met.
Struggled a bit with getting this working as desired until I read more closely that loitering_time defines when an object was considered a part of the zone, as opposed to the object being in the zone and it determining when a detection or alert is defined.
The issue for me was that I had previously had required_zones set, and I had to remove required_zones from my config in certain sections after configuring loitering_time. Specifically:
These may be obvious and expected behavior, but it may cause some people with prior configs and perhaps (ahem) less than perfect reading comprehension to stumble. It can also create some more complicated configs if required_zones is necessary for other purposes.
Documenting this here in case other stumble on this. May not be necessary to document this unless others are stumbling on this.
Version
0.14.0-bccffe6
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
No response
Operating system
Debian
Install method
Docker Compose
Coral version
USB
Network connection
Wired
Camera make and model
Dahua
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions