Night motion detection whats best solution to car light triggers?

ripdo

Hello

I have the 422w dome camera. My main use is to have motion detection within a set zone trigger off only by people. Now do these cameras use PIR technology for heat, or just pixel motion? I had one trigger another another every time a car drives past, how do I reduce this problem, do I have the wrong camera?

Thanks, Dan

Crimp On

(It's just my opinion, but) Yes, you have the wrong camera. Except for the battery-operated Argus line, all Reolink cameras detect motion by "how many pixels changed". The sensitivity setting allows you to require more (or less) pixel change to trigger "motion." If you search through the posts, this is one of the biggest frustrations of Reolink users. If you've already "blacked out" all of the screen except for critical areas, you're screwed.

Some of the instances that people mention are: (1) insects which are drawn to the infrared LED's and appear "really bright" as they fly rapidly close to and past the camera. They are gone in a flash, but they are "motion." (2) When the camera changes from "day" to "night" mode, ALL of the pixels "change", so the camera triggers motion. (3) when plants rustle in the wind or tree shadows move quickly in the wind. and (4) when auto headlights go by or shine off of an object. I have reported these issues as have many others.

My recommendation to Reolink was to allow the user to specify "how long" motion has to continue before it will trigger recording. i.e. if something "moves" for less than one second, I don't care about it. (or 2, 3, 4 seconds. Let me pick.) That would eliminate most of the frustration. If the UPS driver can walk to my door, place a package, and get out of range in less than 2 seconds, then I won't record it. Oh, well.)

Changing how the camera software detects motion is not a trivial programming effort. I suspect that Reolink may not have created the camera software themselves. My guess is the reason Reolink cameras are inexpensive relative to other brands is that they are "integrators" of off-the-shelf components and have very low overhead. Thus, they may not have the resources to rewrite complicated parts of the camera firmware.

PIR motion detectors are not perfect, either. They have definite range limitations and do not detect something moving directly toward the camera as well as they do something moving "across" the camera.

Personally, I'd like to see a camera with BOTH pixel and PIR motion detection, although I have never seen such a camera for sale.

ripdo

Hi

Thanks for your reply. Funny as it may not be I had got this camera because I had such a camera that does have both pixel and PIR detection, the Arlo Pro 2. It was a dam expensive trial but Netgear Arlo people had released a new firmware which totaly messed up the Arlo pro 2. My biggest issues was the motion zones randomly failed, when I say randomly I mean 1 day or night it could be fine, then next two days constant triggers even if I had made a trigger zone right off the screen and tiny, a car 15 meters away would trigger it, this was simply randomly failing to work at all, even ignoring people walking into the zones.

I didnt realise that this camera does not have PIR till yesterday, but I have only had this 2 days today. If the arlo pro 2 had it zones working I think id be fine as I like everything else about it. Iv been trying out Blue Iris demo but cant seem to get it to be sensitive enough at the moment, not sure how to set up yet. The way things are going with everything triggering it off it makes having motion triggers nothing more than a gimik as nobody can control the sun, shadows, and bugs so yes a time delay is the thing and maybe Blue Iris has this?

I would have got the Argus 2 but then found it dont support zones.

Dan