#How to not constantly alert on a stationary car?

1 messages · Page 1 of 1 (latest)

bleak cloak
#

I have read through the configs, but I am still a little confused. What is the proper way to not constantly alert on a stationary object, specifically a car? I want to have the alert and review for a car pulling into the driveway, but I don't want it to constantly be tracking and alerting on it.

finite dew
#

assuming you are referring to Frigate

#

we will need to see your config, and you'll likely want to check the debug live view and see what the bounding boxes look like

bleak cloak
bleak cloak
finite dew
#

best just to share the whole thing

bleak cloak
finite dew
#

seems to be fine so the debug live view is where you'll want to look first with both motion and object boxes enabled

bleak cloak
#

There is currently no box around the stationary car. It will show a red box around a car driving down the road, but it does not trigger a review event

finite dew
#

is detection enabled? that would mean the car wasn't detected

bleak cloak
#

Yes, detection is enabled.

vague cove
#

it could be that the detection is unreliable (depends on lighting?) so it keeps seeing the car appear and disappear. that would explain you getting repeated notifications.

bleak cloak
#

I removed "car" from the "object: tracked" list and so now it doesn't trigger on a car at all. When I included car in that list is when it seemed to constantly trigger on the stationary car.

bleak cloak
#

I'll try to add car back to the tracked list when the weather is more calm and see how it does.

bleak cloak
#

I still haven't been able to figure this out. It seems that no matter what, it is always alerting and tracking the car that is parked in the driveway.

#

Is there a config that will allow it to track the car, but then after it's stationary for like 30 seconds, to stop tracking it until it moves again?

finite dew
#

Is there a config that will allow it to track the car, but then after it's stationary for like 30 seconds, to stop tracking it until it moves again?

That is how it works by default

#

as long as the object detection is consistent and the box doesn't move too much

#

That's why the suggestion was to watch (or perhaps screen record) the debug live view so it is clear what is happening that is causing the object to stop being considered stationary