u/Jos_Chir

What is your HW version?

I have two Argus PT Ultra and are on the same fw. Where they are located I rarely get a trigger but whenever we pass they are triggered.

Use the Windows client and after clicking on the Trackflex go to playback. While in playback click on the highlighted symbol shown below. Troppo facile......

https://preview.redd.it/qfvpp004tlch1.png?width=270&format=png&auto=webp&s=266b659e1d9beffa855f9e0b5c9cf51ec092860c

Try to rotate it a bit more to the left and mask your neighbours.

But how many times we have to report this to get fixed. What they are waiting for this to be fixed. Maybe the programmer left the company? Not on their priority list.

And who does the testing? Maybe the programmer himself. Even the explanation text has been changed to low contrast and you need to get closer to the screen to see it.

Go to their download center and check the newest FW for your hardware type. My HHP is running v3.3.0.466_26040850. Battery doorbell running v3.0.0.5298_26040225.

Nice camera. I still have the Argus 2 😄 which I bought 8 years ago and still in operation. Batteries still good.

I put back the Trackmix and will try to find a location where to install it. Poor VFOV.

I suggest you to make such a request to support.

Keep it up...you are doing great. However, I suggest you to put more resources on software development and testing. And we never stop providing brilliant ideas to implement....we wish to to see Reolink expedite the implementations.

Would you be able to capture a wireshark trace or get the logs at the ftp server side? Are you using FTP or FTPS?

Thanks for sharing.

I would switch off the cam IR Leds if the external one illuminates all the area.

I have one at the backyard and is linked to one of the DUO 2 cams. Never had any issue. Would recommend it.

No. Stream flows between the camera and the PC running the Reolink client. Capture a wireshark trace and you will see it. On 8.8.5 this was working fine.

After getting the A records for the p2p servers, the client requests the server for the private and public IP of each camera using the UID as a pointer to the profile of each camera. Then the PC client first uses the private IPs and if no reply it will use the public IPs....and then establishing communication with the camera server on port 9000....etc

Now place the RLC16 under the same condition and give us feedback in 9 years time :). I have equipment produced 30 years ago and still working as if new. And the new replacement costing millions of Euros.......uh lost count how many boards each week we forward to the supplier for repair.

Unfortunately this is the issue with battery powered cameras. To save battery life, it's only the PIR circuit which is constantly operating and the camera operation state is in sleep or cold mode. Once the PIR is triggered then it wakes up and start recording. So if the object moves quickly out of the FOV then it won't be included in the recorded clip. This can only be avoided if you have DC or POE powered cameras which are constantly recording and in the event of a trigger you will also have say 15s recording before the camera detected the object.

Strange but yes it seems so. RTMP doesn't use either of the 80/443 ports.

A possible solution is Argus 3 Pro having a 256G microSD, a solar panel and a cloud subscription.

Which model?

Switch off/on power. It could be that the WIFI reception is weak at the camera location. As a test, try to change to 2.4G band which has a longer range (longer wavelength).

It happens in all the 64bit 8.10.x versions. Different framework :).

That's not the point either. If my engineers got an idea from their subordinates they won't tell them to come to my office but they rather evaluate and implement. They leave me relaxed lol.....

Most customers come here as they think they can find a solution and is the right place to suggest what they wish to have. Some don't even know the support contact details. So having someone who can go through and forward the suggestions to the team will definintely help.