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

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

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 the past I recall that Reolink have exposed the shutter speed/gain but these are no longer available. These have now been removed as indicated below.

         "ispExposureMode" : {
           "permit" : 0,
           "ver" : 0
         },
 


Would Reolink consider to re-introduce them?

In addition we are only able to adjust the brightness of the spotlight but not of the IR. We did ask for a schedule for these functions but so far no feedback. This is a simple software timer. Include it as part of the state machine. Very simple to implement.

Question: Is Reolink abandoning the Windows/Mac clients and focusing on Android/IoS?

@cle_911680035188990 I agree that the title is misleading. It should read... some advantages of having a HH with battery cams.

Opt for high endurance SD.

@user_918371380109526_918371380109526 Normally it refers to the device. I do not see any issue if you use the 33ft 20awg extension cable. I have a battery camera with the solar panel connected to an extension cable of 8.5m and it is always fully charged.

@onlooker_890638347890931 I know what is BMS and as stated the charging current is set by the charging cct within the cam. Even though you see it 100% charged, it is not 100%. To prolong the life of lithium batteries, they are normally charged to 80%. No need to delve further.

For all battery cams, there is a delay of say 6 to 10s. Only the PIR and the WIFI ccts are consuming current. Application is in cold state. This is triggered once PIR detects an object ot the WIFI cct detects a preamble message. Battery cams is better than having nothing. For prompt reply one has to opt for POE.

@user_620089981972582_620089981972582 I was 100% sure it was the problem on your WIFI network. So the entity serving your doorbell is not access point but rather a WIFI repeater. Normally we refer to access point if and only if it is connected to the router via ethernet. So you have a repeater connected to an access point. If you are unable to have a cable to the doorbell or to this WIFI repeater (which can be converted to Access Point) then I suggest you to get a long range WIFI repeater such as the TP link RE650V2. I have this WIFI repeater and have no issue with it. This is at the back of my house catering for the garden and I cannot wired it to the central router.

A side note. I wish Reolink add high gain antenna to their WIFI cameras. Most of my cams are WIFI as I hate cables being cleated or passed through plastic trunking. I don't want to do any trenches in the walls.

@user_620089981972582_620089981972582 Good.

@user_766834819485911_766834819485911 J'ai supposé que vous aviez formaté la SD. Vous devez activer l'enregistrement continu via l'enregistrement/le calendrier/l'heure et enregistrer.
Il est recommandé d'utiliser du SD haute endurance. 

Vous pouvez tester la SD en la branchant sur le PC et en exécutant un programme comme H2testw pour la tester.

@onlooker_890638347890931 It is the battery charger that controls the charging current, not the chargers power supply. In most lithium battery powered devices the charger is integrated into the device itself, and using a higher amperage power source has no effect on the charging current whatsoever. Devices where you can set the charging current as you wish, like radio controlled models, but those are in the minority.

@user_620089981972582_620089981972582 Would you be able to get the WIFI doorbell inside and connect it to the router? Use both WIFI and eth connectivity. In this way we eliminate the access point.

@user_620089981972582_620089981972582 Check whether the satellites go out of synch. Is it possible to have distinct SSID for 2.4G and 5G? If yes then connect the doorbell to the 2.4G band. If you have the preference WIFI band then set it to 2.4G and restart cam.

@rainman This is an old problem with FE-P v1. I suggest you to open a ticket with support.