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?

I learned years ago not to base decisions on "promised features" (that may never appear). If a product does not do what I need, I do not purchase it.

Open the Download Firmware web page at reolink.com(slash)download-center
Click on the blue prompt "choose your device from the list +"
Doorbell models are listed by name (not by model number).

Use the Reolink App or Client to determine which specific hardware version you have and select it from the Drop-Down menu.

Good Luck.

I have used FTP with several models of Reolink cameras to store recordings on both Cerebus and FileZilla. (Currently using FileZilla.) I debug FTP issues by setting the "debug level" of FileZilla Server and examining the log file. It is not clear (to me) from the description how SFTPGO is being hosted. (locally? on the web?) A brief look at SFTPGO on the web did not turn up information about how to configure logging.

The Reolink cameras support unencrypted FTP (which I use because both cameras and FTP server are on my local network) and FTPS. The "free" FileZilla Server does not support SFTP.

It might be helpful to ensure that your FTP server is accepting either plain (unencrypted) FTP or FTP over TLS (FTPS) and not expecting SFTP.

Home Hub documentation says it accepts up to (2) 512GB SD cards. Total of 1TB.
Home Hub Pro comes with 2TB hard drive and accepts up to 16TB hard drive.

I had assumed that screws packaged with the junction box are used to secure the junction box to the building and the screws included with the camera would be used to secure the camera to the junction box. It appears to be designed to accept MANY different camera models (the letters A, B, C... etc. should "line up" with the mounting holes in different cameras).

(Just my two cents.....) People are SO accustomed to having the option to force reboots on a regular schedule (daily, weekly, etc.) that companies like Reolink catch a lot of flak if they do not offer the feature. I have kept computers, WiFi routers, etc. on for as much as six months with no ill effects. Most "Internet of Things" gizmos do not offer the feature (smart plugs, smart light bulbs, door locks, television sets, etc.)

The product specifications seem to indicate that the internal hard drive can be up to 6 TB and there can be one external SATA drive that is up to 6TB.
https(colon, two slashes) reolink.com/product/rlk8-520d4/#specifications

There is a support article showing how to remove the internal hard drive and connect an external hard drive.

(Wanted to provide a link to the User Manual for this NVR, but I cannot find one.)

Doubt very much that (a) there is a log file, and (b) that customers would have any method of accessing it. Contact Reolink support directly (email).

I usually troubleshoot FTP issues from the Server log. (I use FileZilla FTP server which has an option for how much detail to put into the log file. Set it to 'debug' level 5.)

(I do not have an NVR..... ) Internet search turned up a Reolink document that mentioned WiFi Repeater, but reading further there were comments about "follow the WiFi Repeater manufacturer directions to..." i.e. that specific document was not talking about a Reolink branded WiFi Repeater.

(would attach a link to the document, but we're not allowed to include links in this Forum package.. sigh)