I have mentioned this several times. It makes SO much sense.

I also think there is no reason not to have SETTINGS for several parameters.
"Prerecord", for example, seems to be a fixed number of seconds or none at all.
The user should be able to set up to some maximum value, say 0-20 seconds.
Post record is the same.

I finally solved the "flying insect problem" by purchasing separate Infrared LED lights and placing them 6-8 ft. away from the camera. Bugs are drawn to them and do not appear to be BIG BRIGHT OBJECTS to the camera.

I believe under Profile... Settings (gear symbol) there are options for what notifications to receive.

I believe that all important settings are kept on the cameras themselves. When the Client program starts on the new computer, it will scan the LAN looking for cameras and import the settings from them.

I agree with Fiona that FTP is based entirely on the server IP address. When the server is on the LAN, FTP will not attempt to access the internet.
(caveat: I have no NVR. My individual cameras FTP motion recordings directly to the LAN FTP server.)

On the cameras, there is an option in the FTP setup to "Test" the FTP settings. Took me several tries to get the FTP logon information/password/directory parameters correct.
Should be relatively simple to do a "Test" with a live internet connection and also without a live internet connection.

Absolutely. I have two "battery" cameras that are USB powered. The battery cannot possible run down, so this alert is not useful.

I know of no method to set a constant FTP file name on the Reolink RLC cameras. (Battery powered cameras do not support FTP at all.)
(Lack broad experience with web cams, but some brands such as Wyze and Arlo also lack FTP.)

The effect you seek may be possible some other way, such as:

• Have an app that watches the FTP server and when a new file shows up, erase the previous file and rename the new one.
• Use something besides FTP to gather images from the camera. For example, this article describes how to load JPEG images to a web server:

support.reolink.com/hc/en-us/articles/360007011233-How-to-Capture-Live-JPEG-Image-of-Reolink-Cameras-via-Web-Browsers

I agree. Would even go so far as to ask to be able to specify the notification sound for each camera and the volume level.

Click on the Plus sign ("+") and the Reolink Windows Client application will automatically search the local IP subnet for cameras and display any that it finds.
To add cameras that the program does not find on the local network, enter the UID code for the camera in the box and the program will search the Reolink "Cloud" for the camera, similar to the way the Reolink Apple or Android app does.

My guess: People will be ice skating in.... (that place) before Reolink releases a camera with PowerLine built in. That's not their 'niche'.

A substitute would be either:

• Comtrend PG-9172POE Powerline Ethernet +PoE Adapter ($70US) which bundles Powerline and a PoE injector into one box, or
• A Powerline adapter plus a PoE injector (these are really cheap).

Would you mind sharing the reasoning for not using Google to watch for and notify of new Reolink app versions?

A full resolution 8MB (or 12MB) image might be "too large" for many email systems to process. FTP download would not have this restriction.

@user_987361122091173_987361122091173 Agree entirely. What is the point of (my camera) being 12MB (4,512 x 2,512) if the size of one frame is 1,061,337 bytes when it should be 11,334,144 bytes.

@grod777_275772032561320 Several of my Reolink cameras backup recordings to folders on a hard drive using FTP. This script runs every day to eliminate JPG files older than 4 days and MPG recordings older than 21 days:

ECHO Job begins %date% %time%
ECHO Remove JPG files older than 3 days
Forfiles /p D:\Reolink\E1Outdoor  /s /m *.jpg /d -3 /c "cmd /c del @file /f /q"
Forfiles /p D:\Reolink\FrontDoorCam /s /m *.jpg /d -3 /c "cmd /c del @file /f /q"
Forfiles /p D:\Reolink\HondaCam   /s /m *.jpg /d -3 /c "cmd /c del @file /f /q"
Forfiles /p D:\Reolink\PickupCam  /s /m *.jpg /d -3 /c "cmd /c del @file /f /q"
Forfiles /p D:\Reolink\ShedCam   /s /m *.jpg /d -3 /c "cmd /c del @file /f /q"
Forfiles /p D:\Reolink\SideCam   /s /m *.jpg /d -3 /c "cmd /c del @file /f /q"
Forfiles /p D:\Reolink\TestCam   /s /m *.jpg /d -3 /c "cmd /c del @file /f /q"
ECHO Remove MPG files older than 21 days
Forfiles /p D:\Reolink\E1Outdoor  /s /d -21 /c "cmd /c del @file /f /q"
Forfiles /p D:\Reolink\FrontDoorCam /s /d -21 /c "cmd /c del @file /f /q"
Forfiles /p D:\Reolink\HondaCam   /s /d -21 /c "cmd /c del @file /f /q"
Forfiles /p D:\Reolink\PickupCam  /s /d -21 /c "cmd /c del @file /f /q"
Forfiles /p D:\Reolink\ShedCam   /s /d -21 /c "cmd /c del @file /f /q"
Forfiles /p D:\Reolink\SideCam   /s /d -21 /c "cmd /c del @file /f /q"
Forfiles /p D:\Reolink\TestCam   /s /d -21 /c "cmd /c del @file /f /q"
ECHO Remove Empty Directories
Robocopy D:\Reolink D:\Reolink /S /MOVE

It probably would have worked to simply run the Forfiles command on D:\Reolink rather than having a line for each camera folder. Once it was working correctly, I have not looked at this batch file for a couple of years. Probably I had some idea that it might be useful to keep files from some cameras longer than other cameras?

Using the vendor smartphone app is the easiest way to gain access to cameras when not connected to the local network. "no muss no fuss. It just works."
Many RLC cameras support http and https access (RLCs and some others, such as the E1 Outdoor) Any web browser can connect directly to the camera and view live video or saved recordings.
The major impediment to this is that doing so requires that the user set up a method to connect through the router to a specific local IP address - for each camera!

Imagine there are three cameras at 192.168.1.21, 22, and 23. Because http uses port 80, that means the router will have to be set up to forward one outside connection to 192.168.1.21:80, another port to 192.168.1.22:80, and another port to 192.168.1.23:80. for example:

External port 8081 to 192.168.1.21:80
External port 8082 to 192.168.1.22:80
External port 8083 to 192.168.1.23:80

The user has to remember when using the web browser to enter the public IP address of the home router and the correct port number for each camera.
PLUS... this means that anyone who scans ports 8081, 8082, and 8083 will find they are "open" web servers and can attempt to hack into them. (not likely to succeed if the camera password is strong.)

SO much WORK. Why not just use the app to start with?

@wisemanjaw What indicates that AT&T is blocking access to those Oracle servers? (error messages on the cameras or Reolink 'app'? Notices from AT&T? Entries in an AT&T log file?)

I have always sent an email to support (at sign) reolink.com
(this user interface does not allow entering URLs. What a drag!)

When a camera is defined in the Reolink 'app' using the UID, that UID is linked to the User's Reolink account. Thus, the only way to access the camera is to know both the camera UID and the Reolink account credentials. That is why I think this is a question for Reolink Support.

If a camera is transferred to another owner but has already been defined in the Reolink account of the original owner, my understanding is that attempting to add the camera to another Reolink account will fail. If the camera has been 'deleted' from the original owner Reolink app (in every device that the app has been installed on), then it is probably available to be assigned to a new owner.

This also sort of "calls out" for a practical experiment. i.e.

• Set up a Reolink user login.
• Load the Reolink app on some device.
• Add a camera using the UID to that device.
• Set up a second Reolink user login
• Load the Reolink app on a different device.
• Add that original camera to the second Reolink app using the same UID.

What happens?

Sounds like a perfect question to email support (at sign) reolink.com about.

Has this camera been Factory Reset and reconfigured?

Each RLC camera is built around a specific camera module. ColorX is made possible by the camera module, not by programming. The RLC-842A "does what it does" and cannot be made to do anything that the camera module was not designed to do.