Posts made by pjsmit_155286146154639

@seb_526812765704330 Update: To add to the confusion ..... my new RLC-811A from Amazon FW version is: v3.1.0.2948_23111411 (2023, Nov 14th) ..... (Hardware version IPC_560B158P).

@user_784224808100067_784224808100067 I have similar issues with my RLC-811a. There seem to be a number of issues with the zone detection settings. For example they move / reset without touching the app / old zones stay, although you deleted them / when zooming in/out the detection zones move / detection zone set in app does not correspond with actual detections .....
Contact support and maybe one day they fix this ...... Search for "zone" and you will see that this issue is going on for 2+ years ...........

@joseph_1979 I emailed support and they have now send me a firmware I already received from them a month ago (okt 2023 version) that was not resolving the zone detection issues I have .....
IPC_560B158MP.2784_23101654.RLC-811A.IMX415.8MP.AF.REOLINK.pak

Reolinks firmware updates are really confusing ..... on the website it showed (jan 2024) the latest fw is a 2022 date. Then when contacting support for the first time I get a okt 2023 update and when contacting them a month later I get a juli 2023 update. Now on their website it says there is a feb 2024 update and they send me the okt 2023 update again ....
But the worst of it is that the zone issues are still not solved......

It looks like Reolink has brought out an official new firmware for the 811A (and 822A) a few days ago. (see images below from the download center).
In the installation guideliens it says to check for the correct hardware version. The only version available on the website is for the IPC_523128M8MP. My 811A Hardware version is: IPC_560B159MP. What to do?

PS. The 822A also seems to have the same hardware version on their website .....

Why does the Reolink app only have a "delayed detection" option for items it recognises as person/vehicle/animal?
I want to be notified of any movement around my frontdoor, but only when this is more than 5 seconds, not people/cars passing.
Now their shadows trigger all the time.

Please add the option to have delayed detection for all movement!
PS. People do not get recognised because of the overhead angle of the camera, but that would technically be more difficult to solve......

@cynthia_124785627824270 My camera has similar motion detection issues. So 3 years later the issue is still not solved????
When I contact Resolink support about this issue, they say they are still working on it and I have to be patient ..................

@joseph_1979 I also have a RLC511WA and it does not have these issues ....

@user_775801804398831_775801804398831 It problably is an issue that is not specifically related to your camera model .....
I have the same issues with a RLC-811A. The RMA Reolink support team says the developpers are working on it ...... but when I look in the forum the issue seems to be there for years ........

@erda_752207801675934 I have the same issue and after a few days of uploading videos/images to reolink and resetting camera, new firmware Reolink replies:
"This issue has been collected and reported to our product team.
Our engineers are working hard to find a fix and make an improvement in this regard.
However, this may take time. Your understanding and patience in this regard will be much appreciated."

This has been such a waste of time.

I now started to do my own research as Reolink seem to be more busy with other stuff .....

Luckely I have a Foscam as backup and their software works fine, although their camera lenses are less good .....

@user_623346741346376_623346741346376 I have the same issue with an 811A. Contacted Reolink support (feb 2024) and after going backwrds and forwards for many e-mails the answer is:
"This issue has been collected and reported to our product team.
Our engineers are working hard to find a fix and make an improvement in this regard.
However, this may take time. Your understanding and patience in this regard will be much appreciated."

@joseph_1979 Thank you for your ideas!
I have emailed support before and yes, they send me a newer firmware version (IPC_560B158MP.2784_23101654.RLC-811A.IMX415.8MP.AF.REOLINK.pak) than is offered on the website. This did not resolve the issue.
I have deleted all detection areas, zoomed in and out, did a hard factory reset, but still somehow the new detection zones are 1-2 meter off ..... and somewhat not predictable.
AI with delay would be a good solution, but in my case the camera is filming from the top and does not recognise humans .... so the delay cannot be used. So I get false alarms ALL the time.
I hope you have more ideas after your testing....

PS. I also have a 511 and no issues with that one.

When I set/change a (non) detection zone the new settings are not working accurately.
I have done some experimenting and it looks like the detection area is ofsett a few meters from the actual trigger area. Also it looks like some previous settings for areas are still saved ..... A reboot/factory reset does not change this issue.

What else can I try or is this a software issue by Reolink?

PS. I have my camera zoomed in 5x and when sooming out, the actual detection zone on the realink app changes ......
PS. As the camera is filming from above the door, it has difficulty recognising humans .... and as there is no possibility to delay other things passing, I either miss alarts or get to many .... so can I request the software engineers to create a delay detection option for all movement?

Camera/firmware details below:
RLC-811A

Windows 11, Reolink client: v8.14.2

95270005L27H12WO
build 23101654
IPC_560B158MP
v3.1.0.0
v3.1.0.2784_23101654
IPC_560B158MPS16AFOE1W011000000

Here is an update:I found that if you adjust the Detection Sensitivity on a camera, using the Windows Client, then the Motion Detection Zones get messed up..
I have the same issue. How do you solve this?

PS. I have installed the latest windows client version AND installed the latest firmware (had to get it via support as on the reolink website the latest version is much older .... (811a)).