@gregtakacs commented on GitHub (Feb 4, 2024):
So here is the issue: I have no motion boxes but object detection keeps triggering.....
https://github.com/blakeblackshear/frigate/assets/20398441…
@NickM-27 commented on GitHub (Feb 4, 2024):
Right, that's going to happen because the boxes are inconsistent. But once the object is lost only motion will make it be detected again so motion is…
@gregtakacs commented on GitHub (Feb 4, 2024):
Increased interval to 3000 (10 minutes) and reduced stationary threshold to 20 (4 seconds) and things seem to be much more stable, meaning I don't…
@gregtakacs commented on GitHub (Feb 4, 2024):
So overnight shows what's expected. On the right bay remained tracking and locked for 12 hours, until camera switched from night to daylight…
@NickM-27 commented on GitHub (Feb 4, 2024):
We have ideas to make things better in future versions but it is difficult especially when detection is less accurate / consistent
@NickM-27 commented on GitHub (Feb 5, 2024):
https://github.com/blakeblackshear/frigate/pull/9684 might help with this issue at least a little bit
@github-actions[bot] commented on GitHub (Mar 7, 2024):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@NickM-27 commented on GitHub (Feb 3, 2024):
This could be due to the motion detection being more sensitive by default. The docs have a guide for tuning that.
I'd say this is either a bug or…
@gregtakacs commented on GitHub (Feb 4, 2024):
OK, so now that I read the release docs I guess some of the "issues" make more sense.
I appreciate the effort and the support!
Unfortunately…
@gregtakacs commented on GitHub (Feb 4, 2024):
I actually just set my config to that last mode and now I get data with the events but I don't want to :-) I just don't want these events being…
@NickM-27 commented on GitHub (Feb 4, 2024):
You should tune your motion detection like was previously suggested
@gregtakacs commented on GitHub (Feb 3, 2024):
that is already how frigate works. If a new event is created that is because the object was not detected for max_disappeared frames
What I meant…
@NickM-27 commented on GitHub (Feb 3, 2024):
currently there is no way that a car that stops being detected and is considered lost will be continued on the same event.
max_disappeared is how…
@gregtakacs commented on GitHub (Feb 3, 2024):
Yeah, so to summarize my experience is from several issues:
- Motorcycle detection is poor-ish which means that they keep getting detected and…
@gregtakacs commented on GitHub (Feb 3, 2024):
OK, more data point:
I had updated to the latest frigate on 2/1 and that is when this behavior started. Before that my events were correct(ish). …
@NickM-27 commented on GitHub (Feb 3, 2024):
Is there a way to treat a new detection the "same" if its area/location/height/width is within or close to the previous one within a certain…
@github-actions[bot] commented on GitHub (Mar 6, 2024):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@NickM-27 commented on GitHub (Feb 3, 2024):
I'd be curious how the car detection performs if motorcycle detection is not enabled
@gregtakacs commented on GitHub (Feb 3, 2024):
@gregtakacs commented on GitHub (Feb 3, 2024):
yeah that is going to cause a lot of erratic detection. motorcycle has very few examples in the COCO dataset and remember that the COCO dataset is…