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).
@arestis_676622578688071 Point 1: Unfortunately none of the Reolink products are able to perform update automatically. Recently they have introduced this auto upgrade on their Windows client and when I tried it it failed. I had to upgrade it manually. I guess they have sorted it out.Point 2: Have you upgraded the client to 8.8.5? Are you able to connect through the iPhone using both WIFI and Mobile packet data?Point 3: I did request this too. It would be very handy especially if you have a number of cameras. Point 4: We have requested Reolink to add STATUS and a schedule for the scene mode. We have also requested the Geofencing but I didn't see any feedback from Reolink if and when this shall be implemented.
@user_831986059370713_831986059370713 Try to email support on support(@)reolink(.)com. Maybe they will help you on how to source a white doorbell. If you are not in a hurry I will wait for the new one which shall be released shortly. It shall include package detection and have a wider vertical FOV.
@brett-hyink_464759829713142 I have no issue to view my cameras through my 4Gand 5G smartphones. It not only depends on Reolink but there is also the WIFI at home, the copper or fibre path from home to the BB service provider, routing within its IP Core backbone, the interconnect from this ISP to the mobile operator IP backbone, from the mobile operator IP backbone to its Packet core (MME, SGW, PGW), from its Packet core to its Radio network and from the Radio network to your smartphone.
@ron-morgenstern_794924005208288 When it comes to the transformer you need yo know the VA, that is the voltage x current. You need to know the current provided at that voltage. So if the secondary voltage is 24V and the VA rating is 24VA then the current supplied is 1A. But if it is 24V and 12VA then the max current is 0.5A. Moreover 200feet is a bit long and so you need wire with lower AWG (thicker wire) so the voltage drop is low.
@seb_526812765704330 I have informed them too. If I have the source code ( I program in C++) I will also add the schedule when it is triggered by motion or cameras. few lines of coding..... It doesn't make sense to switch on the floodlight at daylight.
@latez1_702748087968371 I am a customer like you and if I had to design it then I would certainly ping the gateway as most devices do.
@legoguy_24916305373 I fully agree with your analysis and this is what I concluded. Note that I am not an employee of Reolink but a customer like you and assisting members of the community based on my engineering/software skills. Would you be able to collect event logs from Windows or any logs which might be of interest for Reolink to investigate and sort out the issue with their client? Perhaps if you record a video it will help them. Then email Reolink support.
@vigy_591093180735512 Not yet available. You need to connect the NVR, POE switch and BB router to the UPS.
@seb_526812765704330 Correct. It was working fine on a previous version but now whenever you click on the notification it will take you to the live view. They need to fix it.
@reolink-daisy Time to have the Home Hub Pro with more cams, more storage and more features.
@viswa_660432243101703 Maybe they carried out maintenance on their servers. I have already suggested that they should somehow inform the clients about planned maintenance. I had an issue with push message notification and I did a trace and noticed that the alert was being sent by the cameras but there was no push notification sent by their application servers towards google FCM. They said that they will alert the customers of such maintenance.
@vogel_284858079064306 check this out https://www.reddit.com/r/reolinkcam/comments/kn53d0/network_cable_wiring_question/
@ed_682671253913811 From the error code I knew what was the issue. Note that I am not an employee of Reolink but a customer like you :). I am here to give my support based on my engineering and software skills...give me thumb up so I will have a Christmas gift....ha ha ha joking.Good to know you are now streaming.... if you have a nice stream...share it here.
@user_681852094591212_681852094591212 I did request this to support and suggest you to submit your request too.
@ed_682671253913811 So the peer is receiving the RTSP request but refusing connectivity. Ensure you have the RTSP enable. Go to the PC Client>>Network settings>>Advanced>>Network Ports to enable the RTSP ports. Ensure you have the latest firmware installed. I would still email support to check whether you have the latest one. sometimes the ones shown in the download center are not the latest. Of course the credentials are never dumped in logs.Previously there was the possibility to see (netstat) which ports are open by exporting the diagnostic log but this has been removed.
@big_ted yeah...I didn't check the specs as I was handling a call.
@user_688413853466839_688413853466839 Toggle again VPN and add exception to Reolink appl.And ensure you are on 4G/5G and try to lower the resolution. Avoid HSPA.
@blackhatcon_440478845636849 You're a good spotter ...:)
@big_ted Indeed. This 64 bit client brought lots of issues to Reolink customers especially those who are not technicals. I am running the 8.10.3 and have forwarded my complaints to support but their reply was not what I was expecting. Hope there will be improvements.You needed to add the cameras because when you updated the client, the configuration has been moved to the 64bit client.
@user_mhm_789920451715266 Most probably your router is non-POE. So you need a POE adapter (e.g. Unifi U-POE-af) with input being the AC power and the RJ45 cable coming from the router. The output shall be the POE which is connected to your CX810.
Welcome Back!
Hi there! Join the Commnunity to get all the latest news, tips and more!