Posts made by joseph_1979

@steve_701706398327000 I do know that detection zone per object type has been implemented on Argus 3 Pro and DUO 2 respectively. I did request that this should be implemented across all the AI models and possible to add a scheduler per object type. This is all software and the routines have already been implemented on other models and so it isn't that difficult (assuming enough memory and processing power)

Try to email support and request it.

You might opt to record but exclude vehicle from push notification.

@user_704102555316464_704102555316464 Do you have any FW rule on this server? Which Windows server are you running?

@steve_701706398327000 Use detection zone as illustrated in https://support.reolink.com/hc/en-us/articles/900003638406-How-to-Set-up-Motion-Detection-Area-via-Reolink-Client-New-Client-/

I don't have this model so I cannot tell whether it has one global detection zone or a detection zone for each detection type.

@user_704102555316464_704102555316464 Try to disable the hardware acceleration first from the main menu of the client and re-run appl.

@thornton_620874794598455 Perhaps you can email Reolink to forward you an earlier version of the Android client or else update the one running on A42 to 4.37.0.6. I have no issue with this client other than the missing stretch mode live view for some cameras like E1s and RLC511s.

@thornton_620874794598455 I am running 4.37.0.6. What clients are you running on both smartphones?

@thornton_620874794598455 So this means that the cameras are sending the alert to the Reolink pushx server which in turn is sending the push request to FCM and FCM pushes the message to the A42. So there is something within the S20fe environment. Did you upgrade the S20fe lately? Are you running the latest Android?

@user_703793344291048_703793344291048 Eh........ they now support ECDHE (Elliptic curve Diffie–Hellman exchange). Cerberus accepts both ciphers.

s@user_703793344291048_703793344291048 So you were using the FTP rather than FTPS. Then email Reolink support and inform them about this.

@user_703793344291048_703793344291048 You see that cipher shown in your reply is not included in Filezilla. If you add it then it should work.

@user_703793344291048_703793344291048 Just to test it out can you add the ciphers I listed below. It shouldn't take you long but save the file before doing any changes. I see that the cipher is not found in the Filezilla config.

@user_703793344291048_703793344291048 I think there is an issue on Filezilla sever when using FTPS (explicit). Try if it works on Cerberus ftp server (free).

Try this

1.(A) Shut down the service part of zFTPServer.
2.(A) Open Settings.ini in the zFTPServer directory
3. Go to the [FTPS Ciphers] line. Below are the ciphers zFTP offers for negotiation.
4. Go to the end of the line listing the ciphers, and before the terminal double-quote, add:

[FTPS Ciphers]
"<List of other ciphers>,DHE-RSA-AES256-SHA,DHE-RSA-CAMELLIA256-SHA,DHE-RSA-AES128-SHA,DHE-RSA-CAMELLIA128-SHA"

5. (A) Save the file.
6. (A) Start the service again.

(A) means administrative privileges required.

@user_611510361510013_611510361510013 Click playback (icon appearing below in live view) and then select date when the alert was triggered. You should see all the recordings for that day. Select the one you think you are looking for and it will be played.

@das-dos_208145718501556 Ha ha ha............. it's normal. Sometimes a glass of wine and some nuts will help together with a good movie :).

@ks Yes I recall this complaint. This is definitely a heap memory leakage. Can you please paste these in an email and send them to Reolink support so that they will investigate? Maybe calling the malloc() function without issuing the free(ptr) to release it. Visual Studio has a good memory analysis tool which I used it during testing of my projects.

@booth2_409818763895018 According to their Download site the lastest firmware is v.3.1.0.989_22051911 which is more than 1 year old. You can check your firmware from the info menu. Try to reboot it. I would still email Reolink support to see if there has been any newer firmware.

@lilonders_288520038867122 On multi view it has been restored but not for single view for some of the cams like E1, RLC-511WA, etc.

@user_646203682046022_646203682046022 Please run the service 'resmon' (To open the Run dialogue, press Windows+R, then type 'resmon' and click OK) and check the commit memory of the Reolink processes (you should find 6 reolink processes). Select "Commit (KB)," which will reorder it so that the activities that use the most memory are at the top. Can you paste it here?. I would take it up with Reolink support to delve through it. I didn't encounter such a high usage of mem on any of the Reolink processes and I left all 6 cameras in live view for 4 hours.

@thornton_620874794598455 Can you leave the notification only on the other smartphone (not S20fe) and check again for a whole day?

@thornton_620874794598455 Do you have another smartphone? Just to eliminate the Samsung S20. There are a number of entities involved in the process. Android smartphone registers with Google FCM and receives a Token. The Reolink client will then forward the Token to the Reolink push application server (pushx.reolink.com). This server assigns the token to the UID of the camera. So when the camera detects an object it sends an alert to pushx.reolink.com. This application in turn sends a request to Google FCM to send a push notification to your mobile (based on the token). So the entities are the camera, Reolink pushx server, Google FCM, the mobile operator or BB ISP to deliver the message and the smartphone. FCM/Reolink pushx servers cannot be the case as it will be a global problem.

You stated that when you restart your smartphone, PMN will be received and so the cameras are OK too. Try to use another smartphone to test it out.

Note that an application on Android can have up to 24 queued push notifications. If not acknowledged you will not receive more push notification for same application.