Posts made by carbonita_23339214035

Problem has not recurred since, and camera is still operating. SDcard is a probably Samsung PRO endurance, which has been the most reliable for my 10+ cameras. Another issue with this version of the camera is that the voltage tolerance is tight, one must use the included power supply. Previous version of this camera did not have this issue.

@coldevening thanks for the alert. More details on the busyBox vulnerability: https://www.pcmag.com/news/366949/internet-of-things-devices-have-a-serious-security-problem

Problem recurred while camera was protected from rain. Electrical contact cleaner spray for the card and slot seems to have remedied for now.

Playback works as expected for video recorded 11mar2019, but still fails for 10mar2019 after 0200. Playback on android app works fine for all time periods. http client has the proper DST, now matching the camera fw time (which is correct). Will just have to wait for the changeover to Standard time to see if bug can be reproduced.

Interestingly, the http client does playback correctly, albeit with slider-bar time incorrectly at Standard Time. Camera FW switched to DST properly.

Is anyone able to playback video recorded after 02:00 local time? This was the time for the switch to Daylight Savings Time in USA (California). The video plays back as expected prior to 02:00, but fails with no response after this time.

Reolink PC client: 7.2.2.28
Windows 10
Latest posted firmware on 9 cameras

Adding an outlet to the junction box, and then plug in the reolink adapter should work. If exposed to weather, use a weatherproof in-use cover over the outlet. Make sure you have wifi signal at the location before doing all the work, of course.

How about a separate sensor for mbox opening, then use that time-stamp to check the video? An ESP8266 has gpio and wifi. Probably not good for real-time alerts (but IFTTT should work), but possibly ok for daily review.

I agree that it sure would be nice to have an expanded cgi command capability. Brainstorming, one could put the camera inside the mailbox, which would trigger only when opened. Probably need PoE if your mbox is a metal Faraday cage. Alternately, its fairly straightforward to build a rpi zero camera, and then gpio sensors can be added (contact sensor might be easiest in this use case).

Update: After SD card was again not detected, inspection of card and o-ring sealed slot showed no obvious issue (e.g., no condensate). Moving camera under the eaves to protect from direct rain.

Update: SD card spontaneously (meaning no change in network nor device) recording at ~10:00AM local time (as air temperature rises to 15C). Possibly condensation/environmental effect(?)

Has anyone else seen a "No SD card is detected" in the app at playback? I've had an SD card installed and operating since the RLC-410W was purchased directly from Reolink in November 2018, but this message is now displayed. Rebooting does not resolve. Live viewing is fine. Next step is to take down the camera, inspect, and bench-test.

fw v2.0.0.158_18071807

With the >10 cameras in my system, most with overlapping views (as are yours), I've learned that the sensitivity must be tuned separately for each camera. One can't presume that the same sensitivity will work for all perspectives for the motion detection algorithm (unfortunately -- this would make set up much quicker). There will be false negatives with the algorithm used by any camera (I have different brand cams with differing algorithms mounted on the same pole (one is acts as an ALPR), and at times only one camera captures a passing vehicle. BTW, I use the Windows Reolink client for recording, not the NVR.

Carl - Thank you for the response. There doesn't appear to be a startup option in the GUI that forces fluent mode on live view startup. I don't want to bother your support team, since the issue appears to be network congestion (100BT PoE switch + WiFi), as the issue resolves with (manual) switching to fluent on each camera.

Does the Windows PC client have startup options available? I have 9 Reolink cams, but when I listen to live audio there is stuttering. Changing all cams to fluent (from auto) fixes the stuttering issue. An option to start with a flag/argument (e.g., reolink.exe /fluentMode) would save the task of clicking each camera to change to fluent.

Set camera1 to black&white (BW) mode. IR LEDs will turn on when (visible spectrum) photocell is not illuminated. Cover the photocell (tape, paint, desolder) if LEDs must stay on even when lit. Add an external IR illuminator if needed.

Set camera2 to color only mode. The built-in IR cut filter will remove any IR light, including from camera1.

I do this with my mix of 410/411's, but for two-legged buggers, not 6-legged bugs (not to disrespect the useful bees:) ).

Carl - Are API's available for any other cameras?

It might be best to take one of the cams and configure when its unmounted and next to the WAP that will ultimately provide connectivity, then do as Carl suggests with hardwired ethernet, then if you're comfortable with router settings do the static IP setting. Might as well verify that the cam has the latest firmware installed as well, and of course change the login credentials.

What has been tried to resolve the issue? For my mix of Reolink 410/411/etc, I've found that allocating static IP addresses to each camera allows the windows or android client on the same LAN to connect within ~5seconds (was intermittently >50sec with dynamic ip).

Camera is being RMA'd (unfortunately, no free return shipping for full warranty period) following confirmation of failure by support team. Caveat to those using support: the customer management system emails the UID and credentials even when only provided on the reolink website. Otherwise support is quick and complete.