Posts made by joseph_1979

@user_816950336405681_816950336405681 email support on support(@)reolink(dot)com

@markemily_759439911620779 re:Argus 3 Ultra you can save the video on SD or cloud (there is a limit on length). Note that you cannot have continuous recording on battery operated cams.

On the doorbell, you can save it to SD, cloud, ftp or streaming onvif/rtsp to an HA/BI, etc.

@wannabe-farms_809012976083135 Have a look at the link https://support.reolink.com/hc/en-us/articles/9480345752473-Getting-Started-with-Argus-Eco/

@user_814616436797688_814616436797688 Email support on support(@)reolink(dot)com

@connellb_322777373483187 Just copy folder AppData\Roaming\reolink and you won't lose anything.

@gaven_507857660539110 Better so that they have more feedback from us.

@ml_812798949916887 Personally I never used the cloud services. I store the videos on SD and ftp them to an ftp server in another site. According to doc, the fluent should be at max 48s or filesize 7M whichever comes first.

@domkal_775112654221518 In that thread you shall find my comments too.

@domkal_775112654221518 You shall see that calling screen if and only if at the moment the visitor button is pressed, you are on your Android client. At any other instant you have a message notification. This calling feature is based on push message notification.

@domkal_775112654221518

The calling feature announced by Reolink is based on push message notification and this is not what the customers are looking for. We receive a lot of push messages on our smartphone and definitely we will miss them. It has to be as implemented by their competitors and should be based on SIP(S)+SRTP or XMPP + SRTP (like whatsapp). This implies that both the camera and the client has to register with a sip server (REGISTER - 200OK following a challenge 401) and once the button is pressed the camera sends INVITE with SDP codec Audio to the SIP sever which in turn sends an INVITE to the smartphone........which in turn shall send 180 (RINGING)...........and when the client (smartphone) answers a 200OK is sent back..........and two way conversation is established.........and at any time the client can change to video......so an UPDATE or REINVITE is sent back with possible video codecs........  200OK is received and we have video. And then closing the session BYE...........200K........ SIP is fun and and troubleshooting is absolutely exciting........... IMS/VOLTE....

In a nutshell we are waiting for their implementation. Hopefully it shall be based on VOIP.

@user_818925137264881_818925137264881 Check out this link https://support.reolink.com/hc/en-us/articles/14608263489945-How-to-Set-up-Black-White-and-Color-Switching-Threshold-via-Reolink-App/

@tomsreolink Good to hear it.

@user_818905622692080_818905622692080 I don't think that the developers check our requests. I suggest you to submit your requests to support on support(@)reolink(dot)com

@user_818606983745773_818606983745773 Reolink NVR is solely for Reolink poe and dc powered cameras. It won't manage the Reolink battery operated cam.

@gaven_507857660539110 I suggest you to submit your request to support(@)reolink(dot)com

@user_813402656334073_813402656334073 These URLs are incorrect and you need to specify the encoder. In case of fluent, the encoder is h264.

@ml_812798949916887 That's the norm. Check this link https://support.reolink.com/hc/en-us/articles/900000641926-A-Brief-Introduction-to-Reolink-Cloud/

@skeptouchous I fully agree. I didn't get any feedback from their support. They just told me request passed to engineers.

@tomsreolink First run the 8.8.5 and get the UID of NVR (and that of cameras if and only if they are not directly connected to NVR ports). Uninstall both the 32 and 64 bit clients so it will also clear the relative directories under application data. Then install the v8.15.6 and add the NVR (and cameras if they are not directly connected to NVR).

@user_813402656334073_813402656334073 Which URL are you using?

Should be in the format rtsp://admin:password@ip_cam:554//h265Preview_01_main