Best posts made by joseph_1979

@andy It must be something specific on your machine as no other member has reported such an issue. Please check that you have the most updated graphic driver (perhaps uninstall it and install it again). You have encountered this issue on this application only or you had similar issues. What is the model of the PC and which graphic card is installed?

@user_773510003101839_773510003101839 Exactly. Let see.

@user_594027275649135_594027275649135 After rebooting the dynamic settings in the camera (ordered by the client to forward stream) are lost and the application is unaware of what happened at source (camera). So there will be no streaming towards the client and the client doesn't check the stream. I think Reolink should monitor the stream and if no more packets are reaching the client, it shall re-activate the recording. So for the moment I suggest you to inhibit the rebooting at the camera side.

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

@harrylane3_531242661216426 Indeed. Hope Reolink provides a solution to this. Will notify them.

@user_654306224615431_654306224615431 In the past I had one or two issues with push notifications. One was on Argus 2 and I resolved it by restoring the cameras. I was not on site and so had no means of capturing any traces.

On the second occurrence I was on site and so I captured some traces at the router and the smartphone sides. So when I activated push notification from my smartphone on a particular camera (identified by its UID), the client requested a token from Google FCM and subsequently provided in the response message. Then the client forwarded the token (with other parameters such as UID) to Reolink message application server. So far so good. When the camera detected motion, an alert message was sent to the pushx.reolink.com application server. However, the push message notification was not being sent by Google FCM. At the same time I was receiving push notifications for other applications. So I concluded that the issue was at Reolink message application server. It turned out that they were doing some upgrades on these servers. I told them to inform customers of any planned maintenance.

Thereafter I didn't had any further issues on push notifications other than the tone which sometimes they mistakenly change during the upgrade.

And yes they need to be more consistent between clients. Why I cannot enable/disable ports from the Android client or change the restart time? I informed support several times.

@bp787_46270538891 Same for 8.10beta if you want to test it out.

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

@andy There is some incompatibility between the Reolink client and your graphics driver. Uninstalling and re-installing the driver will not help. Can you please email Reolink support, maybe the R&D came across this issue? In the absence of diagnostic logs I cannot do much.

@user_654306224615431_654306224615431 I always tell them, use the genuine members of the communities (here, reddit and FB) and they will surely perform the appropriate testing. There are people out there who are really expert in a number of fields. For some of us these are gadgets in comparison to what we are responsible of.

@mamymam2013_465350299701478 Yes, this is the most stable official Win client available to the general public. I am using the 8.10beta which is still in beta version. Hopefully we shall shortly see the final version.

@reolinkshayla yeah it is filthy due to spray. And it isn't rightly installed....that's why I said that

@rainman You are right............but there are priorities which Reolink R&D decide which and when a feature/function shall be implemented.

@ebaruk_673045617504343 I have no idea. I am a customer like you. You may submit your query to their support on support(@)reolink(dot)com

They are using a number of old modules.

@user_63_633151097208875 I won't think this will ever be entertained. If stored in another external device other than internal SD or cloud then you need to play the files using a 3rd party application.

@og These are old NVRs and their hw doesn't support the DUOs models together with the trackmix as detailed in this link.

https://support.reolink.com/hc/en-us/articles/900000602543-Hardware-Version-of-Reolink-NVRs/

But if you do not intend to add 8M/12M, DUOs and Trackmix and doorbell then keep them till they become faulty.

@user_63_633151097208875 Just do a search on P2P protocol and you will get an idea of how data flows between the client and the IP camera. Once I did get into details and maybe you can do a search in the community articles. As to enhance security, have a strong password and change it say every 2 months and if you have fw then implement some rules.

@medway-computers_685415553384577 Therefore some firmware as the E1.

@rainman you need to restore the camera.

@kimchigun Only a few models as indicated in the link https://support.reolink.com/hc/en-us/articles/360008563054-Introduction-to-the-Wokring-Principle-of-Patrol-for-Reolink-Cameras/