![]() Reolink can simply reject API calls when battery level is low and stop API calls from the 3rd party software. I don't agree with the two points you mentioned in your previous message.ġ/ Reolink can easily implement some strategies to work with the 3rd party software to manage the battery. ![]() This request needs to be seriously evaluated since Reolink has reached the point and maybe in a better position than competitors. Moreover, there could be an overall, user-defined, threshold for battery warning, although never less than the default, factory defined, one (this would cover the case the user was a long distance away from the camera and would prefer to have some security margin to deal with the issue).Īs Vincent Le Bourlot and other participants have said, it is the users responsibility to manage battery.ĪPI will be an important feature to attract more users and open more applications markets (NOT just security) for Reolink. If the user configures some feature requiring a given battery level and it is likely to fall below the threshold, notify the user that feature will be on hold until battery recharging. Define what charging threshold would each "problematic" feature require. ![]() It looks as the battery-powered cameras were the "poor relation" with respect to the rest of Reolink devices, thus using the charging issue as an excuse to cut some features that actually could be easily implemented but we, users, need: web browser access, "common user" type, motion detection area (!!!), saving to FTP server (!!!) or privacy mask, to say the most obvious ones for me.Įscapes me what most of these have to do with battery level but, anyway, if the phone and PC applications are able to know the battery status and whether the camera is connected to a power source (solar panel or other), I don't see what problem would be to implement something as simple as: Reolink people should be aware that we have not chosen these models by whim, but because the required position of the camera doesn't make possible a plug or a POE, but this should not imply such cutting of many basic features whose relationship with the battery is not clear, and moreover when most, if not all, of battery-power users have solar panels as well. I'm using Argus Eco and PT cameras from a few weeks only, and very strongly agree with that statement. ONVIF port: access via third-party software.Second, isn't it the users responsibility to manage battery life, and not yours by restricting access? For instance, my argus 2s are plugged to a solar panel and constantly at max charge during the day, it's a shame I can't access it via web browser. RTSP port: watch a live stream on the VLC player. HTTP & HTTPS port: access via a web browser (the latter port is more secure than the former one). Server port: access via Reolink Client or Reolink App. Please note that E1/Lumus does not support HTTP/HTTPS/RMTP/RSTP/ONVIF connection, E1 Pro does not support HTTP/HTTPS/RMTP ports. Specifically, there are the following six types of ports for almost all the Reolink WiFi and PoE cameras. Refer to How to Forward Ports in Router Interface for Reolink Products for help. When remotely accessing your camera by using IP, you need to forward different ports in the router interface for different access forms. So you don't need to forward ports on the router, but the router needs to allow connection via any UDP ports. When remotely accessing your camera by using UID, there are no designed ports for it, as the camera uses random UDP ports. Remote access can be divided into UID access and IP access. And it also mentions the information about how to allow your camera to go through the firewall, so you can access it remotely.Īpplies to: All Reolink products except battery-powered ones This article shows you all the ports of Reolink cameras and NVRs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |