Forum Replies Created
Certainly frustrating. On the Windows Client 8.2.4, opening the Client causes all of my RLC cameras to connect, but the two old Argus (battery) cameras do NOT connect until I drag them into the viewing window. (see screen shot attached)
It is sort of humorous because after the warranty expired, I uncovered the USB test port inside the battery compartment and these Argus cameras are now 'powered’ from a USB adapter. The Client thinks they are battery powered and keeps after me to conserve the battery. Oh, well.
The product description page seems to indicate that it can (part way down the page – see attached).
I discovered that my Windows Client, v8.1.28, behaves differently for RLC cameras and for my Argus (original battery powered) camera.
The RLC camera Playback has all buttons (see attached image).
The Argus camera Playback does not have the ”Speed” button that the RLC cameras use to resume playback.
My 'guess’ is that the Argus camera was not programmed for different speed playback, which caused the speed button to be left off.
Looks like a definite programming error.
On Windows Client 8.1.28, it appears that the ”Frame by Frame” icon performs the ”Pause” function.
To resume playing, I clicked the icon to the right, selected a speed, and play resumed.
Creating users is a function of the camera, which can be accessed either from the Reolink ”app”, the Reolink Windows Client, or (for newer RLC cameras, from the camera web interface). Users can be admin or ”view only”.
Likewise, cameras can be set to send alerts to more than one email recipient.
UID's show in the Windows Client. Good idea to record them before swapping PC's.
The new Windows Client will scan the network looking for Reolink cameras.
Found all of mine, but I was not concerned because I have all the UID's saved in a text file.
(would not want to be climbing a ladder to physically reach cameras!)February 23, 2021 at 3:38 pm in reply to: No Option to Import Camera Config Since upgrading to Windows Client V 8.1.28 #1289197
I fear the engineering staff have ”fed you a line.” It is almost trivial to code a configuration file with the software version. When importing a configuration file, the first step would be to confirm that it was made on the current firmware. If not, reject the configuration file as incompatible.
There is no reason to remove the ability to save a configuration file and import it into the same camera on the the same software release.
One of the reasons I switched from the original RLC-410 to the newer RLC-410-5MP camera was IR LED management. The original camera had the LED's physically linked to the day/night mode. I had purchased separate IR illuminators to draw insects away from the camera and wound up painting over the LED's on the old cameras. With the new cameras, the controls are independent.
(Have no NVR, so I am not certain that my experience has much in common with yours.)
The RLC-820A has a viewing angle of 87 degrees horizontally. So it would have to rotate 46 degrees for the wall to be at the edge of the picture. I know that bullet cameras can do that, but am not confident that dome cameras can. You are smart to think this through before purchasing.February 15, 2021 at 12:22 am in reply to: Argus2 and ArgusPro no longer emailing notifications. #1280299
My RLC-410-5MP and RLC-520-5MP cameras show the schedule grid in the Windows Client 8.1.28
(see attached screenshot)
I do not have any cameras currently set up to sent email alerts. I realize the ”slider” shows ”on”, but the email definition fields are all blank. (no server, user id, password, recipient, etc.)
Can you please post the URL for the changelog (What's New).
I believe what you intended to ask for was ”allow the user to set the maximum motion in addition to the minimum”.
i.e. the setting now is a number from 0 to 100. Any motion GREATER than this setting triggers ”motion”. Anything under does not. So, if the setting is ”41″, then 40 will not trigger, but 41 up to 100 will.
I very much like this idea. When a cloud moves across the sky and the entire picture changes at once, that is ”too much”.
I would like to see an explanation of why there can be ”time periods” for sensitivity. Is it because color sensitivity is different from black & white?
I am also still want to see some measure of ”time”, both min and max. i.e. if a bird flies across the screen close to the camera, it may trigger ”motion” that lasts only 1 second (of less). I would rather not watch 5 seconds of ”pre-record”, 1/2 sec of bird, then 15 seconds of ”after-record”.
Similarly, on football game days, we put out our college flag which waves constantly in view of the camera. After motion continuing for 30 minutes, maybe it's time to ignore it.
With ranges, the user can decide what they want to see, ranges of sensitivity and time both.
Correct. I had not checked the web interface.
* Windows Client 8.1.28 has Motion, Timer, None
* Camera web interface has Motion, None (no Times).
Obviously, if the Client actually ”works”, then the camera is capable of doing 24/7 FTP capture.
What is 'broken’ is not the basic camera firmware, but the camera web interface.
Of course, if the Client setting fails to result in 24/7 FTP capture, then.... oh, my.
How strange. My app is 8.1.28 and the firmware on my two RLC-410-5MP are
(Having no User Manual, I am left to wonder) What is the meaning of the ”Timer” option on FTP recording?
see picture attached.
My camera is set to record ”Motion” all day. I would think that ”Timer” might mean record whenever the hour is ”Blue”?
There are only three choices, Motion, Timer, and None. Pretty obvious what Motion and None mean.