Posts made by Gary D._344027431432324

Hi

Although not so pretty, I also found this type of chime can be paired and works with the Reolink Doorbell, ebay Item 124027726492 - sorry, it wouldn't allow me to post a link.

Hope it helps!

I've had the doorbell for a few weeks now with the Android app, I would agree with the above comments that currently on my phones there is only one type of push notification whether it's a visitor pushing the doorbell button or clouds passing on another camera, which are mostly ignored anyway. A visitor pushing the doorbell button definitely needs to be a separate notification so the phone can be set to play a different sound so it would get immediate attention, ideally with a jump to the doorbell video.
Thanks!

@gary-d_344027431432324 Previous clients were 32bit and the 8.10.x clients are 64bit. Therefore to run them you need a 64bit Win OS.

That is disappointing, it's a shame development can't build a 32-bit version for those who need it, but thank you for confirming. As I have other software and hardware which only work on the 32-bit OS, I'll stick with v8.8.5 for the moment.

Hi

Good news about the the new Windows client, thank you.
However when I try to install it, I get "64-Bit windows is required", as I'm using 32-bit windows 10 and previous versions worked fine, has 32-bit support been dropped?

Thanks

Hi

I'm currently using v8.5.2 but I think I've had what sounds like the same problem with a number of previous versions.
I see video either live or playback when the application first opens, then after a random amount of time it will show this:-



The little sad face in the top left of the video window appears very briefly then disappears whenever I switch between live or playback, or the mouse pointer moves over the timeline bar. I would assume this icon indicates an internal error of some sort, it would be handy if we could see what the error was so we could report this back to aid diagnosis, even if it was just written out to the console.
This could be my imagination but, it appears it happens more frequently the bigger the main window is, i.e. if it's maximised it happens more than if the window is left at it's initial size.
The only way out of this seems to be to close the application and reopen it.
I am running Windows 10 32-bit with two screens, my cameras and the NVR all have the latest firmware.
Is anyone else having this and is it the same issue previously reported above?

Thanks!

I've also noticed the auto-update within the client doesn't work, I don't think it ever has, I have a theory why. If I run the client from the Windows Command Prompt, when it starts it logs a variety of settings out to the console, then checks for a new version and logs the following:-

Checking for update...
Update for version 8.5.2 is not available (latest version: 8.3.1, downgrade is disallowed).
update-not-available

This suggests to me that wherever it's looking for a new version actually has version 8.3.1, which is older than the versions we have.

Hope it helps someone fix it

Hi

It looks like in the latest Android app version, the value of the detection alarm sensitivity is no longer visible, it's just a slider from "Insensitive" to "Sensitive", I think it was viewable in the previous version or would pop up if you clicked the slider. Would it be possible to add that back into the next version as it was quite useful to compare the effect of different values?

Thank you

Hi

I wasn't going to ask the same question because oyvinder already had, so please consider this to be similar feedback.
Could do with a voting button

Thanks

Hi
I agree a list of changes would be useful but it's nice to see the play/pause button has returned - thank you!
The configuration export does seem to work for me also, I found I have to select a destination folder using the Configuration->Browse button before the export becomes clickable.
Strange that it works for Gsrx38 but the update check still doesn't seem to work for me - "Checking Failed" displayed.
I have had the video go blank once as with the previous versions, but found clicking the new "Refresh" button seems to be bring it back again, maybe a quicker alternative to closing and reopening it.
Thanks

Hi Doc

Thanks for posting that, this was something I had been wondering for a while. I have the RLC520 which also suffers from motion alerts due to light changes and had been wondering if the cameras with person/vehicle detection have the same problem, sounds like they do. I think if we could set a maximum change on the motion detection it might resolve this problem.

Thanks!

Hi Fozzy

I have the RLN8-410 NVR which does allow "User" (non-admin) users to be created, all they can do is view and change their password I think. The only problem I could find with it is although the user can view the cameras on the app, it doesn't seem possible to enable motion alerts.

Hope that helps

Hi Cynthia

This was a problem I also had, if Snaffs had the same problem as me, the problem was the NVR was displaying a resolution beyond what the monitor could display, so displays nothing perhaps with an "out of range" message, so couldn't change the resolution on NVR because I couldn't see what I was doing. In my case I luckily had a second monitor which could display the higher resolution.

Thanks

Hi

It appears the update check in v8.1.28 is not working, for me it shows "Checking Failed" (see attached).
Behind the scenes it appears to be receiving a HTTP 403 (Access Denied) error from the remote server.
This check is also attempted when the application is started and that is also failing.
Also, the retry button doesn't seem to actually retry.

It could be because there is nothing to update to but v8.1.20 does the same thing. I though I'd mention it in case a new version is in the pipeline.

Thanks

CheckingFailed.png

Overall I think the system is good but I also agree with Jose and others that the weakest area is the motion detection and it sounds like quite a few users have the same issues. In my case it depends on the weather conditions e.g.:-
- With static weather it works fine, however on a day which is sunny with patchy cloud, each time a cloud passes in front of the sun the entire scene gets lighter or darker so even if the sensitivity is low, because the entire scene has "changed", an alert is triggered.
- At night it's a different issue, on a clear night, works perfectly, but with light rain blown by the wind, droplets are lit by the light causing momentary flashes of light, similiarly with bugs flying near the camera.
Both these conditions can cause a lot of alerts, I don't need to know that a hundred clouds have passed by so I normally just disable the alerts for that day/night which means I wouldn't be alerted even if there was suspicious activity - not ideal.
I have no idea how good the AI motion detection is, but to be honest I am not too enthusiastic about paying to replace a system I've only just purchased.
If AI can't be added due to hardware constraints, I'm sure it could be improved so am trying to think of suggestions to make the non-AI motion detection work better for us, or is the AI motion detection the solution which R&D came up with for these issues, so not much work will be done to the non-AI systems going forward as it has already been addressed?

Thanks!

Hi Cynthia

Thank you and you're welcome, I think any improvements help both Reolink and us the users, so very happy to do that.
Out of interest, is there a way for a basic user (non-admin) to receive push notifications?

Thanks!

Hi

I use the Reolink Client a lot, if you use "split" (e.g. 2x2 grid) on the live view, the next time you open the application it remembers which camera is in which square of the grid - this is good! It would be handy if the playback tab also did this, so you don't have to drag each camera onto the grid each time you open it, I only have 4 cameras so not a major ordeal but I can imagine if you had 16 that would be pain. It could be an option in the client settings in case some users dont want this to happen.

Thanks

Hi

If possible, I would like to suggest that a basic user has the ability to create scenes in the app which only enable/disable push requests.
As far as I can tell a basic "user" doesn't have the ability to change settings on the NVR, which I agree with, I don't particularly want settings accidentially changed. But this seems to mean a basic user can't receive push notifications as that seems to be a setting on the receiving device even if they are enabled on the NVR, this is a shame as the more users who receive alerts the better from a security point of view.
According to the user guide (p43), it looks like older versions of the NVR firmware had the ability to set different permissions on a user basis e.g. Alarm settings (see attached), but I think this may no longer exist in the latest firmware.
It seems in the app, scenes appear to change slightly different settings, e.g. the email notification is enabling/disabling the setting in the NVR whereas the push notification is changing something in the receiving device (doesn't affect the NVR). Currently a basic user doesn't have the ability to create scenes, in fact the app exits if you attempt to do so, but it would be useful if they could create scenes to just enable/disable push notifications.

Thanks
[My system = RLN8-410/RCL-520]
NVR.png

Hi

On a similiar subject, is there any possibility the RLC-520 camera will be upgraded to include the person/vehicle detection in the future? Or can it be upgraded to be a RLC-520A via firmware update?

Thanks

I've also experienced this, I've got a couple of different machines and it happens mostly on the oldest/slowest machine (Intel Core2 Duo). It tends to happen more in playback mode and seems to happen within a few minutes of opening the first time, sometimes in response to a window event like scrollwheel, mouse click or maximise. Once the video goes blank there doesn't appear to be any way to get it back without closing and reopening the application, it seems to happen less after being opened the second time. Even on this older machine it doesn't seem to happen with the older Reolink Client (v7.2.2.33) which seems to be completely different software.
I haven't noticed it happen on a newer Intel i7 machine, but it could be more to do with the video card of the machine in question.

Hope that helps!