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

@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 which points to a message handler application running an AWS servers in the US. The application will look for the UID included in the received message and will get all the tokens associated with this UID (token for every smartphone which activated the push message on the camera). It will then forward the push message request to FCM (Android) or APNS (IoS) which shall push the message to your smartphone (there is a socket opened between smartphone and FCM/APNS). 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. At the same time the client broadcast a packet with command aaaa0000 on the network with destination port 2000. Note that the Client broadcasts the packet with payload aaaa0000 using destination addresses 255.255.255.255.255 and 192.168.1.255 (or your configured IP subnet). Now 255.255. 255.255 is the limited broadcast address which is only propagated within the single subnet of the interface that sent it. It is never routed to other subnets unlike the subnet directed broadcast address 192.168. 1.255 which may be routed from elsewhere, depending on router configuration. So in most cases only the cameras within the same subnet receives this packet. If there are cameras on the same network they have port 2000 opened and are listening for any broadcast with command aaaa0000. If this is received then the camera will reply to the source IP with the command aaaa0000, UID, IP, port 9000, mac and ID. So once the client receives this on port 3000 then it will start communication with the camera using TCP and port 9000. Note that at this point the communication is directly between the client and the camera which are on the same network. 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 opened with this 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.

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?

@big_ted There are issues with this client. Horrible fonts, audio level, config wheel for ethernet connected cams disappeared, flipping between stretched and not-stretched mode, slower, etc. Downgraded to previous version. I don't know who tested this client before launching it.

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

@tucker3738_367076416745686 It seems that their strategy is only cameras. No IoTs. Even smart plugs they are no longer available.

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

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

@user_687419430965498_687419430965498 under alarm detection enable auto tracking. Select all tracking type..person, vehicle and pet...Set tracking method as digital tracking first...horizontal range...set left and right range....schedule ensure all is enabled.

Under sensitivity go to smart detection and set person to 55, vehicle to 50 and pet to 60...or whatever is your preferences.

If you have false alarms there are other parameters to adjust like alarm delay, object size, sensitivity, detection zones etc.

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

@issom They should have sorted it out at program level. At Reddit you find experienced members who are very helpful. I am there too :). Thanks to share it here.

@mandy_977783715094766 Delete camera from Home Hub Pro. Go to recording of the camera and disable continuous recording. Enable motion recording using person, vehicle and pets and untag any motion. You need to save the settings. Log off/on camera, enter the recording menu and check that the settings are as you have left them. Then connect it to the HHP.

@colin-grimshaw_430254205366491 I suggest you to make the non-detection zone a little bit bigger and remove 'any motion' detection and base your triggering on persons, vehicles and pets. I have seen similar complaints. Maybe using the object size may help. At the same time I will open a ticket with support.

@reolink-cam_813700743893181 Procedure is correct. That's bytes per second. Max is around 8M bytes per second. You may transfer to the USB stick but you need to access the NVR UI.

@andre_148322405413012 https://home-cdn.reolink.us/files/client/electron-release/reolink_setup_8.19.6_0.exe

@mamymam2013_465350299701478 I haven't been asked to test any pro cameras. Whenever I am given one I do rigorous testing and provide feedback. Then it is up to the dev team to take action.

@user_975726620733642_975726620733642 It seems that the Argus 4 Pro is connected to the Home Hub. When a camera is connected to the HH, the flip vertical and flip horizontal are no longer available.

I suggest you to take note of the UID of the Argus 4 Pro and recall the credentials used to log on the camera when it was in standalone. Then delete it from the HH and fix the image orientation. Then add the camera again to the HH using its UID.

@user_782828081017023_782828081017023 They use different repositories and the one used by cameras is never populated by any fw unless they want to push it. We have been asking for this for quite some time and should be available for all their products. Every 3 months I email support to check whether there is any newer fw for battery operated cams. And on the website we want a history of the fw added rather to check one by one. This is very basic.

@user_972866311930034_972866311930034 We stated here under topic 'v8.19.5 client' that this client has a number of bugs one of which is audio during playback. They have released v8.19.6 and the audio at playback is back again.

@mamymam2013_465350299701478 I have never came across any engineer from Reolink at Reddit, here or facebook communities. These are all managed by moderators who are customers and have no access to documentation. Our answers are based on experience and the knowledge we built through our education. And we do it voluntarily as we love support others wherever possible.