Reolink Year in Review 2023
How ColorX Technology Turn Night into Day
Reolink App v4.43 Released
@brian-nielsen_442682315796643 We have requested the support team to inform dev team that a lot of customers are asking for the doorbell to do an outbound voip call to the smartphone with possible actions as is being done by other brands. Other than this we need the full profile T support with full duplex audio.
Customers want clearer pictures and able to read text or numbers within reasonable range. They are also requesting higher fps especially at night time. And yes customers are looking also for HDR implementation. All this comes at a higher processing power and very powerful sensor. Can someone from Reolink development team update us on when these shall be made available to its customer?
Thanks for the update. Can you please let us know what bugs have been resolved by this release?
@islandman63_201848685748477 With the newest release the stretch mode has been removed. So to get the stretch mode you need to go back to the previous version. There have been a lot of requests from members to have the stretch mode back and hopefully we shall see this as an option.
@melroy UID is like your ID number which is a unique identifier pointing to a number of profiles in various ins[censored]utions. If you go to the hospital they will ask you for the ID and by entering this ID they will get all your health information.When you power up your camera, it does some DNS queries to get the IP addresses (A record) of the P2P servers (provided by Amazon and Azure) and registers with the P2P servers using its UID (we are [censored]uming here that UID is enabled). At regular intervals the camera sends packets to the P2P servers which shall include the UID (encrypted). The application on the P2P server decrypts the packet and extracts the UID. The application extracts the private IP and Public IP (BroadBand IP:Port) of the packet and populates them in the respective record [censored]ociated with UID. If the camera changes IP then the record pointed out by the UID is updated accordingly. The credentials you created are not forwarded to the P2P servers. Well if you can emulate the P2P protocol and know the encryption method/phrase then you would be able to get the private and public IP of a particular UID. But so far there have been no such breaches and still you need the credentials to get access to the camera. Therefore it is imperative to follow the policies [censored]ociated with p[censored]words such as create a strong p[censored]word and change it at regular intervals. At this point we see that there is a P2P socket between the camera and the P2P server. For your perusal the camera sends the alerts to the domain pushx.reolink.com. The application server will then forward the push message request to FCM (Android) or APNS (IoS) which shall push the message to your smartphone. Token provided by FCM to your smartphone on registration is forwarded to Reolink pushx application server. This token is included in the request made by this application server to the FCM to push the alert on your smartphone.Now let's take a look from the client side. When you run the Reolink client, it will send a DNS query to 16 P2P servers (p2p1, p2p3, etc) and the response is the A record containing the IP address of the P2P server. Any P2P server which is not yet [censored]igned will get the A record with the loop IP (127.0.0.1). For each working P2P server, the client requests the Public IP (the Relay P2P server with which the camera is connected) and Private IPs of the camera using destination port 9999. So if we have 8 working P2P servers and 8 cameras, then the client will send 64 requests over UDP. When the client receives the replies, it will first start to open communication with each camera using the private IP over TCP. Here the credentials are included in the request. If the camera replies then communication continues with the media being sent over UDP. Note that at this point the communication is directly between the client and the camera. At the same time the client also sends the request using the public IP. This public IP is not the public IP on your BB router but rather the IP of the AWS/Azure Relay P2P server to which the camera has been registered. But if communication using the private IP fails then the client establishes connectivity with this Relay P2P server. Recall that the camera has already a p2p socket with thus server. Communication is over UDP. In my opinion, this has been adopted because a number of ISPs restrict users to connect directly to other devices. Technically this is not P2P as there is the Relay server in the middle. So in this case the encrypted packets flow from the client to the Relay server and from the Relay server to the camera and vice versa. In this case the encrypted credentials are sent to the camera through this Relay P2P server. And here comes a question....if there are 1000 12Mbps@25fps and using high def H.265 and the cameras are being accessed remotely using the public IP, then on the P2P relay servers we need a bandwidth of 17Gbps .......... which is really m[censored]ive.....This explains the delay between viewing using private/local IP (cameras and client on same network) and public IP (other). And I do not think that neither Amazon nor Azure will give unlimited bandwidth.Now the question being posed is 'Do we trust this setup?' Do you trust p[censored]ing the bank information when buying over the internet? Do you trust ATM machines which are connected over BB? Do you trust your voice calls over 3G (A5/2 encryption)? etc etc.............. so you have the answer.No matter how much security you have...there is always a way to get through. Even Alcatraz was a prison where nobody can escape...but they escaped. Nevertheless we need to do our best to protect and be secured.Apologise for the lengthy answer...but this is high level...can go to the low level...ha ha these are rather simple protocols with the most complicated being within the Telco NEs.
@bruceda_323950257770638 This motion tagging is quite interesting and merit an evaluation...and implementation. Other brands have it.@Fiona Please forward this request to the development team.
@terryjensen_510712816316578 I do not think there is a solution now. Previous Windows clients had an option to disable it but in the recent upgrades this feature has been removed. I have notified support to re-introduce it and its up to the customer if the camera drains the battery.
@user_623346741346376_623346741346376 I disabled any motion on the RLC511WA and have added a 1 sec delay for person and thereafter no false alarms. Since April I haven't seen any firmware update on this model.
@olive_608518832963622 that's the first implementation of Reolink doorbell. SIP calling will come too hopefully.
@diegosalerno_560796844831021 Good to hear your positivity on the video doorbell. Indeed the issue of low audio at the doorbell side has been identified some weeks ago and this has been resolved by adding the volume control to the speaker. This shall be available in the next Android release 184.108.40.206. As for the different rings, this merely depends on the application and not Android. Android limits the ring type per application. PMN can have embedded in it the type of ring tone. Recall that this is the first generation of video doorbell and we will definitely see new features in the next releases. Customers are asking for SIP calling and able to integrate it with the existing chime. Any additional ideas are more than welcome.
@user_793110460846229_793110460846229 I don't have Alexa and so can't [censored]ist. I suggest you to email support at support @ reolink . com (delete spaces as the site won't let me to include email addresses).Moreover, I do suggest you to ask the Reolink users on reddit https://www.reddit.com/r/reolinkcam/ . There are a lot of customers who have integrated the doorbell to Alexa. Check this out https://www.reddit.com/r/reolinkcam/comments/172k3h8/doorbell_issues_with_alexa/
@user_750021959827684_750021959827684 Not yet. Everyone is looking forward for this new firmware to test out.
@c0nfick3r_781404561744056 I suggest you to send some videos in clear mode to support so that they can refine their detection algorithm.Can you try to experiment with minimum and max object size?
@grantiago There is no such configuration.
@user_792702754615469_792702754615469 that's why the false alerts because of the high sensitivity for the smart detection. The higher the value the lowest resemblance. Set between 50 to 65. There are two sensitivity settings.....one for any motion and one for smart detections.
@user_792702754615469_792702754615469 What is the sensitivity for smart detection? The one you showed in low is for motion detection.I see 3s is a bit too much and I will use the object size too. You need some patience till you find the optimal setting.
@schuzili_761593036189872 It seems to be a common issue on all the E1s. I have the E1 Zoom and the E1 OD Pro and the audio is sometimes being recorded underwater. I did reported it but didn't get any fw with improved audio. I suggest you to email reolink support. The more emails they get on this, the higher the probability to fix it and improve their audio recording.
@iallinoro_169065503625461 Ben ogni tanto succede. Allora lui sta uzando la versiona nouva. Io non ho avuto mai la problema di vedere il stream.....ma di funzione si. Il tempo di fare tanti test prima di lanciare e' ormai p[censored]ato. Cost savings and less human resources......and of course talented engineers. I see this from the new engineers being recruited within my department. But this is life.
@thomas-oneill_306809385144533 Thomas, I don't have this NVR and so I cannot provide a solution. However, there are users at Reddit who have your setup and may [censored]ist you. Go to reolink reddit.
@user_792781723140271_792781723140271 fw still not yet released. We are all waiting for this to check out.
Hi there! Join the Commnunity to get all the latest news, tips and more!