March 15, 2018 at 9:28 pm #103395
Every morning I get an alarm when my cameras switch from black and white to color mode because the sun is coming up. This should not be the case. I don’t need an extra alarm to wake up in the morning!
— JoshuaMarch 16, 2018 at 10:45 am #103629
If the motion detection is disabled during this period, you’ll leave the intruder a chance to break in without you notified, which is a harzard. If a man with a bad will has some basic understanding of IP cameras, he will take advantage of this bug to make evil attempts.March 16, 2018 at 4:10 pm #103685
Maybe this is down to setting the “sweet spot” for the Sensitivity level.March 17, 2018 at 9:26 am #103931
Bob, the cameras report what mode they are in, be it black and white or color. All the system needs to do, is detect when the cameras are switching from black and white to color and vice versa, and just not report movement during that transition, which would be a single frame. This wouldn’t be a security issue seeing as how it’s only a single frame. I don’t feel I should have to work around system limitations by changing the sensitivity levels. I still feel this needs to be added as a feature.
ThanksMarch 19, 2018 at 12:24 pm #104533
Thank you for sharing your perspectives. I will forward to our development team. It may not be an easy-to-implement feature techinically but we are trying.
Thank again!March 19, 2018 at 3:14 pm #104551
Oh, if this is doable in the firmware, why not?
Hope to see a new firmware with this feature.March 19, 2018 at 9:04 pm #104635
Thanks for forwarding my request to the dev team. once again, I offer my development abilities to code this myself and submit a patch to your dev team to get this done quicker, along with the other requests I have made. Can you please check with the dev team to see if this is possible?
ThanksMarch 19, 2018 at 9:29 pm #104646
You need to submit your CV in order to do that… 😀
Just let the dev team do their magic.March 21, 2018 at 2:01 am #104985
I also noticed this issue, and how it should be possible to avoid the camera causing a motion event (itself) by switching between day and night modes. Basing motion detection on changes in the actual picture offers significant capabilities over using a cheap PIR sensor (like the Argus models), but it also leads to irritating issues, like this one and those pesky insects flying close to the infrared LED’s.March 21, 2018 at 3:20 am #105008
+1. Please fix this.
RLC-411WS x 1
C1-PRO x 2
RLC-422W x 2May 11, 2018 at 7:40 am #117653
Agreed, this is pretty annoying.July 31, 2018 at 7:34 am #135451
+1 this is very annoying and my biggest complaint.August 19, 2018 at 5:51 am #140044
+1 also noted, that switching between color / bw caused an alert.
Since I’m a software developer myself, I would apply the KISS-Principle:
– Whenever the camera switches between operation modes: Ignore the motion detection for 2-3 seconds.
– Make this optional available in the firmware with a checkbox like:
 Suppress Alerts on daylight change – Disclaimer: “I understand, that enabling this option
might not trigger a motion alert during the X seconds of operation-mode-switch-over.
Second Option maybe:
 Store footage recorded during operation-mode-switch-over without sending an alert.
December 29, 2018 at 3:05 am #189639
- This reply was modified 6 months ago by dognose.
Hello, any update on this matter? I am having the exact same issue. I would love to see this as a Firmware update to the 5MP cameras.
I also have this similar issue happen if it is a sunny day and clouds randomly go over and it changes the lightning that the camera sees. This constantly triggers “motion detection” as a false positive.
Thanks!December 29, 2018 at 3:18 am #189645
I have listed this as a request to Reolink for a LONG time. I doubt that programming can do much about clouds or trees moving shadows around, or foliage moving in the wind. They detect how many pixels have changed, and if we lower the sensitivity enough to ignore those events, we’ll miss almost everything. I deal with some of this by masking parts of the picture, but have learned to live with it. When the camera changes modes, however, is TOTALLY something the programmer can detect and accommodate. This is just lazy, OR Reolink has to take whatever firmware their supplier produces and the supplier isn’t interested.
I also find it unfortunate that the cameras which are NOT able to turn off their IR LEDs switch to black and white mode when the LEDs come on, even if there is enough light to record in color. I have an Argus mounted close to a RLC-410WS. I have disabled the LEDs on the Argus and mounted a separate IR illuminator several feet away. This solves the “bugs drawn to the LEDs problem.” Since I cannot turn off the LEDs on the 410, I covered them with tape. When the separate IR illuminator turns on, the Argus continues to record in color until the ambient light totally fades, but the 410 switches to black and white when it turns on its own LEDs (that I have covered and aren’t doing anything useful). So, exactly same lighting, but Argus is color and 410 is black & white.
You must be logged in to reply to this topic.