Posts made by burkm_172321696190677

@vodkan_410792752525441

A POE power supply can be connected in between the camera and the switch in front of it, if the switch itself directly in front of the camera does not contain this feature already. But have an eye on the needed power, which has to be provided by the POE power supply of this channel. But POE features of the switch *before* this can't be used, because only directly following items can be powered by a switch. The POE feature itself is not touched / connected in any way to the Mesh features of Your system...
I myself use a rather complex Mesh system and POE feature are provided by POE power supplies directly in front of the cameras (in between switches and cameras).

@mamymam2013_465350299701478 My latest Windows client (Windows 11 Pro) adjusts himself to the highest possible resolution of the monitor and keeps that stored. You might have to disable stopping cookies for Reolink...

Hi,

I checked with the model name RLC-823A for a new firmware version (as stated) but your firmware page does no longer recognize the Reolink RLC-823A model as a valid Reolink camera. Any idea, what is going on ???

@reolink-fiona
Using current Windows 11 Pro (22H2) OS setup on my system. Client versions 8.10.3 and 8.10.4 seem to work without any visible problems.

@joseph_1979
You are missing the situation, where other clients have to be connected to the same switch too (constraints), which might have a higher transfer rate...

Looks somewhat "pixelated" to me too...

@reolink-fiona (RLC-823A) I seem to face the same problem: although the return-timer ist set for about 60s, the camera returns to its default position after about 10s, when nothing is happing, which would trigger the tracking feature.

Kind regards - burkm

@reolink-fiona
I've got two RLC-823A cameras. but can't find those features: "Tracking limit" and Tracking Schedule" in the new beta firmware ?
Where are they located ???

Hi,

I installed the Beta firmware for the RLC-823A but forgot the "Reset configuration" switch to set as mentioned.
How can I get this activated as an afterthought ?

Note: The camera does not autotrack anymore....

@reolink-fiona
Hi Fiona,
Its day-time now. I will have to wait for night-time. But what should have changed ? I have accessed the camera through its web (IP) interface directly and a new firmware doesn't seem to be available, which could have changed this behavior ?

I just discovered another "bug" in the current firmware for the RLC-823A: I changed the option for "Black & White" from "Auto" to Manual" in the menu interface. This change ( to 119) has worked as expected, because of a visible outdoor-lamp the auto-exposure feature had darkend the image to much. But as soon, as a person activated the spotlight during night-time, walking i.e. to the letter box, and the IR-LEDs had been reactivated again after some time, the exposure changed the image. To my surprise, the picture again looked quite dark, as if my prior "Manual" correction (brightness) was no longer active. I checked the cameras setup (browser) and discovered that the exposure compensation Black & White" had been (re-)set to "Auto" again. This seems to happen right after the spotlight had been switched off, ignoring my prior changes and setup to "Manual" mode. This unwanted switch from "Manual" to "Auto" mode seems to be the default action in this situation.

@reolink-fiona

Hi fiona,
I am curious not about the low sensitivity range you describe but the behavior at the preset sensitivity and else. This image does not match what I get, when I manually change to the same (?) setting as default. Is that a "bug" ?

Refering to "Basic setting" and "Image" (not "Encoding") It will show only unscaled sliders there without any numbers to eventually match if set manually differently in between. "Default" behaves differently as in "Encoding" because it saves the current settings as "Default" and not setting the values back to factory defaulr.

Another "problem" is, that in the "Preview" menu "Basic Settings" no numbers (scaling) are given for the image settings. If you change anything manually there, there is no way in knowing how to return to the default (or previous) settings, because only some (unscaled) sliders are presented for adjusting those values. Pressing the "Default" button saves only those settings, whatever they are currently, but does not provide any "reference" for being able to go back to factory defaults.

@faasio82_480971996033257
The same happens to me: instead of relatively short runs of recorded shots I now got some, which are shown as running much longer (for *hours*) although nothing seems to happen in between, which would cause this.
I looked through my setup and didn't find anything, which would extend a recording the way this happens now. The only difference is, that an 128 GB high speed SD is in use now.

@reolink-fiona
Hi,

if you open the "Sensitivity" setup a "standard" image is always been shown. If I adjust this manually back and forth to the same value as set by the factory (default), the image suddenly changes considerably in accordance to the sensisitivity value. The same happens, if you change the sensitivity manually to something else, the shown image changes its size and appearence by quite a margin !

@burkm_172321696190677

I tested the new firmware for the "new" RLC-823A a lot - yesterday and today - during day- and night-time hours, especially the auto-tracking feature "Person". The results are rather "sobering". Only the predetermined (factory default) settings for "object size" lead to a working auto-tracking (without saving them).

I tested numerous different settings for the corresponding object size, even the settings: maximize "maximum" and minimize "minimum" object size, which always, if "normal" functioning, should reestablish auto-tracking, but none of them seemed to work after I saved them, which, as a consequence, disabled auto-tracking completely for the tested auto-tracking type "Person", both for day- and night-time action. The factory default settings for "object size" seem to be shown just as "dummies", because the displayed rectangles, when opening the corresponding window, show "maximum = minimum", saving your own settings then display, after reopening the corresponding menu-window, disjunct rectangles for "minimum" and "maximum" object size, none of them seem to be working as expected, because auto-tracking no longer was working at all.

Note: Reenabling the auto-tracking feature was only possible by resetting the camera to factory default settings using the existing hardware button on the supplied cable interface.
Thus "auto-tracking", as described, cannot be setup as expected and was a real disappointment.
Another "bug": The sensitivity image displayed is always the same and does not correspond to the "real" image after saving it, which only then changes in size corresponding to the set "sensitivity value" when the sensitivity has been changed manually...

My resume: Never (!) try to change and save "object size" for your object of interest at least with the current fimware version !

I rechecked my AI detection parameters on my RLC-823A camera having the latest firmware. I use the latest Reolink PC client and tested with the one before that too and the browser interface.
First thing i obeserved, that the resolution of the display is not scaled to the resolution of my display: 2560 x 1440. "Clear" will never work but it always switches either to a much lower resolution of "Balanced" or even "Fluent". Within the client only "fluent" and "clear" is offered as a selection / choice, but only "fluent" can be selected then. Strange.

As soon as I change the object size on the "Person" object size screen two things happen: When I save the changed parameters both sizes (minimum, maximum) are located within each other, then I close the window. After entering that object size screen again, both fields are disjunct, the yellow "minimum size" rectangle is always on the left side, the "maximum size" rectangle is always on the right side. This differs from the original display as presented first time, where both are within each other and always the same size (why?). Therafter the detection of persons movement will no longer work and the same holds true for the "auto-tracking" feature. Even if I setup minimum and maximum for same size and as close as possible to the original (factory setup) sizes, nothing will happen: no auto-tracking (and spotlight) anymore.
What makes me wonder although, that all factory size setups show the same size for minimum and maximum rectangles. What for ???

The logic behind those AI setup parameters is not clear to me...

Hi,

First thing I noticed, that the camera RLC-823A no longer has a HTTPS certificate, which is quite unusual, because most browsers signal this as an "error" (HTTP and HTTPS ports are both enabled, but no valid HTTPS certificate had been provided in the corresponding menu fields of the camera's firmware).

A rather "fatal" bug of the "new" camera firmware seems to be, that, if the camera is mounted alongside i.e. the long end of a garage or house wall, the auto-tracking feature at night follows the intruder up to the opposite corner, but the activated spotlight will then "highlight" the (white) wall near the camera so much (closer to the camera even more), that the automatic exposure compensation algorithm of the camera will, as a consequence, darken the surroundings completely, so that everything including the intruder will no longer be detected anymore for several seconds and the auto-tracking mechanism as a result focuses no longer onto the intruder but the nearby wall. When I first realized this, I had my wife walking in front of the camera at night time to the opposite garage corner to test it, and that was, what happened as soon as the spotlight turned on.
The surroundings of the camera were darkened to almost ver dark grey or black because of this "phenomenon" and my wife was no longer visible in the resulting (almost complete) "darkness" visible on the monitor's screen, because the camera focused on the (white) wall and auto-tracking moved the camera as a result in the wrong direction. It took several seconds, until the background lighted up again rather slowly, but my wife had moved away from the corner in the meantime whilst the spotlight (and camera) was still pointing at the corner because of this. My wife was therefore no longer visible on the camera's image, because she had moved outside the viewing angle (wide angle) of the camera following the usual path through the garden. This - naturally - happened only during nighttime, because the spotlight is not been activated during daytime hours. That specific situation must have been missed by the deverloper(s) testing the auto-tracking behavior of the camera...

Another thing, which was quite frustrating, that after some rather minor changes to the detection parameters, the camera would no longer auto-track and restarted working auto-tracking only after resetting it to factory defaults. Because I had continously problems with auto-tracking I cleared the correspsonding "Object size" images, but after that auto-tracking had seized working and I wasn't able to establish something functional there. The actual reasons for this could not be found by the Reolink customer service, because I wasn't able to grant access to the camera from the internet.
Note: All discoveries of mine were made with the latest Beta-Firmware (dated January 7th 2022) and - probably - are still present in the current firmware release...