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

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

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

@ryanoverholtzer_356153850994850 I wish to see this feature too implemented. Yeah they work pretty well on Ring and Wyze.

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

@mrspock75_889662031028381 I don't have the home hub yet and so cannot give a definite answer to your questions. However, you can post this on Reddit Reolink where there are lots of customers using the home hub and will certainly answer you.

@chopstix_887064913674433 you must either enable helper-addresses or UDP forwarding via spanning tree to get the broadcast propagated.

@grod777_275772032561320 It is a base and you can tailor it to your requirements. Their client is not meant to record for 24x7 but rather to configure and have a quick look. For 24x7 you need an NVR or 3rd party application.

I suggest you to submit your request to support on support @ reolink . I am a customer like you.

@mrspock75_889662031028381 Why don't you ask your mobile operator to forward the sms to your other MSISDN. Some operators offer sms to email conversion. So apart from the sms you receive an email.

I suggest you to submit your request to support on support @ reolink . Com

@sibedad I have several cams from Reolink and never had any major issue. Wherever possible avoid battery cams. But it is better than nothing.

@vodkan_410792752525441 If the PIR is disabled then it shouldn't record or send push motification. This is what I have on all my Argus 3 and Argus 4 cams.

@chopstix_887064913674433 So if the client is on 172.20.1.x/24 then the dynamic broadcast shall be 172.20.1.255 and you need to program the router to broadcast it through other subnets. Normally this is not done and so the client won't receive the packet with payload aaaa0000, UID, IP, etc. Then it will do a DNS query for P2PX servers etc....as I described in the para I have mentioned in my previous correspondence.

Wireshark is quite good. Protocols are fun especially when there are issue in a network where a number of protocols are involved, Telecom, networking and IMS. I am a senior technical Architect handling such networks and in my free time a programmer using C++. Have good knowledge of SQP (using Oracle, sybase, etc), python, Assembly language, etc ......

@chopstix_887064913674433 You may wish to read what I wrote in June 23 at https://community.reolink.com/topic/87/how-does-the-reolink-uid-actually-work?post_id=22657&_=1734789769689

So the client broadcast the packet with payload on 255.255.255.255 and 192.168.1.255 repectively (assuming cams are on 192.168.1.0/24. Now 255.255.255.255 and 192.168.1.255 have identical effect if there are no subnets in the network. However, there is a difference when you have broken down your network into subnets. 255.255.255.255 (called as 'Limited-Broadcast') is used by a host to broadcast to all of its immediate neighbors i.e. all those interfaces on the local subnet. Whereas, you would use 192.168.1.255 (called as 'Directed-Broadcast') to broadcast to all the interfaces on the entire LAN or WAN. In this case the router has to be configure to broadcast to all subnets when receiving a broadcast on 192.168.1.255. Also, 255.255.255.255 is used by a node to broadcast on subnet if it doesn't know about its network (or simply prior to it IP configuration) and is requesting for its dynamic IP from a DHCP server. Refer to 'RFC 919' for more details.

You sound to be technical and will ask Oskar whether he can nominate you as a global moderator to assist customers.

@cabin_850248283140282 you can opt to use your WIFI rather than that of the NVR. If you don't have this feature then upgrade its firmware.

Geofencing is not available on Reolink cameras but they have the scene mode. Again this has no schedule and status. Have been asking for it for 2 years.

The client is normally used for setup and a quick look at the ecosystem. Best approach is to integrate the system with HA, Frigate, etc. Where you have more control and features.

And finally I suggest you to submit your requests to support on support @ reolink . Com.

@grod777_275772032561320 so far this cannot be done. You need to write a script to delete old files and use a scheduler to run it every x days. It's easy.