Posts made by Crimp On_62210811129

@joseph_1979 Correct. The RLC-423 requires IEEE 802.3at (often marketed as POE+), which is different from the original IEEE 802.3af Power over Ethernet.

Both the Windows Client and the Android app have an option to set Download to Clear or Fluent. (If this stupid software allowed users to upload screen shots I would do so - sigh)

I have asked Reolink about access to the actual "full resolution" image (i.e. the RAW image) Reolink confirmed that there is no method for users to gain access to the actual full resolution image.
Rather, like many smartphone cameras, the camera hardware module that is included in Reolink cameras produces single images as JPEG compressions and video streams as H.264 or H.265 compressed streams. It would be wildly impractical to stream a full resolution picture.

@joseph_1979 Thank you. Sorry to vent about this horrid forum interface. It is just so annoying.

No. This additional feature on the RLC-1212A does not appear to be related to "Perimeter Protection and Smart Event Detection". This (Beta) feature draws a box around people, animals, and vehicles that are moving. Unfortunately, it chooses to draw boxes around vehicles that clear are NOT moving.

Not that the camera has been on this firmware release for a day, I will open some recordings and see what it does to people and animals.

Appreciate your help.

Also, inserting a screen capture into a post results in the word "undefined" rather than the actual image.

Just installed v3.1.0.5036 on an RLC-1212A, dated Sept 3, 2025. The new "beta" feature is to mark "moving" objects:

Alas, four vehicles which are clearly not moving have rectangles around them, but a vehicle which clearly moves across the picture does not.

This is SO SAD.

The app can access the NVR remotely (from networks other than the local network that the NVR is connected to), but cannot access from a network connected via Starlink?

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.

Perhaps a silly question. How much light does it take for this camera to produce a decent color picture? The specs seem to indicate that the spotlight will produce a maximum of 400 lumens at full brightness. The product description gives the impression that the light level can be controlled.

Perhaps a couple of low wattage outdoor night lights would produce enough to enable the camera to function without using the spotlight at all. Maybe some low voltage landscape lighting?

Some of the RLC cameras have the ability to set motion sensitivity for different periods of each day. Disappointing that the battery powered (PIR) cameras appear not to have that feature.

Is there an SD card in the camera? I do not have the E1 Pro, but do have an E1 Outdoor. Both the Reolink 'app' and the Reolink Windows Client allow me to play back recordings from the SD card.that I placed in the camera when installing it. In addition, I use the FTP feature to send recordings to an FTP server (in case "something happens" to the actual camera.)

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.