Best posts made by joseph_1979

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

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

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

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

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

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

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

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

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

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

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

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

@rainman you need to restore the camera.

@medway-computers_685415553384577 Therefore some firmware as the E1.

@andrewadventure_658285543473233 Sometimes the answer is in front of us and our CPU is busy processing other prioritised tasks.

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

@rainman Can you list what configuration you have changed from the default value? Can you leave out the detection zone and try again? Just to identity what is causing the issue. Moreover please check that you have the most recent firmware. You can check it in Reolink download center.

@fxn_329751914586312 Have you added the apn?

@rainman I am not a Reolink employee but supporting members wherever possible based on my engineering skills. It is clear that this has nothing to do with the detection zone and most probable it is a firmware issue. I do not see any further tests and so I suggest you to email Reolink support and include your hardware version and the tests you have conducted. I have no access to logs and they are limited. One last test please....... Can you install Reolink client on another smartphone and re-create the config from scratch for one of the DUOs and check it out? Are you on Android or IoS? If you are on Android there is a limitation on the number of push notifications per application. If I recall correctly this is limited to 24. In case of Android smartphone, when you click on the push notification of the camera through the client, the client registers with Google FCM (it stores the IP of the client) and the client receives a token. Then client forwards this token (you can see it from the system menu of client) to the Reolink application server receiving the push messages from cams. So when there is a person detection the camera sends a message to Reolink application server. This application server already knows the token (passed by client) and sends a trigger message request to Google FCM. This includes the token the client registered with FCM. FCM then uses this token to fetch the mobile profile (IP) and pushes the message to the smartphone. This is high level. It's complicated but that part we leave it to the troubleshooters :).