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

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

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

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

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

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.

@reolink-oskar

In order to be in line with your competitors you need to implement actual calling feature based on VOIP or XMPP. The one implemented is merely based on push message notification. And to go the extra mile, implement face recognition. And what about IFTTT, matter and webhook? Not all customers have HA for automation and I see that IFTTT is very basic. You may include the door lock too as competitors did. There are more and more features to add. It depends on one's imagination and creativity. Just read the customers requests here, at Reddit and in facebook and you will have an idea of what they are after.

@reolink-oskar In my opinion it should have been a WIFI 6 rather than WIFI 5 booster so as to have your WIFI 6 (current and new releases) cams anchor to it at WIFI 6 speed.

How about having it powered through POE?

@user_949367016734899_949367016734899 Which problem?

@user_865232354136279_865232354136279 Detection is done by the camera and once triggered it opens two independent streams. One directed to the SD and the other to the HHP (Home Hub Pro). So the starting times should be merely the same. I did check this on my plugin and battery cams connected to the HHP and they are the same.

The only difference is the end time. The stream opened towards HHP is kept a bit longer. So there might be cases where you have two recordings on the SD and one on HHP. This is because the successive trigger occurs when the stream towards HHP is still open. The duration of the recording on the HHP will be the duration of the two recordings on the SD plus a bit more.

Note that there is no synchronicity between what is recorded on the SD and on the HHP. We asked for it and we have been told that it shall be made available in the near future.

@reolink-oskar This is a milestone reached by 2Q2025. Hopefully we will hear more innovatives and implementations of requests put forward by the customers.

Keep up the momentum.

@lafunamor This is only available on the NVR and the HHP. Not yet available on the application itself.

@kimchigun Could be. Did you report it?

@mooglestiltzkin_394766309384342 Being a novice to security that's the way forward. However, I would opt for an NVR rather than a HHP. Higher capacity and at least a 1G eth port. HHP has 100M eth port and this poses limitation on the number of concurrent streams. If you have eight 12M cams then you have already reached the limit. Personally they should have released the HHP with a 1G eth port.

He might opt to use third party applications like Frigate, BI, etc provided that the cameras can stream in ONVIF (which batteries cannot provide unless connected to the HHP).

@user_933469458169984_933469458169984 Opt for Altas PT ultra but ensure they provide the 12W solar panel. It offers continuous recording and auto tracking.

Have a look at the comparison Excel workbook created by moderator at reddit.

https://www.reddit.com/r/reolinkcam/comments/z6caqk/reolink_specs_comparison_charts/

@rainman Never heard this whistling on any of my Reolink cameras or came across someone complaining of similar noise. I suggest you to open a ticket with support.

If you cover the mic with a tape, would you still hear the same sound? Did you try to reset the camera?

@user_732475412443337_732475412443337 Agree. Have been requested by a number of customers.