Posts made by Jose_320595376935068

I would say that "first" page is:

https://support.reolink.com/hc/en-us/categories/360001053634-Firmware-and-User-Manual-Download

And the "second" one:

https://support.reolink.com/hc/en-us/sections/360002374874-Firmware

In that regard, yesterday after updating the iOS Reolink app and connecting to my Argus 2 camera, I saw there was a firmware upgrade for it. As I have automatic upgrading disabled, just to see what it was about I checked those pages, but I have noticed that there is no info at all about Argus series firmware.

Even if the upgrading procedure is not so handmade as in other models, I think the firmware list should include all the information... and be properly sorted by date as well, of course.

Although most of this thread (and the Cynthia explanation above) seems to apply only to cameras with "motion detection through image change" cameras, the "time periods" feature could and should also be applied to battery-powered ones using PIR sensors. If I'm right, in Argus cameras the chosen sensitivity is actually an all or nothing thing. I can schedule when detection runs but it will always do with the same selected value. I'm unable to define different sensitivity values for a chosen time period or moment of the day or set a sentitivity values range (instead of a unique value only) as well proposed above. I would say that more than a feasibility issue it is a matter of UI design. What is undeniable is that we all need a better performance in detection.

I strongly endorse the above comments about the need of some solution for giving AI to current customers. In fact, days ago I had an e-mail exchange with Reolink Support about the problem I'm having with *lots* of false alarms because of bad management of high contrast, sunshine and moving shadows (see attachment with so many alarms around noon time). After all, all my outdoor cameras around my country house face sunshine at one time or another. Support kindly told me that maybe I could wish to consider replacing the Argus series cameras with a newer AI model. However, I have to use battery-powered cameras, and the only AI model I know of is the new Argus 3 Pro, and morevover, although not so many as in Hflorida case, replacing five cameras with less of one year of use is not a cheap solution without some trade or discount offer, as jchurchward has proposed.

Argus2_playback-2021-01-30.png

I have purchased (from amazon.es) one of these to extend the power cable of my (white) Huawei router: https://www.amazon.com/Liwinting-Extension-Connector-Adapter-Monitors/dp/B073V3RLV5/. As far as I can see there are a lot of similar extension cables to choose from.

For what is worth, this is an excellent suggestion. Any chance to get it also in battery-powered cameras? Currently I'm dealing with a greater than normal number of false alarms because the lower position of the sun at this time of year makes more pronounced moving shadow effects. Then, any tool helping to manage or at least reduce them would be welcome.

As far as I know, there is a new mounting bracket for Argus PT ("Note: There are 2 versions of the white outdoor security mount. And we will ship one of them randomly". https://reolink.com/product/argus-pt/). Although not metal-made, I would say the newer one looks a bit more stable. Pity that Reolink is not giving it with ALL new purchases, but randomly alternating between both brackets.

Hello.

I can not speak about the RLC-520 model, but I had similar connection problems with my E1 Zoom cameras and, for what it is worth, they were solved with a firmware update.

Hi, Cynthia, I am very grateful for your reply.

As I wrote, this is not a question for Support team, really. In fact, I have a recent response from Fred telling me about what the problem seems to be (some backwards incompatibility on newer SDKs). My doubt is whether or not are other Mac users facing this same issue since I have not seen comments about it in this forum.

Thanks again.
J.

When I bought the cameras I started using the version 3.5.6.55 of Mac Client (it was in the download page, if I remember correctly), running it on my iMac 24" over OS 10.9.5 (Mavericks). Some weeks after I was advised from Support to check a newer version 8.0.5. Although the download page (/software-and-manual/) says "System requirement: MacOS 10.9 and later" it didn't work so I upgraded my Air to OS 10.11.6 (El Capitan). Well, it worked fine.


Laterly, while checking several camera issues Support told me to test the newer 8.1.18 and 8.1.20 clients, but both of these and some beta in between failed with a black screen just after starting up. I have seen similar notices here and there in this forum, but they seem related to Windows version only. The issue is right now in a Support ticket so my question is rather addressed to other Mac users: given that Mac Client 8.1.20 is already a public release, am I the only one facing this black screen problem? What OS version are you using to run Reolink Mac Client?


Thanks,
J.

Cleaning the spam manually may be a never-ending Sisyphus task. See the https://reolink.com/topic/how-to-add-a-youtube-video-here/page/3/ thread, for example. You may also wish to consider closing the writing to the forum, except for true Reolink users...

As a newcomer to Reolink cameras (but not to computing or imaging fields) I'm reading most of the info I can find about it. So I have reached an interesting article about "7 signs that remind you to upgrade your outdated security camera system". Among these worrying signs there are two to be highlighted:

#5. Use Traditional Wired Technology: "With the rapidly-advancing technology, there are 100% truly wire-free security cameras even for outdoor use which adopts long-lasting batteries".

Great!, I have bought four Reolink battery-powered cameras just for that reason. But wait, shockingly enough...

#2. No Remote Viewing via Web Browser: "But if you can only remotely visit your security camera via mobile phone, your security system is a little out of style. More and more security cameras can now be easily accessed on web browsers."

Oh, my God... then my new cameras recently bought are already OUTDATED BY DEFAULT, even fresh off the factory floor!

Seriously now, when will we have web access and FTP uploading in our battery-powered cameras? And, please, no, the battery power is not a valid excuse anymore: most of us have solar panels and anyway the energy consumption for those tasks is not higher than for current remote client access and uploading to the cloud, respectively.

Regards,
J.

Alas so, almost forget, the article is there: https://reolink.com/signs-your-security-system-is-outdated/

what is the preferred way for reolink to get bug reports?
A public tracker could avoid reporting known issues.
A public ”feature request collecting and voting system” allows to quantity feedback.

I strongly support that idea. I have reported some bugs and improvement suggestions directly to Support and, beyond the usual and kind word of thanks, there is no real way to know whether or not there are other interested users and the ultimate fate of the proposals.

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

I'm using Argus Eco and PT cameras from a few weeks only, and very strongly agree with that statement. 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.

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.

Escapes 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:

- Define what charging threshold would each "problematic" feature require.
- 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.
- 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).

As Vincent Le Bourlot and other participants have said, it is the users responsibility to manage battery.

I currently have three Reoling cameras (Argus Eco and two E1 Zoom) and a fourth one (Argus PT) is just on its way from Amazon. I'm very pleased with the cameras and I'm looking to cover other spots, so I would be delighted of testing this new Reolink creature.