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

@seb_526812765704330 We have requested the scene mode to have both a scheduler and a status. Moreover to be enhanced we asked for geofencing which shall toggle (if selected) the activation/deactivation of the scene mode automatically once we arrive or leave the premises.

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.

@luuke_869320929738914 Detection algorithm was not able to determine the exact object type. Can you send the video to support on support @ reolink . Com so that they will improve the algorithm.

@alan_909533752111327 Are you using the Windows client? Did you try to uninstall and re-install the client? Do you have another PC where you can run the client?

@reolink-oskar This all boils down to costs. One of the key advantages of full colour night vision technology is that it offers clear and vivid colour images, even in near complete darkness say as low as 0.0005 lux. This is made possible by having a massive 1/1.2'' CMOS image sensor to capture more light, as well as a warm light that reaches up to 200ft. The technology has come a long way in recent years and continues to improve, making it a popular choice for cameras. There are also a couple different technologies to achieve full color. Some of the more affordable full color cameras use a built in warm light that can go as far as 100ft. More advanced cameras utilize two lenses. One lens captures visible light and the other captures infrared, both are then combined with clever programming to achieve a multi-spectral image. This means that with the same 100ft warm light, you can see even further in the dark.

Another technology is thermal imaging technology which captures the temperature difference between objects. They use microbolometers to detect different amounts of infrared light which are then converted to images of heat signatures. Since these cameras can identify heat patterns, they can see even in zero light and when there’s smoke present. So thermal night vision cameras are very useful for security where visual clarity is important regardless of the lighting condition.

@flynn74 There isn't this option. However, you may submit your request to support on support @ reolink . com for re-consideration.

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

@reolink-oskar WIFI 6 is fast but only if you have a number of devices connected to. If your current router is fairly new, isn’t giving you any issues, and you are happy with it, then it’s certainly best to keep it for now and upgrade when the time is right. However, if you haven’t upgraded your router in a while, your WiFi is slowing to a crawl, and you keep adding more connected devices, then you may consider a WiFi 6e router to help future proof your home. Now we have WIFI 6e and shortly WIFI 7. WIFI 6 makes use another band, the 6G. This is by far better than the WIFI 6. The higher the frequency the lower the wavelength and so the less will be the range.

But if we look at the camera side we see that the bandwidth required is merely 10Mbps for 8MP. So why all this bandwidth when just 10Mbps is required. Is it a hype? Might as well change the eth port of the cam from 100M to 1G or 10G :).

@reolink-oskar Yeah, a poe Argus 4 Pro.

A remark on the mounting. The mounting is similar to RLC-511WA, RLC-811WA, etc and it can easily be pushed downwards. Not tight at all. It has to be locked.

@boomish_893913578897601 Uh patience is a key to success in your life.

So if you are connected to the same subnet, they should be fast to access esp POE cams and WIFI mains powered cam. For battery there is a delay since only the PIR and the WIFI reception ccts are only active. Try to connect the camera directly to the router and check it out. If fast then there is something wrong in your network.

On mobile you need to be on 4G/5G as 3G (HSPA) offers much less bandwidth (unless the mobile operator provides HSPA+ but most operators are decommissioning 3G to provide more spectrum for the 5G). Mobile technology is nice to work in esp with the proliferation of IMS. And it is fun when there are issues on such network and you have all the probes to capture traces and analyse.

@crimp-on_62210811129 We have a phrase but cannot write it as I will be banned. So simple....few seconds to add it to release history. We are in 2025. So imagine if the code is not commented. The outcome is instability if more than one is working on it.

My colleague has TAPO and when there is a new fw the client prompts a window informing him whether to update or not. And this is from the Android client. This can easily be implemented by letting the client check for newer fw say once every week...in the background. This is all software. No Phd is needed.

I have an RLC811WA and I observed that when there are tcp retransmission packets the audio stops and you see frames freeze when viewing in clear mode. I told them that in video and audio the norm is to use UDP even on local networks.. For this you see that the bit rate shown on the Android client varies. I think they need to revise the network services on this camera. I have a Trackmix a few meters away and it works better. Compared to the RLC511WA, the RLC811WA has lower vertical FOV. It seems that newer cameras have lower vertical FOV. I dont think it is a sensor issue. Moreover the clip magnifier on the RLC811WA doesn't work on any client. I told them but has never been fixed.

@user_672936957612150_672936957612150 From the description appearing on the screen this is not a repeater but rather an access point. It states to connect it to the ethernet port of the NVR. I do not think Reolink will make any access points or repeaters as it will never match those available on the market. This simple tells you how to extend the WIFI signal using any access point.

It shall use same credentials as the host.

Eh he....you posted it on Reddit too...and Facebook didn't see it.