Posts made by joseph_1979

@user_681852094591212_681852094591212 I did request this to support and suggest you to submit your request too.

@user_694227756134544_694227756134544 Take note of the UID of the NVR. Delete it from the Windows client (click on the NVR in left hand window) and add it again.

@raygoldstein5_307154471190675 I suggest you to submit your request to Reolink support.

@bfeliciano_416958891729142 Good.

@bfeliciano_416958891729142 It's the application and not the camera. No more stretching for 5MP.

@user_768126377545948_768126377545948 I have seen some customers complaining about differences in hue. These are two independent lenses with different light intensity entering each lens. Seems that there is some reflections from the wall. As a test, can you move it a bit to the right. Check that you have the newest firmware (from their Reolink Download Center) and try to synch the brightness using the Windows client.

@mrazik_760743929200783 I suggest you to send your requests on https://support.reolink.com/requests/ so that they get whet the customers are asking for.

@nathan Then better to report it to Reolink support. I am running 8 cameras and have no issues. But cannot say anything if this happens when more cameras are added.

@bill-doria Try to disable the hw acceleration first and check again. I had this issue on older version and I solved it by installing the Directx Redist. But in my case it happened all the times and for both the live and playback. Which version were you running before the update? And which camera models?

@erik-reynaert_338361198649528 Delete the cameras from the left hand side and add them again. All that you need are the credentials since the parameters values are stored in the cameras themselves. Alternatively you should uninstall the current one and install the new version. Indeed Reolink should make this upgrades more transparent to clients, especially to those who are not technical.

@m-lapkovskis_133073381171361 This would drain the battery within a few hours and the charging current is not adequate to keep it functioning 24x7. It takes time to charge the battery. Pixel changes detection is normally available on dc powered or POE cams.

But you may email Reolink Support and propose your suggestion.

@pedrofsilva_762258334912663 I didn't see any updates on the scene mode feature.

@user_760785751838903_760785751838903 This is available on the Windows client v8.14.2.

@user_620735247532084_620735247532084 Agreed. Kindly submit your requests on https://support.reolink.com/requests/

@frankoverip Email support and check if they have a newer firmware.

@s-stoessler_71959255531 Email them.

@john_350143387672724 There is an newer client v8.14.2. I am running this version and so far so good. Motion tagging has been added to the client for both live view and playback in CLEAR mode. I noted that it takes some time for the Motion Mark to appear on the camera menu.

I would have preferred its implementation at source rather than on the client. Though the algo might be the same we still cannot be 100% sure what has caused the trigger (in certain scenarios). But better than nothing :).

@user_752523005767835_752523005767835 I had the issue with 8.14.0 and it was resolved when I have upgraded to 8.14.2. Did you reach Reolink support?

@user_745660696895718_745660696895718 When you are unable to connect, check the WIFI at the location of the camera with your smartphone. To ensure whether it is a WIFI issue, for a day bring the doorbell near your router and check it out.

@user_745660696895718_745660696895718 Check the the WIFI strength is quite good at the location of the doorbell. Install ookla from Playstore on your smartphone and from this location check the upload speed. Note that from the camera perspective it is the upload speed which is important. Is this occuring when you check from the same WIFI as the camera or from another external network?