Posts made by carbonita_23339214035

Thanks for sharing the improvement, which has me thinking about upgrading my antennas. Are you able to verify the reception improvement (in decibels) from your router/ap? I ask, rather than try it myself, since my cameras are hard to reach.

AFAIK, this is the most recent fw available (dated 2018may22). I only see *180207 fw (2018feb07) on the reolink.com/firmware site.

Feasible to check if lan (non FTP) recording is full res as debugging step? On windows client, its Local Settings > Record Settings > Stream Type > Clear. Works for my 4mp RLC-411ws/410s .

FYI for V7.2.2.20
Change Log:
1. Supports more Reolink camera models
2. Add "System State"
3. Add "File Type" for FTP Settings
4. Some bug fixes

Bob - Is this 2.0.0.126_180522* fw available for download? This version is not visible on reolink.com/firmware.

My first (bought in 2016) RLC-411ws mounted outside had a moisture intrusion problem as well. Reolink replaced very quickly under warranty, and the replacement (and all other Reolink's) have had no issues.

For those needing a sun lens shade for an RLC-410s, a design is available for 3D printing. Made using by Boolean of 65mm inner diameter 1mm thick tube with a 80x42degree (the FOV of the camera) pyramid. Stay glare-free, reolink'ers!

https://www.tinkercad.com/things/7rdrs7sZZ7x-sunlensshade

Is it feasible to post the documentation of the commands? They sound interesting, and possibly useful.

Bob - Any estimate for the fix being available? The contrasting timestamp background feature in the new fw was nice, but the UID not working was a showstopper. TIA.

Thanks for the quick verification, Bob. It's great that Reolink has continuing firmware and client updates

One last screenshot, verification of new fw install. Part 3 of 2
18020702_06.jpg

Part 2 of 2, additional images.
18020702_03.jpg
18020702_04.jpg
18020702_05.jpg

Bob - Thanks for verifying. Screenshot sequence below, 1) starting with working-as-expected RLC-410s running 17112702 firmware with access via http or windows client, 2) installing 18020702 firmware, 3) failure using UID, 4) success using IP addr, 5) unusual UID string via http client.
17112702_01.jpg
17112702_02.jpg
17112702_03.jpg
18020702_01.jpg
18020702_02.jpg

While debugging, in turns out the UID shown in the http interface differs from the UID shown in the windows (and android) app. The anomalous UID differs in string length by 4 chars (20 character string), and does not begin with the XCPTP sub-string. I've rolled back to previous firmware (170830), and all is copacetic again.

After updating a RLC-410s and C1 to the firmware posted 02apr2018, 1288_180207*, the Windows nor Android client would "login" to these cameras. Changing from UID to IP address login allows the login, but is problematic for DHCP networks. Anyone else have this issue?

Does anyone have the lens thread information for the RLC-410? I'd like to have a wider field of view (FOV), and am considering swapping the lens. From video teardowns of other brands, M12x0.5 may be the thread. TIA.

ICYMI New version of the PC client 7.2.2.18 dated 15mar2018 is available from the download site. For those with multiple cams, you may want to record your UIDs for entry into the new software (no import capability). Release notes from the download manifest below.

Release note.txt

1.Supports Reolink battery powered security cameras (for Reolink Argus, Argus 2 & Keen).
Here is the instruction to add the camera to Reolink desktop client.
https://reolink.com/faq/add-argus-reolink-client-windows/

2.Supports semi-transparent OSD background.

3.Adds the ¡°buzz¡± prompt tone when the IP cameras detect motion events. You can enable or disable the prompt tone via the local configuration.
4.Supports multiple languages.

Has anyone seen issues with email NOT being sent, even though video IS captured via PC client and on camera-local storage? This occurred with all of the 9 Reolink RLC-{410s,411ws} and C1's for a 20-minute period of time today. The cams use smtp gmail, and have worked properly prior to, and subsequent to, this anomalous period. The email interval time is set to be shorter than the interval of motion events. The cam networks were connected to the internet, since another brand of cloud-recording cam was operating.

Does the firmware update 1055_17110901 patch the KRACK vulnerability?

@jc -- thanks for sharing your nice mod. I'd also be interested in hearing from the design team as to the battery choice.