Best posts made by joseph_1979

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

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

@skeptouchous Please submit your request to Reolink support. I have forwarded this suggestion for quite a long time. I have asked that if the P2P servers fail to receive 10 consecutive packets (at intervals of 20s) then an email or push message notification shall be forwarded to the customer informing that the camera is no longer on-line. The more requests they have the higher the probability of being implemented. At the end it is their decision what to implement.

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

@joseph-chircop_497308027822318 On another note in the playback view, the duration of the recorded video and the progress view bar are missing. These are readily available on the Android version.

@mdunning_323765759099098 This is a known issue and shall be solved in the next release.

@vigy_591093180735512 There are a multitude of security features which can be added. I have passed the following to the Reolink support for consideration.

Having the username/password credential is not enough and I propose the following for your evaluation.

1. Introduce 2FA which definitely provide another layer of security fir cloud account. This has already been implemented in RING, Wyze, etc. Introduce it as an option and let the customer to activate it or not.....This has been implemented.
2. Introduce a log of the source IP logging on to the camera. Have the last 20 IPs together with timestamp logged and exposed them to the customer.
3. Send a push notification or email when user fails to log to the camera. In additional to the account locked feature.
4. Add a read only Audit log which captures all the changes made by the Admin. To include timestamp with each change made.
5. Add the possibility to send a push notification when a user logs the camera. Leave it to the customer to activate/deactivate the feature
6. Add a privacy shutter which inhibits any recording. This must be password protected and administered by the admin.
7. Introduce a heartbeat feature with changeable timings where a push notification or an email is send to the customer at specified regular intervals. Or else have the heartbeat mechanism be implemented with your servers and if this is not received for say 5 consecutive times, a push notification or an email is forwarded to the customer. This will definitely entails to augment the number of servers at your end and so option 1 is more favorable.  
8. Encrypting the mp4 files in the SD (using AES 128/256bits or 3DES) and files can only be viewed from the Android/Ios/Windows applications using the combination of UID and password of the camera. Then if the customer wants to pass this video to police then it can be exported with no protection.
9. Camera to send its IP in an email if it changes. Say camera has been stolen. Both public and private IPs are stored in the P2P servers but definitely you won't disclose it.

WE NEED TO BE PROTECTED

@reolink-fiona In general customers want

1. MQTT implementation
2. Facial Recognition
3. Geofencing
4. Higher fps and higher optic zooming
5. Rich push notifications across all recent cams with embedded action like calling emergency
6. Clicking on received push notification shall direct you straight to the recorded video
7. More detection zones each of which has its own alerts, schedule, siren, notifications, etc
8. Distinct sound at application level depending on source (cam)
9. More AI detections like any Pet, Package, smoke, sound, etc
10. More IoT devices (Smoke detectors, PIR detectors, Sound detectors, water leakage detectors, temperature and humid detectors etc)
11. More complex IFTTT...... if (face==matched or License plate == ABC) then switch off camera 2 and release relay to open gate
12. More security on cameras and applications (logging source IPs, Audit log logging all activities done by a user, encrypting mp4 files on SD, sending an email once a user logs on to camera, Windows/MAC client to be password protected at start up, etc)
13. More efficient and robust communication protocols between cameras and applications (esp wake up method on battery operated cams, playback improvement)
14. More robust applications and firmware
15. More flexible timers (pre and post recording, files retention, guard and patrol timers, etc)
16. Statistics on events, based on recognition...counting and congestion
17. Deleting specific files stored on SD through a function on application
18. SFTP access to the user cloud account
19. Improve ways of how to inform customers about upgrades and maintenance windows which might impact cameras operations.
20. .........you want more :).

@bboy_202565157167353 Today everything is getting complicated. Other features had higher priority but it started to be deployed with floodlight.

@reolink-fiona You're welcome. Please press development team to close the gap with other suppliers. In this forum members come up with wonderful ideas. And of course they are eager to see them implemented and not just written down.

@reolink-fiona Yesterday I upgraded it and so far so good. Hopefully we shall see this feature in the new or following Android client.

@eduardopereiracorreia_314757253894288 I fully agree that it should be back if not as a default at least as an option.

@big_ted This only makes sense if you have a poe cam nvr system. Just add a UPS which feeds the NVR and the fibre ONT or BB router. It will become expensive to have individual UPS which also adds maintenance. Anyhow if you do a search you can find lots of UPS say 12V 14.8W for say 30 bucks.

@reolink-fiona Thanks a lot. Wish you a healthy, peaceful and a very successful 2023. Keep it up and tease the customers with new products. Appreciate if you continuously pester your developmemt team with the suggestions put forward by the members.

@rivera-family_659654519037999 Go to Reolink download center and download the Windows client version 8.8.4 and install it. And then add the devices. Ensure you get the UID and the password of each camera you have installed.

@nad-wolfgang_581208661188791 I already raised this with Reolink and had no feedback.

@g2m-advisors_537747045552377 I already forwarded this suggestion. The only reason I can see is that FTPS is easier to implement. SFTP offers better usability with firewalls as it uses one port while FTPS uses multiple ports. Have been working with lot of equipment from different suppliers and never used the FTPS.

Hopefully one day we shall see SFTP on both cameras and NVRs.

@nacster_1969 This is a community where we share and support each other on issues which we came across. In case of severe issues one has to resort to the supplier who has all the means and tools to delve in your problem privately. For instance I found functional issues with the 8.10.3 and I opened tickets with support and we are working on them.

@user_629911810629744_629911810629744 We have no knowledge of their strategies and prioritisation. On large projects I add resources and do my utmost to complete it before the agreed dates. I would like to see them implement a number of features, features which have been implemented by their competitors for quite some time.

@reolink-fiona Can you please add a link so we will download and test out? As regards security I wish to see more features like the ones I proposed. Thanks for sharing with us.