Posts made by joseph_1979

@antonio089_626720538640449 if you have no electricity then your option is to have 4G cameras charged through a solar panel as suggested by Steve. And ensure that you have local recording (on SD) as well as in the cloud just in case the cameras are stolen. There is the GO PT plus and Duo 2 LTE.

Have a look at https://m.reolink.com/product/reolink-go-pt-plus/?gclid=EAIaIQobChMI9IrI8YnQgAMVhdzVCh32FQTWEAAYASAAEgIYdPD_BwE

Ensure you have a strong 4G coverage as HSPA bandwidth (3G data) is not enough.

@meanbigbrother_172968072114399 So your new PC is on Windows 10. Save the DirectX file in a folder and unzip and execute dxsetup.exe. It will copy the ddls to system32 and SysWOW64. These won't harm your system at all and you still have the DirectX11 installed. This is due to the fact that during development DirectX9 was used. I am running v8.12.1 without issue so far.

As for older versions, we have requested Reolink to include older clients and firmware in their Download Center.

@marian-siczek_715086104985814 Next time try to restore it. Which model?

@dioclervaux_692411932307595 There is a free plan for 1 camera which has to be renewed occasionally. But there are other methods to store the videos such as NVR and FTP servers.

@user_724091070546163_724091070546163 Since you are on the same private network then disable the TLS and use plain SMTP (No TLSv1.2). Install Wireshark on your server and trace the SMTP messages (filter on tcp.port == 1025). Check that the packets arrive at the SMTP server and it replies back. Which SMTP server have you installed?

Did you try to use gmail to ensure that the email works on the camera (which I have no doubt at all)? I have a number of WIFI models and email works on all without any error at all. One thing to note is that the video attached (if selected) is of low resolution due to the file size.

Normally I disable HTTP and use HTTPS which uses the self signed certificate.

@user_724016330887410_724016330887410 Just extract the file in a folder and execute the dxsetup.exe. Dll files shall be installed in C:\Windows\System32 (and C:\Windows\SysWOW64 on a 64-bit copy of Windows)

@veronica-falzone_691720783737520 We have requested the event history especially for cases where the object has been detected by various cameras. I have seen this on another brand and its a must have.

@Lorenz Any date please?

@pierre-gielen_288801745879289 copy the cab files to a folder and run the dxsetup.exe. it will install the dll of DirectX files at C:\Windows\System32 (and C:\Windows\SysWOW64 on a 64-bit copy of Windows)

@crimp-on_62210811129 These are the cab files.

@colin-grimshaw_430254205366491 White will be better and perhaps widening the time bar a bit.

@laphunhon_689657095459000 I suggest you to send these requests to Reolink support. They prioritise features in accordance to the number of requests received.

We have already proposed these features.

Rich notification is awesome with action. This, of course, requires further processing at their application servers and may require a subscription. This is being done for WIFI doorbell.

I recall old Android clients which when clicking on the notification , it used to take you to the recorded video but I cannot understand why this has been removed. We also requested that when a user select the playback, the client should point to the last clip.

Event logging is required for cases where the object has been detected by various cameras and you want to go through in accordance to the sequence of events.

Motion tagging is under development and we hope to see it soon. Most probably this will be on new cameras. Maybe Lorenz can provide further details on when this shall be available

@vladosk_604441546297359 So here is a description.

IPC_523SD8 is the hw version
1643 is the fw generation number
23041100 Is the date (11/04/2023) when the fw was compiled.

But Reolink don't include this camera in the download center due to the fact that there are various variants of this model. So I suggest you to email support quoting your full hw version.

@mart-tob_723653357826278 You're welcome. The server port can be changed and you can assign different server port for each camera. Then use port forwarding in the BB router to route it to the respective camera. In this way you shall get the clear mode.

I recall testing this quite some time ago but I forgot whether I tried it locally. Maybe you can test it out.

@brandoncarrolleet_691346059215349 I suggest you to take it up with support by attaching the recorded video. But as you stated it's not the fps but the shutter speed and exposure which are needed for clear pic at night time. I would also consider to have independent IR illuminators so as to avoid reflection and have more IR light.

@mart-tob_723653357826278 This is how it is designed to work when connected from an external network. Assuming that you have done the installation and you run the Android/Win client. When you run the client it will send DNS queries to get the IPs of the P2P servers which are AWS/Azure. Client receives the DNS response for the 16 P2P servers ( not all used...some point to loop back IP...future expansion). Then the client sends a request to each P2P server with the UID of each camera. The P2P servers send the local IP of each camera together with a public IP on the P2P server. When the client receives these responses it will first start to establish communication using the private IPs and port 9000. If the client is on the same network as the camera then the camera will respond and communication will be established (TCP). Here the stored stream mode will be used as bandwidth is not an issue. Note that at regular intervals the camera sends a heart beat message to the P2P servers and from this message the P2P servers get the private IP of the camera and its assigned public IP/port on your BB router.

If, however, the client is on an external network, it will not receive any replies when using the private IPs and so it will use the public IPs. So the client will establish a session with the P2P Relay servers and the P2P server establishes a session with the camera (using the BB router public IP/port mentioned above). So the flow of media and messages is through the P2P servers and UDP is used as the transport prot. The P2P Relay servers don't have infinite bandwidth and this bandwidth is not free and so Reolink has to pay for it. So in order not to create congestion on the allocated bandwidth they opted to have the stream mode to default to FLUENT irrespective of what you set it before (my personal thinking). So here is a trade off.......

Note that media and messages are encrypted at both ends. The flow can easily be seen by capturing traces on the egress of the BB router using Wireshark.

@crimp-on_62210811129 This is the redistribution package for DirectX. Just download to a folder, unzip and execute the dxsetup.exe. Yes some dlls dates back to 2010.

@crimp-on_62210811129 These are the DirectX9 libraries. Normally they are installed under system where there are the DirectX11 libraries.

@mart-tob_723653357826278 I was expecting that answer but wanted a confirmation. Yes, DirectX9 is needed with the recent clients. Thanks.

@mart-tob_723653357826278 Do you recall the missing files? Please check that all features function as expected. So far so good on my notebook.

@jm_fort_525559425302685 Excellent. Enjoy.