Posts made by joseph_1979

@legoguy_24916305373 I fully agree with your analysis and this is what I concluded. Note that I am not an employee of Reolink but a customer like you and assisting members of the community based on my engineering/software skills. Would you be able to collect event logs from Windows or any logs which might be of interest for Reolink to investigate and sort out the issue with their client? Perhaps if you record a video it will help them. Then email Reolink support.

@country1706_654925491045469 They are performing the final tests and once successfully completed it will be added to the list in the download center. But if you wish to check when it shall be available then email the support.

@user_686288253579422_686288253579422 Depends on your budget. Have a look at the following WIFI DC powered cameras at Reolink website. It is important that you select a camera with person/vehicle and possible pet detection otherwise you will have a number of false triggers. Also insert the cables in a weatherproof junction box (>=IP65) to avoid problems caused by moisture.

1. TrackMix WIFI
2. RLC523WA
3. RLC511WA
4. RLC510WA
5. DUO 2 WIFI - Field of View nearly 180 degrees.
6. And if you want to wait ... there will be the E1 outdoor Pro.

To check which protocols are supported by the camera click on specs and go to protocol and you should see something like this.

Protocols & Standards

HTTPS, SSL, TCP/IP, UDP, HTTP, IPv4, UPnP, RTSP, RTMP, SMTP, NTP, DHCP, DNS, DDNS, FTP, P2P

So ONVIF Profile S/T is the standard and RTSP is the protocol.

@user_686576360607949_686576360607949 I just finished a long meeting with my engineers and just executed the command and hereunder find the outcome (onlystatus=1 and if you want each detection then onlystatus=0...you have the timestamp and filename). Yes, with the token it should work too.

@user_686288253579422_686288253579422 None.

@user_686576360607949_686576360607949 Enable HTTPS from Network menu and run the following curl command. Just replace the CameraIP with the private IP of the camera.

curl -s -k -X POST -H "Content-Type : application/json" -d "[{"cmd": "Search", "action":0, "param": { "Search": { "channel": 0, "onlyStatus": 1, "streamType": "main", "StartTime": { "year": 2023, "mon": 04, "day": 21, "hour": 12, "min": 26, "sec": 1},"EndTime": { "year": 2023,"mon": 04, "day": 21, "hour": 21, "min": 34, "sec": 1}}}}]" "https://CameraIP/cgi-bin/api.cgi?user=#username#&password=#password#"

@dgordon42_415060065599711 I did raise the SIP calling as an important feature together with the capability of using the existing chimes and being fully ONVIF Profile T compliant. Otherwise it is superb.

SIP calling entails a SIP stack to be installed on the camera and the camera has to register with a SIP server (provided by either Reolink or an ISP/Operator). When the button is pressed, the camera sends an INVITE (with SDP having AVP 0, 8,9,18----voice codecs) with the configured called number to the SIP server and the SIP server will acknowledge with 100 Trying. The server will send the INVITE to the smartphone (which has to register with the SIP server too) and the smartphone starts to ring....180 is sent back. Then we have the answer 200 OK with the SDP (from smartphone side -- initially voice codecs) and then the caller may opt to change to video in which case the smartphone sends a RE_INVITE with the SDP having the video codec (H.264, H.265,,)........... So to handle this for all the doorbells sold, Reolink would need quite a number of SIP servers and adding the VOIP feature on their client. Some competitors have already deployed this facility.....SIP is fun....esp troubleshooting.

And hopefully we will see more vivid colourful images with F1.0 advanced lenses. 

@ac130eng_604936342302775 If it is a lengthy video it is really frustrating. They need to improve the playback. I have seen the TAPO playback and would say one could easily navigate in the playback movie and would load faster too. Hope that we shall see improvements in this field.

@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.