Posts made by joseph_1979

@nick_26792935116 Try to disable ssl on Synology. You shouldn't have a trailing '/' at the end of the pathname.

Can you use Filezilla/Coreftp client and try to transfer from your PC to Synology using the cam account?

Any logs on Synology?

Did you upgrade the fw of the doorbell?

@artech I have no idea. But this should have been rigorously tested before launching it to the customers. I used to spend over a year testing a Mobile Switching Centre before putting it into service. Similarly for IMS networks. I still cannot understand how their method is going to work. I know all the technicalities around the method employed by Arlo, Eufy and Wyze.

@nick_26792935116 I presume you have provided all the rights to the account. It seems it starts to write but is restricted. Would you be able to install wireshark and capture a trace? Use FTP and disable ssl on both cam and synology.

@user_746623229407444_746623229407444 Normally they implement the feature on the camera and then they extend it on the NVR. You can reach their support on support @ reolink . com (delete spaces). I am a customer too and assist members wherever possible.

@user_746623229407444_746623229407444 Yes, I know about this. It has to be used as a standalone.. that is connected through a switch.

@user_746623229407444_746623229407444 Applicable to both models as indicated in the description. Go to download center and see what has been added/improved.

But from the feedback provided by customers, the calling feature is not working. I didn't test it yet as I am not on site.

Go under push notification.

@nick_26792935116 Don't include url as they are not allowed. Add spaces.

Try to install Filezilla or Cerberus ftp server on your PC. It should work. To troubleshoot capture traces through Wireshark.

@nick_26792935116 Yes, it has been released, removed for a few days and is not back at the download center. Did you manage to make the call feature working?

@gralin So far none of my cameras did ever invoke an upgrade. I keep record of their current version and every quarter I email support to check whether there has been any newer fw. Note that for battery cam, the only way is to ask Reolink support to add it to your cam profile (identified by UID) and then it will be automatically updated.

@ruben-vanlommel_60754004429 I suggest you to email support on support @ reolink . com (delete spaces).

@gralin You need to update manually. And I suggest you that every 3/4 months or so, email support to check whether there is any newer fw for your models.

It is not advisable to upgrade once a fw is available (sometimes it is a zip file, sometimes pak file). It is not the first time that after releasing the fw, it will be removed as they discovered a bug. And if you upgrade, the camera might not come up and this means no security at all. So it is recommended that upgrades are carried out manually.

I don't know what checks are made before upgrading. I assume that this is done but I suggest you to ask Reolink support or if you have a spare camera.....you might apply a different fw.

@tiaan_781250483077293 So why all these complaints. Hopefully they will sort it out like what they did in the past.

@brent-yoches_392520784879857 Battery operated cams cannot be managed by the NVR fir the obvious reason of battery draining quickly. Yes, you can add Argus 3 Pro/Ultra to your application. Just add them using the UID on your Android/Windows clients.

On battery cams, recording can be on SD and/or cloud. No ftp and no nvr integration.

@user_798152400830710_798152400830710 Detection on 823A is based on pixel changes. And this is poe/dc powered camera. Only battery operated cams come with PIR.

@tiaan_781250483077293 But to have the call emulation you need to have the application running.

@artech That implies you need to purchase an NVR with a doorbell. And SIP server requires static public IP (client registration) which is not the case with a number of ISPs. So best option is Reolink/provider hosts the SIP servers.

@tiaan_781250483077293 This is rather based on push notification and so you need to click on the received notification which will start the application or it will pop up if you are in the application as your case. This is not practical at all.

Implementation should be based on registration of both doorbell and client. One can use either XMPP + SRTP (whatsapp) or SIPS + SRTP(VOIP). Competitors (arlo, wyze, eufy, etc) implemented the voip method.

@rodp Could be. Android 8 is too old now.

@vodkan_410792752525441 Email support. They should have add it similar to a smartphone. Ensure it is on HSPA as otherwise you have issues.

@user_797938908946587_797938908946587 You need the certificate file with extension .crt and the key file with extension .key. You need to use OpenSSL to generate them.