Posts made by joseph_1979

@reolink-fiona I am aware of this. We need a list so we can check who has accessed the camera. And it should be read only abd cannot be modified or deleted not even by the admin.

Can you ask the appl dev team to try to add the logging of the remote IP together with the timestamp in a list which the customer can check? A list of the last 20 accesses shall suffice.

Customers may be too much hectic in their routine and sometimes forget to check their cameras. There may be instances where the camera fails for one reason or another or it may be stolen and when it is really required then evidence is not available. Can you devise a heart beat mechanism between the camera and your host server and if the camera misses say 5 heart beats then a message/email will be sent to the customer? A lot of equipment employs such mechanism like for example IP PBX which sends the OPTIONS message and the peer server replies with 200 OK or 403 Forbidden. If there is no reply then this means that the SIP trunk is out of order. Think of it.....maybe you will be one of the first to introduce.

@chuck_529633235447953 It's off. To be honest in my case it didn't have any impact whatsoever on both smartphones.

I already have argus and RLC511WA and I am interested in having the E1 outdoor. This has now been released since April of last year and I guess most of the issues have been resolved (I hope).

Any users who still have complaints on the E1 outdoor?

I am still doubtful whether the camera can withstand harsh environment like being exposed to Sun for 6 hours with temperature reaching 40 degrees. Is the detection quite effective as the one employed on RLC511WA? Does the camera return to its original position after motion has been detected?

@joseph-chircop_497308027822318 typing error............. 4.29.0.X and not 4.20.0.X

@joseph-chircop_497308027822318 And in the 4.30.0.5, clicking the push notification icon on the smartphone will just open the Reolink application and playback with not start. And it is not even able to identify to which camera the notification has been generated from. At the same time one should note that the playback has greatly improved and hopefully this will give a relief to most customers who have been complaining since the first upgrade in the series 4.20.0.X. These were the worst updates which spoilt the reputation of Reolink.

@faasio82_480971996033257 You should have first changed the camera password and then the WIFI. Most probably resetting the camera will not erase the WIFI setting but any other setting will be set to its default value. So you need to start afresh.

@reolink-fiona I am not getting the email to access the 4.30.0.6. Can you share what has been corrected, changed or added in this version compared to the 4.29.0.8? This will let us be focused when conducting testing.

@reolink-fiona Can you extend this to E1 outdoor?

@reolink-fiona It seems that there is no synchronicity whatsoever between your departments. It is available on a French site apktele ...... which is not Reolink at all. It should be provided here so we will test it and provide feedback to your development team. Stability seems to have improved but more and more work is needed to achieve the quality of the competitors. Choppy sound at high def is still there.

@reolink-fiona Can we have the Android application 4.30.0.05 here to test it out?

@neil_chaplin_is_450076909830276 It should be on ver 8.7.3. I have RLC511WA and now it is as it should have been from the start.

@ashall3n_532259310379259. It should be there as indicated below.

@faasio82_480971996033257 4.28.0.8 is the most stable. Depends what cameras you have. If you git Argus then stay on 4.28 version.

Can you let us know when we shall have a stable Android application since the failed updates 4.49.0.X? Hope that this time you have learnt a lesson that before launching a product you need to have adequate testing and passed the necessary quality? Your rating has been fallen on the day with increasing complaints. You are taking too long to solve bugs. You are not consumer oriented at all. We consumer expect a good product for which we have paid.

@reolink-fiona There are issues of push notifications on Argus 2 with the 4.29.0.X updates and still not yet solved. Support tells you to restore the camera and set the PIR and don't touch it again as the problem will crop up again. This answer should be for a few days until a new release is created but not prolonged for over 4 months and the problem is still there. And this is not the only problem. Why it takes too long to preview a recorded video? Sometimes it will load after 10 attempts. I have no issue of bandwidth on neither the Wifi (1GB/300M) nor on the smartphone (165M/48M). There is something wrong in the protocol. And why when I change to clear the sound chops and the video freezes? It is definitely a camera issue either the algorithm or processing power. This is evident on both Argus 2 and RLC511WA.

@reolink-fiona What customers expect is immediate bugs resolution and improved functionalities. Why the support team takes so long to sort out issues? Have a look at the myriads of complaints raised in play store. The same complaints are raised after each update. Other competitors act immediately and so customers confide in them.

Can you let us know when the new stable android client shall be available? Hope that this is rigorously tested before being released and won't bring additional issues as has been the case with most updates. It is frustrating to have security cameras which will no longer be fully functional following a client update. This is unacceptable in security area. A colleague has the TAPO from TP-Link and rarely he complains of an application issue following an upgrade. It is totally seamless as it should be. Giving a cumbersome workaround is not the way forward like restoring the camera and don't deactivate the PIR. If you need to compete you need to hear your customers and improve the entities which are not at the expected level of satisfaction. You are not alone in this market.

@reolink-fiona Issue is still there with 4.29.06. Solution is to rollback to 4.28 version. Whenever the PIR is activated from the application, the schedule is disabled and so nothing is triggered. Default should be activated at all times for all days. Moreover the recording is disabled and so nothing is stored on the SD. This really shows that testing is minimal. You need to invest in more testing as otherwise customers seek other suppliers. In the website please include all previous applications so that customer can rollback.

Note that email notification works. So the issue is with push notification and maybe there need to be changes in your server handling the push notifications.