Ability to configure lightning threshold behavior regarding keeping recordings

[Protected]

Describe what you are trying to accomplish and why in non technical terms I'm trying to keep camera-initiated panning, tilting and zooming (such as by the camera's patrol or motion tracking features) from triggering Frigate's detections. A lot of storage space is being wasted because if there are detectable objects standing still in range and the camera pans, those objects trigger video snippets to be logged as Detections for review. I can't simply mask those objects out because panning means they change positions relative to the image.

Describe the solution you'd like I'd love it if there was a setting (can default to 1.0) representing the maximum proportion of the stream's image that can "change" for detections to be triggered. Above that proportion, detections would not be triggrered. For example, if set to 0.5 and more than 50% of the image changed, detections would not be triggered. (I don't know how this works internally - 50% of pixels sufficiently changed color?)

This would keep panning from triggering detections because since panning shifts the entire perspective, the "entire" image (potentially) changes.

This would be inadvisable for ground level cameras such as doorbell cameras where the entire image can quickly be covered by a moving target. However, cameras installed in high places never have objects close up under normal circumstances, and can make use of this feature.

For the sake of hardware efficiency, if set to the default 1.0, the entire process can simply be skipped.

Describe alternatives you've considered I would prefer if Frigate could be in charge of controlling PTZ via ONVIF and the camera itself never initiated its own PTZ. However, it appears that my camera doesn't support the requisite ONVIF features for autotracking (relative PTZ).

The brand of camera I acquired was my fifth choice; others weren't readily available or convenient to acquire in my country. That said, my experience with the entire process of interacting with this brand, their store, delivery and installation was extremely good, and I would happily buy from them again. A feature like this seems like a simple way to improve usability of these cameras with Frigate.

Additional context Reddit conversation

[Protected]

(EDIT: This was in response to a removed question about whether lightning_threshold would suffice.)

According to the reddit conversation, that setting is inadequate because detections are still logged. But I expect it would be similar in implementation?

[NickM-27]

What you're describing, assuming you mean object detections, is exactly what lighting threshold is

[Kedryn]

I asked this last year, but they told me that this would break how Frigate works because would stop detections.

That is what we are asking for :)

[NickM-27]

It's not clear what you're asking for, as I pointed out the option as described in the OP already exists.

[Kedryn]

I've already tested Lightinig Threshold in the past for that same reason as per your post on another thread #14578:

"Lightning threshold does not stop motion from being detected entirely. Instead, it stops additional motion detection from running once an initial amount of motion is detected above the threshold."

and

"I'll update that, the feature is designed to reduce false positive object detections and motion usage during periods of high motion. It will not stop recordings from being saved as users still expect their ptz camera to record while it is moving, for example."

and lastly: "The consequence of not recording during this is the potential of missing something important like a ptz camera following an object using auto tracking or seeing something while moving.

The consequence of keeping this motion recording is potentially a couple recordings segments that take up a few megabytes and something that takes almost no time at all to review in the timeline in the UI."

but we are aware of that. We are asking to be able to chose to skip that motion. My problem is that i have a light bulb near the zone the camera is pointing.

My 2 options are:

1. Use MOTION for turning light on, but then it will loop because as soon as the light switch off after like 3 minutes are passed, that change in lighting is a MOTION and the light turns on again, in an infinite loop
2. use DETECTION, but that means if something moves that is not recognized, lights wont turn on.

If there is a way to use lightning threshold to completely skip a motion (IR switching, light bulb turning on and of, camera motions) we can choose to skip or not based on our use cases. Right now we simply can't.

[NickM-27]

right, which is why I originally said

What you're describing, assuming you mean object detections, is exactly what lighting threshold is

otherwise, this would essentially be a request for another lightning threshold configuration but one that would block all motion, or perhaps a way to control the behavior in case lightning threshold is triggered.

[Kedryn]

right, which is why I originally said

What you're describing, assuming you mean object detections, is exactly what lighting threshold is

otherwise, this would essentially be a request for another lightning threshold configuration but one that would block all motion, or perhaps a way to control the behavior in case lightning threshold is triggered.

Exactly what we need Another NVR has the option "SKIP MOTION IF % OF THE SCENE CHANGES" and then a slider. Befor Frigate i had it at like 70% and would skip all IR or LIGHT changes. As well as storms.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Kedryn]

no stale plz