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

@melroy UID is like your ID number which is a unique identifier pointing to a number of profiles in various institutions. 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 assuming 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 associated 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 associated with passwords such as create a strong password 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 assigned 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 massive.....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 passing 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.

@reolinkshayla They are all excellent products. I have one question though. Do the new E1 ODs have the same gear mechanism as the previous models? Thanks.

Update: support told me that they have different gearing mechanism and hopefully the problem of deviation is something of the past.

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

Thanks for the update. Can you please let us know what bugs have been resolved by this release?

@dgordon42_415060065599711 I didn't hear anything from support. They should move away from the push notification and base their design on SIP(S) + SRTP or XMPP + SRTP (used by Whatsapp) as has been implemented by other camera suppliers. Of course this design requires SIP servers which entails the client and cam to be registered. SIP is fun...........have been working on this protocol (and many many other protocols) for a long time.

In security one of the most important factor is contacting the owner. We receive lots of push notifications, messages, alerts on our mobile and we tend to ignore. But if it is a call, we do check who is calling. So they can add a feature for the cam to call in the event a particular event is triggered, say glass sound, alarm sound, etc. The ideas depend on one's immagination.

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

@reolink-fiona Hi Fiona, thanks for the invitation. We will certainly assist the members as much as we can.

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

@reolink-daisy So far the TM and hopefully we have the CX version with improved Telephoto.

@reolink-daisy We do appreciate the launch of new cameras but we wish to see new features and robust and bugless clients. There is an endless list of features we have requested.

@big_ted of course. But they need to improve their clients and add more features customers are requesting. We are seeing new cameras but no features.

@marepinta_741786199699593 E1 OD Pro requires dc power through an adapter and do this is not suitable to you. Of I recall correctly Trackmix abd Argut OT ultra battery operated provides zooming. Check them out at Reolink site.

@user_678736611209466_678736611209466 nope.

@mamymam2013_465350299701478 Uh....the ladder to reach the camera :)....

@reolink-daisy Can we have the specs please?

@user_678736611209466_678736611209466 we still need to wait for that....it's something else...a battery cam.

@mamymam2013_465350299701478 Thanks buddy. I will check and test it out right now.

Outcome: Colour is better and almost the same as the previous. Slightly more natural. Max bitrate and max fps for Clear mode have been kept too. WIFI signal strength.....one bar. I need to check the signal strength but need a ladder :). When I will do some work outside I will check it.

I told them for the WIFI cams to include the speed test...........from the cam and not the smartphone....from the smartphone there are myriads of speedtest applications.

Always keep older fw and clients just in case you need to revert.

@user_827561404055684_827561404055684 Normally this occurs when there is moisture in the reset button.