Posts made by joseph_1979

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

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.

@issom I never use time lapse. I suggest you to report it to Reolink support on support @ reolink.com.

@cle_911680035188990 We, engineers, never use anything we develop. We let it to the customers to use it and report back ....ha ha ha:) But professional ones do conduct rigorous tests under lots of scenarios and listen to customers' feedback. I have requested Reolink to implement schedule and status for the scene mode since it first appeared. In case of cameras you need to add it for each model. But you have the HHP and it is easy to implement and query the connected devices. This shouldn't take more than a day to implement on the HHP. And this should have been there from day 1. My personal opinion.

Hopefully we see them implemented one day.

As for the activation of push notification (for example) the procedure is to activate them via the home hub scene mode (Home or Away). If you activate them through the camera settings it will not work. I spent 15 minutes to troubleshoot this....as I was expecting that it should work if I set it through camera setting from the HHP. We learn through experience.

We are in 2025 and manual scheduling is something of the past.

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

@weiliang Yes you can. Just disable auto reboot as illustrated below. Use Windows client. I do not have this issue. However, I am using my WIFI network.

@ram_799163019051222 I suggest you to submit your requests to support on support @ reolink.com. I am aware of the first two issues. Cannot comment on the Alexa part as I don't have it.

@jeankok_709237676638430 Correct. You cannot access any settings when connected to a TV through HDMI. Only layouts. You need to use the client to change any setting. I already have submitted a complain to Reolink. Can you do it too? The more requests they have the more we see it implemented.

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

@big_ted Well 2GB is more than adequate unless you constantly watch live views or playbacks. So you get a year of free SIM and then you have to top it up or swap it with a local one. How stable is its 4G connectivity? Any disconnections? Any errors? I would have checked the GTP-C and U protocols but one needs a probe which I have access to and good knowledge of these protocols :).

Do you know who is the provider of the SIM (from IMSI)?

@davidguy2020_353818044313826 Install Reolink Windows or Mac client from their download center (https://reolink.com/software-and-manual/) and then add the camera from the + sign. However, prior to this you need to get the UID from the camera. Follow this link https://support.reolink.com/hc/en-us/articles/900003548586-How-to-Add-Reolink-Products-to-Reolink-Client/

If the playback is not smooth then there is some restriction at the transport layer. It could be from camera to mobile operator (you need at least 12Mbps upload speed) and then the download speed on your smartphone. There is also the Amazon servers to act as a relay server and maybe there is some congestion here.

@kevinkss I think the issue is the upload speed of your router. Can you install ookla from playstore on your smartphone and check it out? Switch to WIFi and check upload speed. Now switch to mobile data and check download speed. From the camera side, it is the upload speed which is important. The upload (from router to your ISP) should be at least 20 Mbps.

Are you able to pass a cat5/6 cable from the router to the repeater? If yes then configure the Re715 as access point rather than repeater. In this case the data between router and RE715 is over ethernet.

@user_901203979997352_901203979997352 we have requested that festure. I read that during this year they will add IFTTT.

@user_901203979997352_901203979997352 Yes, this is the correct procedure. Thanks for sharing with members.

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

@knowonehere_887891129163931 I have the standalone floodlight and has all the features that you have requested.

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