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.

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

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/pa*sword/directory parameters correct.
Should be relatively simple to do a "Test" with a live internet connection and also without a live internet connection.

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

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.

Could you please identify the cameras involved?

I have found that battery operated cameras give the appearance of being "disconnected" when they go into some sort of power saving mode. Selected the camera "wakes them up" and the app or the Windows Client connects to them.

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

@reolink-fiona

And, there is now a Beta version of Windows Client 8.4. My guess is that Reolink engineers will be more likely to respond to problem reports about the latest software version.

This is just my "two cents"....

When products boast of being "waterproof", I snort, "oh, sure", and mount them under the eaves if at all possible.

Search for Corner Bracket. A user described using one from another company.

Thanks for the notice. Just for entertainment, I opened the Windows Client and selected "Update".

Such Fun!

I have an RLC-510WA. Upon reading this, I thought, "What the hell?". I have always set camera "Clear" resolution to be the highest possible. Sure enough, this observation is correct.
The higher resolution picture is 4:3 and the lower resolution is 16:9.

I believe this is related to (a) the actual camera sensor and (b) the computer display (monitor). My monitor for example, has a resolution of 1,920 x 1,080. (It is also VERY old. Have not considered upgrading the monitor because there is not physical space for a taller monitor.) Thus, 2,560x1,920 is more pixels than my monitor has available. In addition, even when the Client program is "full screen", only a portion of those 1,920 x 1,080 pixels are available to display the camera image. Thus, the Windows Client must take the camera image and shrink it so that it will fit inside the space where the image is supposed to appear. Suppose the number of vertical pixels in the display area is X. Fitting 1,920 pixels into X results in a ratio of Y = X/1,920. Multiply 2,560 by Y to get how many pixels wide the picture will appear.

If the pixels are "square", then 2,560 x 1,920 is a ratio of 4:3. 2,560 x 1,440 is a ratio of 16:9. I have taken snapshots of the RLC-510WA set to both resolutions, and the 16:9 image does indeed appear "flattened". However, looking closely the two images cover exactly the same view. Each of the four corners of both pictures are identical.

The RLC-510WA specs quote a resolution of 2,560 x 1,920 pixels (4,915,200 pixels), which Reolink describes as 5MB (close enough). Thus, a Clear resolution of 2,560x1,920 will result in the most accurate representation of "what the camera sees." But, what if the customer network cannot support this amount of bandwidth? Lower resolution images require less bandwidth.

What an interesting puzzle. Thanks for pointing this out.

8.14.0 produces sound on my Windows 11 (Home) Client.

@markarron9_504005354344625 I do not accept that a box around a stationary automobile that is parked across the street can be a "Motion Mark".

2 minutes and 24 seconds into the installation video, it describes mounting on the ceiling.

I would post a link here, but........

Using the Windows client, the mouse "scroll wheel" zooms the image. I then use the mouse to move the image around.

@tchubaba I was thinking of a very specific firewall rule.
i.e. "allow this one IP address (camera) to connect to this one IP address (Reolink Client machine or computer running web browser if it is different) on these specific TCP ports"
My thinking is that it is actually not clear whether a "connection" has been made or not.
i.e.

• A TCP request comes into the camera.
• The camera replies, accepting the connection request.
• The firewall blocks the ACK from going back to the computer making the request.

An ICMP packet is not the same as a TCP or UDP packet, so the firewall rule affecting TCPv4 will not affect it.
Search for "ICMP packet wiki"
(Because Reolink does not allow us to include URLs in messages.)

@tchubaba VLANs are pretty technical. Could it be that another rule is required to allow traffic FROM the cam VLAN TO the main VLAN?
In addition to testing with ICMP (ping), if these are RLC cameras, they also have a web server on both port 80 (http) and 443 (https). Might be worth checking if those respond to a connection from the main VLAN.