Best posts made by joseph_1979

@reolink-daisy Thanks for keeping us updated. Indeed it does need improvements. See my comments on this firmware. Basically three points.

1. Colours washed out
2. fps and bitrate reduced
3. Degradation in WIFI - There is now a 2 to 3s delay to establish communication as compared to previous version. Moreover we only see 1 bar even though it is 2m away from router.

The Reolink Home Hub Pro is a smart home device designed to integrate with various Reolink products, enhancing home security and management. Here’s a concise report covering its key features, benefits, limitations and recommendations for improvement.

Key Features:

1. Central Hub: Acts as a centralized control unit for Reolink cameras and devices, allowing users to manage them through a single interface.
2. Video Recording: Supports local storage and can record footage from connected cameras, typically using an external hard drive or SD card.
3. 4K Ultra HD Resolution: Supports 4K resolution for compatible cameras, delivering crystal-clear video quality for detailed monitoring.
4. Remote Access: Users can access live video feeds and recorded footage remotely via the Reolink app, available for both iOS and Android.
5. Two-Way Audio: Enables communication with visitors or intruders through connected cameras with a built-in microphone and speaker.
6. Smart Integrations: Compatible with various smart home ecosystems and can be integrated with voice assistants for hands-free control. Works with Alexa and Google Assistant.
7. User-Friendly Interface: Simplified setup process and intuitive app design make it accessible for all users.
8. HB with connected cams: At regular intervals, it checks the communication between the HHP and the connected cameras. If there is no acknowledgement, the HHP informs the user through an email or push message notification.
9. Security: Offers enhanced privacy and security by keeping data offline and the stored videos are encrypted with AES128.
10. WIFI/LAN: Connectivity is either through LAN or WIFI or both. Supports WIFI 6.
11. Expandable System: Supports up to 12 plug-in cameras (POE and dc powered WIFI) and 12 battery operated cameras, making it suitable for both small and large properties.
12. Ease of Use: The setup process is straightforward, with the Reolink App guiding users through each step. The interface is intuitive, making it easy to manage cameras and review footage.
13. Reliability: The device operates consistently, with minimal downtime or connectivity issues. Local storage ensures uninterrupted recording, even during internet outages.

Benefits:

1. Enhanced Security: Centralizes control over multiple surveillance devices, making it easier to monitor security.
2. Convenience: Users can manage their home security setup from anywhere, providing peace of mind.
3. Cost-Effective: By managing multiple devices through one hub, users may save on equipment costs and streamline their security setup.

Recommendations for improvements:

1. Improve Firmware Update Process: Ensure updates are more reliable and provide clear instructions for troubleshooting failed updates. HHP should check the firmware of the connected cameras and report to the user of any new firmware. This shall apply to ALL cameras including battery operated.
2. Enhance Connectivity: Address intermittent connectivity issues with better hardware and software optimization. Perhaps measuring the RSSI of the signal transmitted by each WIFI camera. Better communication establishment protocol with battery cameras.
3. Optimize Mobile App: Improve the performance and user interface of the Reolink mobile application. Faster loading times and smoother navigation. Sometimes the voice becomes choppy when changing to clear mode and using H.265 codec.
4. Add Battery Backup: Include a built-in battery to ensure functionality during power outages.
5. Expand RAID Options: Offer more advanced RAID configurations for better storage efficiency and performance.
6. Synch of recorded videos: Synchronizing of files stored on the SD and the HHP. HHP should align with the files stored on the SD.
7. Deletion of videos: Allow the deletion of video clips stored on the HHP. These videos should be marked as non-transferable from the SD.
8. Different ring tone: Allow different ring tone for each camera and object detection.
9. Access to HDD: Allow users to have access to HDD to allow them to transfer files more efficiently.
10. Advanced Scene feature: Enhance the scene mode with flexible scheduler and status. Perhaps adding geofencing.
11. Grouping: Add grouping of cameras.
12. Protocols: Adding IFTTT/MQTT to allow users to control cameras according to their needs. Add a correlation event handler which shall alert user when a combination of alarms are triggered..
13. SIP Client: Add a SIP client which shall allow users to call phone numbers when a combination of triggers occur. This shall replace the traditional alarm panel with integrated dialer.
14. IoT: Allow the addition of the standalone Floodlight and smart plug.
15. Diagnostic files: Allow the HHP to download log files from cameras as we used to have in the past on Windows client. Allow the HHP to access the CPU and memory usage and present it to user.
16. Enhance logging: Adding a non-erasure file which shall contain the source ip, account name, time logged, duration and action performed on the HHP.
17. More throughput: Replace the WAN 100M port with 1G port
18. GPS: Adding location tracking just in case it is stolen.
19. Direct Access to Cameras: Allow users to have the possibility to access the cameras directly in a similar way to NVR with the cameras are connected through a switch.
20. Storage capacity: Offer more storage capacity.
21. Analysis of alarms and performance: Enhance the analysis to include the resources usage and alarms per device. Currently alarms for all devices is available.
22. TV interface: Allow user to have control over HHP setting when connected to TV via HDMI.
23. Sharing: Allow user to individually share cameras connected to HHP with certain rights.
24. Enhance AI Capabilities: Further develop AI-based features such as facial recognition, LPR and advanced motion analytics.
25. Transport Protocol: For live streaming, UDP should be used throughout from camera to client as it requires much lower bandwidth and latency. So in case of a user watching a live view on a smartphone connected to the same network of the HHP, we have UDP between camera and HHP and TCP between HHP and client (smartphone). I do not think that the HHP will be able to request the camera to send lost packages. Conversely when viewing a POE or dc powered WIFI cam from an external network we have TCP between camera and HHP and UDP between HHP and client. I do not know if there is adequate buffer at the dc power WIFI camera to allow packet retransmission. By capturing various traces i noticed that during retransmission sound becomes choppy.

By addressing these requests, Reolink could significantly enhance the user experience and reliability of the Home Hub Pro.

Conclusion:

The Reolink Home Hub Pro is a valuable addition for anyone looking to enhance their home security system with a centralized management solution. It offers robust features that cater to both tech-savvy users and those looking for straightforward home security options.

Some Photos:

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

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

@user_651490629161069_651490629161069 Totally agreed. I have proposed sound detection (AI - with user recorded sounds) for some time now and I am hoping that one day we will see it implemented. I did even proposed other detection types such as fire detection, facial detection and recognition, number plate recognition, glass breaking, crying, package, etc. Moreover this can be enhanced by having VOIP calling to a list of numbers.

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

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

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

@tom_649276670137414 They should add geofencing to the scene mode which should automatically alarm/disalarm the cameras once you exit/enter the house.

@user_603674336231435_603674336231435 Maybe shortly we shall have a new client and check this out. Perhaps by that time we get acquainted by the 1:1 aspect ratio :).

@johnny2064_368119747915946 Agree. We did suggest this in a survey on shortcuts (previously named scene mode). I suggest you to submit your proposals to support on support @ reolink . Com

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