Posts made by joseph_1979

@rainman This is an old problem with FE-P v1. I suggest you to open a ticket with support.

@onlooker_890638347890931 Depends how much it is triggered. Once I tested an Argus 4 Pro on an intense traffic road and it didn't cope.

@chopstix At least fixed :).

Issue is still at the sw dev team. Apart from this I have a WIFI stability problem on the RLC-811WA. I am getting choppy audio and freeze frames. Camera is less than 3m away from the WIFI access point and 1 m below it I have the battery doorbell which is quite stable. This issue arises because they are using TCP rather than UDP for local transport. To the best of my knowledge live streaming/audio is mostly transported over UDP.

@chopstix So we got through same problem. I opened a ticket. I will ask for an update.

@chopstix If you set the WIFI Band Reference to only 5G and then you change the WIFI connection to 2.4G then it will not connect to the 2.4G. It won't even try to connect to the 5G. This was my scenario. This is a bug for me and I did report it.

@reolink-oskar With HHP I would add the Argus 4 Pro, the Argus PT ultra and the Argus 3 Ultra. Perfect match.

@reolink-oskar We really miss Wild Life. Awesome video.

@chopstix That's the design now.... it works as designed... their usual answer. I had similar issues with big suppliers and then I withheld support payments.

@chopstix As for the password this is forwarded by the HHP. It should show more bars...2.4G has lower wavelength and so longer range and more penetrable. The problem is why it didn't connect to the 2.4G? On the WIFI doorbell do you have the preferred connection set to 5G? If so this is the problem. I have encountered this and had to connect via the eth port to fix it.

@user_901203979997352_901203979997352 Submit your request to support on support @ reolink . Com

I did ask for flexible schedulers on various functions.

@reocam_448003255267488

Your Android smartphone which is connected to your home WIFI has Google services running on it which continuously update the Google FCM with its IP. So when the Google FCM receives the push message request from Reolink message handler server (AWS), it knows where to send it...to the IP of your smartphone. Consider the IP as your home address which is unique in the world. This is at high level as there is NAT at your router but this is beyond your understanding.

@user_777824613310594_777824613310594 Submit your request to support. The more requests they get the more we see it implemented.

@ray6_474495078473946 You can improve detection during the night by adding an external IR illuminator.

@user_917272178602112_917272178602112 Have a look at https://support.reolink.com/hc/en-us/articles/4411454612633-How-to-Set-the-Pre-Motion-Recording-via-Reolink-Client-New-Client/

@user_inktvis75_745316076404877 According to its specs no ptz.

@user_915488562708725_915488562708725 Unfortunately it is not possible. Maybe this is achievable through HA.

@obrowne_92224518385850 I suggest you to submit your complaint with relative screenshots to support on support @ reolink .com

802.1XThere is no network authentication on any of the Reolink camera. Logging is through username/password credentials. If you need to add security then you need to have VLAN and use VPN to access them remotely.

@crimp-on_62210811129 if your software is robust and well tested then there is no need of an auto reboot.

@reocam_448003255267488

Push Message Notification works on both WIFI and Cellular and works only on Android and IoS.

1 When you run the Reolink client for the first time, it will register to the push message service provided by Google FCM (Android) or Apple APNS (IoS).

2 The push service FCM/APNS generates a unique token to identify the device+application and returns this token to the application. Note that the google/apple services running on the smartphone will update the FCM/APNS with the source Public IP of the smartphone.

3 When you enable push notification on a camera, the application transmits the token together with the UID of the camera to the token maintainer hosted by Amazon.

4 The token maintainer checks if the UID is already available. If not a record is created with UID as the index and token added as a field in the record. If
the record exists, the new token is added.

5 When the camera detects an object and the push notification is enabled, a message containing the UID is forwarded to pushx.reolink.com ( will hit the server mentioned above -- you can check its IPs with nslookup -q pushx.reolink.com). The application workflow requires a push notification to warn all registered devices/apps.

6 The push provider (Reolink message handler running on AWS) reads the database using the UID as the pointer to the registered tokens. Note that a camera can be enabled from a number of smartphones, each of which has its own token.

7 The push provider (Reolink message handler running on AWS) sends push notification requests to the push service (FCM or APNS) for each token.

8 The push service (FCM or APNS) broadcasts the notification messages to all registered devices using the source Public IP. So if the IP is assigned to a mobile operator then the push message is sent over the mobile packet data i.e. FCM -----> Internet ----> IP core of mobile operator - PGW - SGW/MME - eNodeB - smartphone (assuming 4G). If your smartphone is connected to WIFI then we have Google FCM -----> Internet ------> ISP IP core ---------> GPON OLT (assuming fibre to the home) ------>GPON ONT at your home ------> router at your home ---(NAT Public to Private IP)------- smartphone connected to WIFI.

And if you need to know how media is conveyed between camera and client then read my explanation at https://community.reolink.com/topic/87/how-does-the-reolink-uid-actually-work/2?post_id=22657&_=1739217026299

Hope that now you have a clear picture of how things work.