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

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?

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

@diegosalerno_560796844831021 Good to hear your positivity on the video doorbell. Indeed the issue of low audio at the doorbell side has been identified some weeks ago and this has been resolved by adding the volume control to the speaker. This shall be available in the next Android release 4.35.0.7. As for the different rings, this merely depends on the application and not Android. Android limits the ring type per application. PMN can have embedded in it the type of ring tone. Recall that this is the first generation of video doorbell and we will definitely see new features in the next releases. Customers are asking for SIP calling and able to integrate it with the existing chime. Any additional ideas are more than welcome.

@bruceda_323950257770638 This motion tagging is quite interesting and merit an evaluation...and implementation. Other brands have it.

@Fiona Please forward this request to the development team.

@reolink-fiona Hi Fiona, thanks for the invitation. We will certainly assist the members as much as we can.

@reolink-fiona Thanks for the update. I had a quick glimpse and noted the following.

1. This update will delete all the configurations done on the installed version and one has to start adding the devices from scratch. Developers should have done this transparent to users.
2. Points 1 to 3 are not applicable to the E1 AI Zoom despite it has auto tracking. Maybe there is the need of a firmware upgrade.
3. Pictures in the already defined presets are not loaded.

Update: These seem to arise when upgrading from 8.10beta.

@olive_608518832963622 that's the first implementation of Reolink doorbell. SIP calling will come too hopefully.

@ginny They need to learn to keep the previous downloaded version . Despite the myriads of requests, Reolink should save old versions of applications and firmware at their website or at the community.

@senzo150_417180774088936 Email Reolink support and they shall provide you with the details. Hereunder is what I came across.

@steven_738981743145089 Rich notification is only allowed for doorbell WIFI and this is against a subscription. The preference showed by most members is to have a VOIP callout. Basically Reolink has to deploy SIP application servers which when alerted from the doorbell originates a SIP call to the user smartphone. The ingress to the appl. server shall be a live view from the camera. Users have to set up a VOIP account on Reolink SIP servers.

@shayla Can you please let us know if rich notification will be extended to other cameras? And is there any plans to introduce call outs when the doorbell button is pressed similar to what is being done by your competitors.

@latez1_702748087968371 Good. Absolutely that there is always room for improvements.

@user_741670321848486_741670321848486 Then use v8.11.0 which can be downloaded from https://home-cdn.reolink.us/files/client/electron-release/reolink_setup_8.11.0.exe

@klimavicius-irmantas_350705300095137 It fails to connect from both your smartphone and PC clients? Ensure that the 4G signal is strong as if it handover to 3G you may experience connection failures. Mobile operators tend to change the power of the eNodeB.

@rui-godinho-lopes_709100408737905 Yes but it has to host the COR to provide the header info.

@rui-godinho-lopes_709100408737905 For sure the cameras won't host the cross-origin resource but you may get the confirmation from Reolink suport on https://support.reolink.com/requests/ If this is supported they would have included it in the specs. But try

You need to use the Outbound Nat rule (manual) and assign the IPs. Otherwise try to use the 1:1 NAT as a start.

@rui-godinho-lopes_709100408737905 Is there any specific reason for using Firefox browser to stream from cam? Can you enter with https (assuming you enabled https on camera) and check whether you can watch live and playback?

@dt Try to submit these details to the support on https://support.reolink.com/requests/ Are you running the latest MAC client?

@james-jenner_683177101791235 What is the smartphone through which you cannot access the camera? Did you try to swap SIMs?

In case of the NVR, the videos are stored in the NVR too. If you log onto the NVR then you shall watch the ones stored on it. However, I will try to fix the smartphone issue before I proceed to purchase an NVR and additional cameras.