Posts made by joseph_1979

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

@davidandrewpowell81_526149738635440 I suggest you to roll back to 8.8.5 on the other pc and wait till they fix it. You are not the only one to encounter this issue. I cannot reproduce and so cannot delve through.

I saw some have drag the camera out of the liveview. Others have deleted and added cams.

In my opinion when upgrading to 64 bit client they should have done a clean up of the installed client and its data and then proceed with the fresh installation. The 64 bit client is using the same data of the 32 bit client.

@davidandrewpowell81_526149738635440 Another suggestion. Can you delete one camera from client and add it again please? None of the configuration is lost.

Versions 8.10.x are 64 bit clients.

@thornton_620874794598455 I told you to restore one first and then one by one if the first works. Always take note of what the settings were before restoring.

@user_667520826966038_667520826966038 E1 OD Pro is DC powered. The picture is crystal clear and never had any false alert since installed.

@thornton_620874794598455 So it works after restore?

@davidandrewpowell81_526149738635440 I am a customer like you and trying to help wherever possible. I have it installed on both Win 10 and 11 and don't have any of those mentioned by you and the other customer. But there are other issues which I have reported to support. I normally close tickets when our customers are satisfied with the solution/answer provided. Moreover I close tickets with international BIG suppliers if I am satisfied with the solution provided.

Presumably these issues didn't appear in your case when you were running the 8.8.5 (32bit client). So the difference is the environment. Are your Windows and MS C++ distributed packages updated?

I re-read your comment and I see that you are unable to connect to the cameras? Can you ping the cameras? Can you describe your setup? Are you using different VLANs?

@das-dos_208145718501556 No response!! So command is not reaching the camera as otherwise there is a response. Can you please send the command directly rather than executing the script? Can you ping the camera?

Try this simple cmd to get the time

curl -s -k -X POST -H "Content-Type : application/json" -d "[{\"cmd\":\"GetTime\",\"action\":1}]" "https://camera_IP/cgi-bin/api.cgi?user=USER&password=PASSWORD"

@davidandrewpowell81_526149738635440 Win 10 or Win 11?

@andré-figueiredo Unfortunately we haven't seen this implemented yet.

On this line we have requested
1. Separate detection and alarm trigger zones each of which has its own scheduler
2. In email and push notification, a separate schedule for each object type.
3. In sensitivity, a separste scheduler for each object type which allows user to change its value at least night and day.

@thornton_620874794598455 Do a restore on one of the cameras and check again. What is the model of your smartphone?

@bcloco_670093297197135 I presume the cams are connected via a switch to your server on which you are running the Windows client. When this happens go to the task manager and on performance tab check the receive bytes on the connected eth. If it is low then the camera are not sending the stream but I doubt this is the case.

As a test I would remove the recording and have the live view and see whether this occurs. I suggest you to start with low resolution and then repeat the test with the highest resolution. Leave hw acceleration off (you can permanently set it to FALSE in the usersettings file). Repeat the tests with recording on. I would also use an application to pink the cameras to ensure they are always reachable. There are myriads of such programs.

@das-dos_208145718501556 I replaced the '5' with '0'. Please insert your IP and credentials and try again. What is the error received? Ensure https is enabled. I tried the command on a non-patrolled PTZ camera and hereunder find the expected response. This is because parameter StartPatrol is not accepted on my camera.