Posts made by Christian

Yes, unfortunately this is a problem in the whole E1 series which have the tracking function.

I had the e1-Outdor and also the E1-zoom V1 as well as the V2 models with Lan connection and 2 different model series.
I did long-term tests here to find out the cause. Unfortunately, I could not find any clues to reproduce it cleanly.
The fact is that when there is a lot of tracking traffic, the camera turns completely to the left once a day to the stop.

The only thing that helps here is manual calibration, which then only lasts until the next error occurs.

The camera itself is good, but only as long as you don't use the tracking function. Actually very unfortunate.

But since the error is already known from the previous models, I wonder why nothing was done here in the sensor control. Unfortunately, I don't know the mechanical structure (yet), but I'm about to take the part apart and see where the problem lies. I have a few assumptions but I won't know until I disassemble the part.

@jschulz_680169125388712

Are you sure you know how such certificates work at all?

How should the reolink deposit a certificate tailored to you?
You call up the camera via an IP and a corresponding certificate must exist for this.
Even if you use your own FQDN URL, there must be a certificate for it. Reolink cannot do that.

The certificate that is stored there is only intended for an HTTPS connection to be established at all.
The browser reports that it cannot be valid, because it is trying to check it with the CA it knows, but this cannot work.
All of this is completely normal behavior.

And as I said above, please use the WebGUI to see if you don't already find the function to upload your own certificate, as in the picture above.

@crimp-on_62210811129
I dont have a RLC-822.
I am only have a RLC-823WA, TrackMix and a E1-Zoom V2 and all of them has the ability to
upload an own certificate via WebGUI (only there) not the Client.

It looks like this here.

You can now upload certificates yourself for the newer models with the latest firmware.
However, that presupposes that you know how to do it.
Even if Reolink installs a valid certificate on its own, it is only temporary.

@joseph_1979

Hello Joseph,
Thanks for reply.

Yes, DirectX V9 is installed on Win 10 Pro.
It was one of the first things since i have Win10 because i have some very old Apps who still
use Direct X V9.

I have installed this from Microsoft:
Offline Version: directx_Jun2010_redist.exe

I already chekced the Registry:
HKey Local Machine\SOFTWARE\Microsoft\DirectX
Version=4.09.00.0904

So it can't be with the DirectX V9

Regards Chris

PS: I solved the Issue but it has another Bug.

You must delete all Cam-Entries and set it again when you Update from V8.8.5
Than you have again all Buttons.
But when you close the App an start it again than all Buttons still gone again.

In V8.11 now the Microfone and PTZ-Controll has gone.

I am using 3 Cams. Trackmix Wifi, E1-Zoom and RLC-523WA.


Yep and already now rolling back to the good old 8.8.5

every time the same

I have also updated and now i missed some funktions like PTZ, Microphone, ...
What has happend here?

I am back now on 8.8.5 an everything is ok.

@reolink-fiona
120W provided power is impressive.
In the wild you will find only 60W for small switches.

But why you provide only 100Mbit on this ports?
1GB/s ist state of the art.
I know that is sufficent for the cams but so you are a little bit restricted.

Regards Chris

Hello everyone,
i am a new owner of a RLC-523WA and impressed of this product and their features.

Since i have chekced some features i have a problem with the RTSP Stream. I monitoring the live stream via VLC (3.0.18) on
Windows 10 and put in the follwing URL:
rtsp://<ip>:554/h264Preview_01_sub

I only noticed it now since i saw an old picture und see that the time is not count up. When i restart the stream i see the new picture but the time is freezed and the picture also.

When i use this URL evrything is fine: rtsp://<ip>:554/h264Preview_01_main

When i use the browser view or the client everything works.

The actually FW ist: v3.1.0.1643_22122310_v1.0.0.30

I don't know which of them causes the Problem.

Any hints?

Regards Chris