Reolink updates Learn More
Meet Reolink at IFA 2024! Learn More
Reolink Q&A Learn More
Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
@ramms_119 Good to hear that. I have it running on Win 10 and 11 respectively.
@user_617650665832448_617650665832448 Under Push and Email (if used) untag any motion. Just detect person, vehicle and pet. And if there are false alarms on person use the alarm delay under alarm settings.
@rainman Can you list what configuration you have changed from the default value? Can you leave out the detection zone and try again? Just to identity what is causing the issue. Moreover please check that you have the most recent firmware. You can check it in Reolink download center.
@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.
@quizzical In my case the issue was from both mic and as stated the new upgrade did solve the volume. Kindly report it you Reolink support.
@rainman I am not a Reolink employee but supporting members wherever possible based on my engineering skills. It is clear that this has nothing to do with the detection zone and most probable it is a firmware issue. I do not see any further tests and so I suggest you to email Reolink support and include your hardware version and the tests you have conducted. I have no access to logs and they are limited. One last test please....... Can you install Reolink client on another smartphone and re-create the config from scratch for one of the DUOs and check it out? Are you on Android or IoS? If you are on Android there is a limitation on the number of push notifications per application. If I recall correctly this is limited to 24. In case of Android smartphone, when you click on the push notification of the camera through the client, the client registers with Google FCM (it stores the IP of the client) and the client receives a token. Then client forwards this token (you can see it from the system menu of client) to the Reolink application server receiving the push messages from cams. So when there is a person detection the camera sends a message to Reolink application server. This application server already knows the token (passed by client) and sends a trigger message request to Google FCM. This includes the token the client registered with FCM. FCM then uses this token to fetch the mobile profile (IP) and pushes the message to the smartphone. This is high level. It's complicated but that part we leave it to the troubleshooters :).
@alvaro2 It also depends on the power output of the router. I have an Argus 3 Pro on 5G and it is at least 17m away from router. I do not have any connectivity issue . That's expected from plastic when exposed to long hours of direct sunlight. I did install an aluminium cover on top of the camera and so far still in original colour.
@seb_526812765704330 I think 5 chimes to a single doorbell. Please check chimes availability on the site.
@rainman Then you are running on Android 13. Try the last test I proposed. Even though the download center shows your firmware, do email them as they might have never firmware which they haven't yet released. Normally they shall reply within 48 hours.
@rob_631717169750022 I did ask senior support to have it even on single view. Didn't get any reply yet.
@aymen_647614801764433 Because it is based on the signal strength. I sort it out by having distinct SSID for 2.4G and 5G and I have set it to the 5G SSID.
@user_667513685061740_667513685061740 And clips should be sent in high definition.
@ramms_119 Yes I noticed this from the instant I upgraded. As you stated it was working really well on previous version. Support notified.
@seb_526812765704330 According to its specs, it provides 25W per port and this is more than adequate to power up the entities you have stated above. It also supports both IEEE 802.3 af/at interfaces. From your list only floodlight has 'at' interface. Max power consumed by those cam < 12W while the floodlight consumes < 25W.
@guessy_305491556810936 Data transfer capability depends not only on the medium but more specifically on the source processing power which in this case is the camera. It can be seen from your video that the max data transfer is around 1.7MB/s or 13.6Mbps which is not that slow either. I have high end servers HP G10 and when I transfer a 20G file, the transfer rate is around 40Mbps. The issue I see is that somehow the transfer occasionally stops and this has to be sorted or improved. Maybe in the recent versions they change the mechanism of saving the data to HDD. I did inform Reolink accordingly.
@s-stoessler_71959255531 You are a true honest Brit. As long as they are functioning and deliver what is expected then as you said...they are all superb.
@randy_tidd_166680584470723 Definitely it is on the list of implementation and others are asking for callout rather than a push notification together with using existing chimes. These are three of the most requested features.
@big_ted Actually I encountered this myself and did report it to support. Hopefully it will be added in a Win client upgrade. I am still on 4.35.1.1. Will ask for the beta to test it out.
@christian Hello Mister. Can you please install DirectX 9 and re-install v8.11.0? Let me know if this fixes the issue.
@big_ted Apply marine grease to the bolts :).
Welcome Back!
Hi there! Join the Commnunity to get all the latest news, tips and more!