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

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

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

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?

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

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

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

@terryjensen_510712816316578 I do not think there is a solution now. Previous Windows clients had an option to disable it but in the recent upgrades this feature has been removed. I have notified support to re-introduce it and its up to the customer if the camera drains the battery.

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

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

@brad_532657611677883 No need to have internet for the setup I proposed. The NAS shall be connected to the on-site switch.

Moreover I cannot say with certainty that you can extend the HDD of the NVR as I have no knowledge of its specific design. They might be using proprietary protocols in which case.......forget it. Have you tried to email Reolink support?

If there is no way to get broadband on site then the other option is to have a 4G router and use FTP. So how come they know that something went wrong when there is no way to communicate remotely with the NVR? No SNMP traps. I did requested Reolink to implement SNMP on the NVR but didn't hear anything.

@brad_532657611677883 Just add a cheap NAS and install an FTP server on it. And connect the NVR and the NAS to a switch.

@paul_201485632876727 Depends on HW version. Go to Reolink download center and check out the latest stable firmware.

@crimp-on_62210811129 Not always. You may directly use a public DNS such as google 8.8.8.8. The default gateway would mean that the DNS query will be forwarded to the ISP. For instance to get the A record for the p2p8 Reolink server from the google DNS server, in Windows cmd enter nslookup --dns-ip=8.8.8.8 p2p8.reolink.com Once the client receives the A record it will query each P2P server for each camera (connected ones) to get what? Guess :).

@campbell_99 I can understand you but it's their strategy. But as long as you can find it shouldn't be an issue.

@brad_532657611677883 Why don't you use the FTP service on the NVR?

@hometheater503_202558512976108 Normally data can be shared on SD but the application normally resides on the internal mem. Anyhow it works for you ........... If you need the details to the byte level of the mobile messages exchanged with both the packet and circuit switch core then I can teach you....ha ha ha....Even VOLTE which requires the IMS core. Have a nice day.

@saf3_480263206457537 Which version of Windows client are you running? I am running the latest 8.8.4 and cannot reproduce your scenario. So you must have something related to your environment.

@user_645880601444421_645880601444421 I have been running both the 8.10beta and the 8.8.4 without the issues you raised in points 1 to 3. Point 4 is an issue which they need to correct. Yes, the upgrade doesn't work on neither the camera nor the application. I have raised this with support but didn't get a valid answer. I think that this may overload the servers where the firmware and application reside. I also proposed to at least prompt the user with a pop up informing him/her that there is a newer version.

Hope that this will be implemented.

@ermaconsolini_619748074721328 just add it to crontab.