Posts made by joseph_1979

@user_686288253579422_686288253579422 Battery-operated cameras can only communicate with Reolink clients and Reolink P2P/Application servers. In addition it can store the video to Reolink cloud against a subscription.

Cameras supporting CGI, RTSP(Protocol) and ONVIF(Standard) can be found at https://support.reolink.com/hc/en-us/articles/900000617826-Which-Reolink-Products-Support-CGI-RTSP-ONVIF/

I suggest you to restore the camera (from Client go to Advance and click on Restore --- WIFI settings untouched) and start configuring again.....should not take more than a few minutes.

@saleinspahr_532352931750057 Which camera model? Did you set up the push message notification? Have a look here... https://support.reolink.com/hc/en-us/articles/360004189214/?_gl=1*1j8kro5*_ga*MzI3NTUwNzk5LjE2ODE0NTg4NjI.*_ga_Q2NV1EV2K8*MTY4MjMyMDMxMi4xMC4xLjE2ODIzMjIyMzYuMC4wLjA.

@fredericneveux_352399457841348 I would say a year or so difference. The RLC-520A has the ability to detect person and vehicle.

Check this link https://support.reolink.com/hc/en-us/articles/900006251626-How-to-Install-the-Micro-SD-card-into-RLC-423/?gclid=CjwKCAjw0ZiiBhBKEiwA4PT9z0XMFlMRcIDyJbEpsMrvTFfBVE-cFbiJp7NSBA1XX5q6t_cCh1HGYxoC0QYQAvD_BwE

@user_686288253579422_686288253579422 To the best of my knowledge, none of the battery-operated Reolink cameras supports the ONVIF/RTSP and CGI.

As for the bolded parameters, these are the credentials to log on the camera and if the camera and device receiving the media is on the same private network then you should have the private IP assigned to the camera. Otherwise you need the public IP and the you need to do port forwarding on the router.

@corpex39_417116623257763 Good to hear that. Wish to hear your feedback once you installed it and had it ran for a few weeks.

@user_639929078194246_639929078194246 Which model? If this is POE just plug it in and the NVR will detect it. Normally when you buy a complete system then most probably the cameras have no UIDs.

@enrico-montefusco_322036714238195 It seems that the client is encountering an issue with the latest Intel Iris update. Can you roll back the Intel Iris driver to an old version and try again?

@westwind-pavel_602090576867688 I am a customer like you. But people tend to point to the camera as the main culprit. As I pointed out in my previous reply there are numerous entities along the path between the camera and the device running the client. I have a number of Reolink WIFI cams/doorbell/floodlight and never had any issue to communicate with the units from both the Android and Windows client (have good WIFI network at home with 1G/300M and good 4G/5G coverage).

Nothing is perfect and of course there is a lot to be done at both camera and application side. It is rather difficult to implement all ideas put forward. Some are really brilliant which being an engineer didnt think of. Usually brilliant ideas come from the least expected. What I wish to see is more diagnostic tools and logs to assist in troubleshooting (especially if the camera is at a remote site). Throwing a number as an error is of no help unless this is well documented and available to customers.

I remember Warren answering a journalist.... it takes 20 years to build a reputation and 5 min to ruin it. If you think about that, you will do things differently.

@tekmaven-zs_242452477804726 With dual graphics there seems to be an issue. Would you be able to send the details of your system to Reolink support so that they will investigate why their client fails to run in dual graphics mode.

@user_685537082409112_685537082409112 Ensure you don't get the American version which use different frequency spectrum.

@user_685537082409112_685537082409112 Yes, you have the 1800 (B3). You have B40 too...but this is time division duplexing and used in China and Australia. In Europe we use B3 and B8.

@seb_526812765704330 I have informed them too. If I have the source code ( I program in C++) I will also add the schedule when it is triggered by motion or cameras. few lines of coding..... It doesn't make sense to switch on the floodlight at daylight.

@seb_526812765704330 I did tested it out and confirm your findings. In my opinion it should not switch on during daylight. Reolink informed.

@kip_46655195393 How are the sites connected to the host? And what camera models you have at each site? What is the connection (1G fibre patch) between the router and the host server? So if we assume a 4M pixel camera (Requires 8Mbps bandwidth if using H.264) then you will need at least 3G bandwidth between the router and the host. If you are recording on 24x7 at high resolution then you definitely need a 10G IP backbone. I would use two routers and would take into consideration the server redundancy. Raid 10 is a good choice for this scenario.

The freezing issue. Did you manage to monitor the processes/resources during the instance the application freezes? Can you pinpoint which resource is being used mostly? As a test I would set all the cameras at the lowest resolution/fps and bitrate and even switch off the hardware acceleration first from the main menu of the Reolink client (here you shall see an incremental cpu load but should be OK). What PC are you using? I have VMware on HP G10 and have no issues of resources but for different applications. I use vsphere to monitor.

Another suggestion would be to run the cameras on client version 7? Just give it a try. This seems to use less resources and the code seems efficient. Just to test.

And another suggestion would be to use ONVIF and use a 3rd party client.

What was the reply from support?

@letandemetlavie_510638925045941 Go to their download center at https://m.reolink.com/download-center/ and get the firmware.

@seb_526812765704330 Would the floodlight switch on when you walk across its PIR during daylight? If yes then email Reolink support to send you a newer firmware of the floodlight and you should be able to adjust the ambient light when the floodlight should switch on.

@ianh_684667170234560 Follow this link https://support.reolink.com/hc/en-us/articles/360020644034-How-to-Add-Reolink-Cameras-to-Google-Home/#:~:text=Launch%20the%20Reolink%20App%20and,will%20be%20shown%20as%20Unbind.

@kweckstrom_652263608210296 H.264 and H.265 are both standards for video compression used in recording and distributing digital video. The main difference between H.264 and H.265 is how each processes information and the resulting video file size and bandwidth consumption used with each standard.
H.264 processes frames of video using macroblocks, while H.265 processes information using coding tree units (CTUs). CTUs process information more efficiently, which results in a smaller file size and less bandwidth used for your streamed video. So most manufacturers opt to use H.265 for high definition which requires less bandwidth and storage space. So if the definition is higher than 1440p they opt to use the H.265. However, they can still use the H.264. There is no adamant rule.

The higher the resolution, the fps and max bit rate the more clarity the picture will be and subsequently better digital zooming.

Moreover as already stated if Audio works with VLC then it's not a Reolink issue. But I cannot state eith certainly why it is not being decoded by ZM. There must be some bits ZM is not understanding.

BTW what was Reolink support reply? Try to contact them. Maybe someone else raised it up and have a solution. I am a customer.....

@bigblue007_631330884632579 The official one is the one provided by Reolink download center and so one has to adhere to the product owner site. Reolink will not be held responsible if one applies the firmware from third party sites and damage the unit. For instance they have pulled out the last two doorbell firmware so as not to cause issues until a more robust firmware is available.

Personally I won't ever apply a firmware of a product from third party site.