[Config Support]: Motion detection for light changes and IR

[lordraiden]

Describe the problem you are having

As seen in the video the process is the light is on, goes off, IR camera gets activated, the process will continue with light on, camera IR disable. etc

I have tried everything but still frigate detects this as motion, Is there a way to fix it? any advice?

I'm using this parameters:

Version

System 0.13.2-6476f8a

Frigate config file

motion:
      mask:
        - 903,65,1664,65,1664,0,903,0 # timestamp reolink
        - 681,1234,681,1276,629,1276,629,1234 # elevator numbers
      threshold: 200
      contour_area: 30
      lightning_threshold: 0.3

Relevant log output

N/A

Frigate stats

No response

Operating system

UNRAID

Install method

Docker Compose

Object Detector

CPU (no coral)

Any other information that may be helpful

No response

[NickM-27]

Motion is pixels changing, in this case almost every single pixel is changing. If that is not detected as motion then nothing will be. Is there a reason why you need this to not be detected as motion?

[Kedryn]

Or you could just have a cool down before the light will turn back on again. Frigates motion detection is not as sophisticated as other system which lack intelligent object tracking. Triggering off an object is what I do and it works perfectly

You can also use lightning threshold as that is what the option is specifically for

What a "cool down" will solve? When the light turns off, a movement is detected.

I already tested lightning threshold to 0.3 (minium value accepted), but it does not solve the problem.

[NickM-27]

basically, once the lights turn off you require a few seconds before the lights can turn on again. You are using motion detection in a way it is not designed to be used for in frigate

[Kedryn]

basically, once the lights turn off you require a few seconds before the lights can turn on again. You are using motion detection in a way it is not designed to be used for in frigate

Uhm, no, that's not what i'm trying to explain.
Let me try again.

I have my main entrance like in this photo:

on the top left you can see a light bulb.
When movemente is detected, after sunset, the light turns on.
After 3 minutes, the lights turns off.
When the lights turn off, there is a massive motion detected, like 100%, that turns it on again.
The "lightining_threshold" can't go lower than 0.3, so it's not enough.
Before switching to Frigate, i was using (and still i'm, but only for scheduled recordings), Blue Iris.
In BI there is an option that skips motion detection when it is greater of a chosen percentage (i use 80%), and it works flawlessy in my situation.

The same is for the garage,
With Frigate, right now, my lights turns on at first movement detected, and turns off at sunrise, with a glitch every 3 minutes.

[NickM-27]

Right, I'm telling you that you should change the logic so that it won't turn on the light immediately after it turns off.

For frigate the detection runs at 5 fps, it's entirely possible that that first frame after the light turns on doesn't have > 30% of the pixels changing yet so motion is detected then a frame or two later the lightning detection kicks in. That would explain why you still get motion detection triggering. You can fix it the way I described.

[Kedryn]

being simpler for my setup with home assistant, i tried to disable the motion and detection for like 8 seconds BEFORE turning off the light.

Turn motion/detection off->turn light off->wait 8 seconds->Turno motion/detection on

When i turn motion and detection on again, frigate signals motion and the light turns on again.

I'll try the "cool down" route for the light on