Best posts made by joseph_1979

@chopstix So far Reolink introduced file encryption on Home Hub, Home Hub Pro, Altas Pt and Altas PT Plus. Reolink stated that it will deploy this encryption to its products (maybe recent releases plus new ones).

Unfortunately if WIFI is lost or the HHP is switched off and there are recordings on the cameras SD, the HHP will not synchronised the video clips. User has to delete camera and access it in standalone. There have been a lot of requests from customers to allow them to access the cameras directly and hope they are working on it. Personally this should have been available from the day the HHP has been released.

@chopstix Fully in agreement. And on the HUB they should allow the deletion of clips using the admin account. There is a lot of features which can be added some of which may not require changes at the camera side.

@dotslash_888755199733903 Indeed the speaker and the USB port should have been under the camera. I have mine fully exposed and it did rain for days without impacting the functionalities of the device. It is classified as IP 66. While an IP66-rated camera is designed to be highly resistant to water, it is not designed to be submerged in water or to be continuously exposed to heavy rain or water jet.

I do concur with you that the vertical FOV is rather low. And it is not only this cam but all the newly released cameras have lower vertical FOV. We have complained about this and asked Reolink to make it bigger as we used to have them in the past.

As for the anti-theft (or camera left off-line) we have asked for a HB mechanism. In the event that this is missed for say 5 times an alert is sent to the customer in the form of email/push notification. The HB mechanism can be implemented between cam and P2P AWS servers, between camera and NVR or between camera and Home Hub. Maybe they can add a GPS and we get the location too just in case it is stolen. Why not. And if this is difficult for them to do then they can add a feature on the camera with adjustable time interval to send an email/push notification say every 12 hours.

@reocam_448003255267488 Yes you can. Check out this link https://support.reolink.com/hc/en-us/articles/900000537406-How-to-Connect-PoE-Switch-Router-and-Reolink-NVRs/

@chopstix From the specs provided by the supplier, it is clear that it can be used as AP as illustrated below. Issue could be from repeater to router. So in this setup it is excluded.

@chopstix Bingo. Yes I do remember that NT server. It could be a memory leak. It's the modern way of hiding problems which cannot be solved :).

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

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.

@reocam_448003255267488

Push Message Notification works on both WIFI and Cellular.

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.

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

@twitch04advert_547475244449986 If there is adequate external light then the spot light will not lit. Do you see the IR leds on? Most probably not because there is adequate light. I have one outside my main door and the spot light never lights up despite activated because of the street lighting. To check it out get it inside a dark room.

Your firmware is more recent than what is shown in the download centre.

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

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

@mcs-yard-4_748142991896757 If you are not able to communicate with the camera through the client then it is not possible to restart or restore it.

Could it be that the battery has been drained? Could it be that it lost 4G coverage? Could it be that the data bundle has been used? The best option is to go on site where the camera is installed and check.

@reocam_448003255267488 If both cameras are POE then you can use a POE combiner/splitter as illustrated in https://support.reolink.com/hc/en-us/articles/20057468511897-Introduction-to-Reolink-PoE-Combiner-and-Splitter/

Normally we do not connect the cameras directly to the NVR (even if it is hybrid) but rather through a POE/Normal switch. This gives us the possibility of accessing the cameras directly and if the NVR becomes faulty we are still able to connect to the cameras. One more advice. Install high endurance SD (say 64G) and enable event recording on them. Don't forget UPS.

@chopstix it is rather difficult to state why it stopped streaming to 2 PCs without knowing the network configuration and if the client was experiencing leaking memory or conflicts with other services.

Best option is as you stated to open a ticket and support will ask customer to forward logs.

@reolink-oskar It's really plug and play. However, we would like to see more features added to the HHP. I already provided my feedback to your senior support.

@gailsmule_905391527133360 Install Netspot from Playstore on your Android smartphone and check the signal strength of your WIFI 2.4G and 5G bands at the location where you wish to install the camera. If it is less than -70dBm then you are fine otherwise you shall encounter communication issues.

• -30 dBm to -50 dBm: Excellent signal.
• -50 dBm to -60 dBm: Good signal.
• -60 dBm to -70 dBm: Fair signal.
• -70 dBm to -80 dBm: Weak signal.
• -80 dBm to -90 dBm: Very weak signal, possibly no connection.

This application allows you to check if your neighbours are using the same channels as yours and this will cause interference. You can change the channel from your router.

@chopstix Additional note to Chopstix's comment.

Ensure that the preference band is set to auto when changing from 5G to 2.4G band as otherwise it will not anchor to the 2.4G band.