Posts made by joseph_1979

@friedhofsblond_74434013315 Fist set the FTP on the HHP and then enable the FTP on the camera. Once camera is bound to the HHP you no longer have to add the IP of the FTP server.

So on the HHP it should look like this



If you do a test and check the logs on the FTP server you shall see (part of the FTP messages)



And from the camera side you shall have





And if one presses test from the camera side, we shall see the following messages on the ftp server.




As FTP server I am using the Cerberus but you can use FileZilla and others. Note that Reolink products don't support SFTP (requires SSH) but plain ftp and FTPS

@lafunamor You may forward your suggestions to the support.

@user_953742728401077_953742728401077 No. The stream is encrypted. All they can do is trying to access your camera and if you have a weak password then they will get through. So follow the password policy.

@kimchigun RTMP has lower latency and normally used for live streaming. But yes I still say that Reolink have to improve the RTSP protocol. Maybe this is attributed to resources which are operating at engineering level.

A software NVR. Uh this will be a workload on support due to different platforms. We have issues on a simple client let alone having a software based NVR.

@pdougan Through Playback.

@rocketdylon50_212394713747637 GO to Amazon and search for J-Tech-Digital-Extender-Ethernet-Supports

@friedhofsblond_74434013315 When you connect the cam to the Home Hub and ftp is enabled on both entities, then the file is uploaded from the camera to the HHP and from the HHP to the ftp server. In fact the ftp server configuration appears on the HHP. Ensure that the Argus 3 Pro is on fw v3.0.0.3951_24081932. If this is not what is installed on your Argus 3 Pro then email support to push you this fw.

@reolink-oskar Customers are now after a CX version with a higher optical zoom and more resolution on the Telephoto. And how about adding a third fixed lens on the top which shall be aimed at the position to be constantly monitored while the other lenses do the tracking and patrolling.

@kev_57257967492 If we adhere to the compilation date then the 4289 is more recent. The date is read as follows YY(24)MM(12 Dec)DD(17). Yours has been compiled on 10th Dec 2024. Total confusion. Seems the rule is not followed correctly. Anyhow the most important is that your issue has been solved.

Hope they will update their download center too.

@user_953742728401077_953742728401077 if they have them then you can use them otherwise if it is a kit then most probably they don't have UID.

This is like the mac address. Cannot be added or changed.

@lio_773845245571269 Have a look at https://support.reolink.com/hc/en-us/articles/900004614403-How-to-Add-Reolink-Cameras-to-Reolink-NVR-New-UI/

@elijah-pokrop Maybe you hit a limit.

I assume your RLN12W WAN port is connected to a router. If this is the case I suggest you to run half of your cameras on your home WIFI and add them to the RLN12W. This means that the data flows from camera to router (WIFI) and from router to RLN12W (cable). Note that we cannot run all the cams in this way as we will hit the 100Mbps bandwidth of the eth port on the RLN12W. I cannot understand why in 2025 they still implement 100M eth port. It should be 1G. Same cost.

See if the lagging dissappears. If not then it is a resource issue on the RLN12W.

@tripp_949654993338538 Good points. We really need geofencing and face recognition.

@user_950867264204965_950867264204965 No need. Just ensure you have the same SSID and password. It shall connect automatically.

Ensure that from the location of the camera you have an upload speed of at least 12Mbps.

@kev_57257967492 Thanks a lot. You are amongst the very few who updates us when a solution is found. We are here to support others who may have been through the same issue. Note that 5 days ago there was an fw upgrade for E1 OD Pro. This was created to fix bugs and maybe yours is included too. Have a look at their Download Center.

Once again thanks for the update.

@user_944216066371752_944216066371752 If power is restored then the camera should connect to the WIFI network and should be reachable.

Is your router back in operation? Do you have any other device which you can connect to?

@user_828616743243981_828616743243981 I don't have this issue on v 8.18.12. How about uninstall and re-install client?

Note that if you run the client from an external network all the streams default to Fluent.

@reolink-oskar Well Done. Now we need to see more improvements and features on the clients side.

@user_944897190998152_944897190998152 Push notification continues to function as camera sends the alert message to the pushx.reolink.com irrespective of source IP.

In your case, it seems that the session between the cameras and the P2P relay servers (AWS) is somehow lost. Since this is common to all the cams then I suspect a router issue. Do the disconnections coincide with the TTL of the DHCP? You may assign one of the camera a static IP (outside the DHCP range) and check.

@user_616377605799979_616377605799979 Yesterday I have removed the RLC-811WA to do some plastering and checked how the mounting has been made. I realized that when you turn the lock with the Allen key, it presses against the ball end and subsequently keeps it from moving. But the trick is that you first secure the plate against the wall and then turn the lock, preferably with a better Allen key. Now it is quite secured and one can hang a bucket (empty :).