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).
By design, Reolink cameras register their UID with Reolink's cloud service. This is how the Apple and Android apps "find" the cameras. I queried my router "open ports" table and found that all 5 of my Reolink cameras maintain open connections to 54.210.7.156 (Amazon Web Services). My guess is if you block that IP, (1) you will eliminate the security hole, but (2) your Reolink apps will no longer be able to view your cameras when not at home. (That's where ZoneMinder comes in? Or, if you run a VPN, I guess you could use the HTTP/HTTPS capability.)My cameras have the sound turned off. (no help there, sorry)I have no experience with ZoneMinder. The "Hardware Compatibility List" does not include Reolink. I am a bit confused, because that list mentions cameras that are ONVIF compliant. Reolink C1 cameras support RTSP (Real Time Streaming Protocol), which is the example used in the ZoneMinder User Guide. (ONVIF vs. RTSP? Here, you are WAY ahead of me.) When I do a port scan on one of my Reolink cameras (sorry, not a C1) I find HTTP, HTTPS, and Port 554 (rtsp). VLC Media Player streams from my Reolink cameras, so their implementation of RTSP seems to work.The Reolink Windows client reports using port 9000. I have no idea what that's all about.Reolink cameras support FTP, but not FTPD (server). My cameras FTP motion files TO my FTP server just fine.I don't know that any of this is helpful. Good Luck!
I am not an expert, but I do have a couple of questions:1. Is your PC Windows or Mac? (you said the magic word "iPhone")2. When you set up the camera by plugging in an ethernet cable, you said it was working. Did that include finding your WiFi router? And, you tested it by unplugging the ethernet cable, rebooting, and the PC client could still find it?3. Did you "add" the camera by UID or IP address? The smartphone app is intended to connect to the camera by asking the Reolink cloud server, "where is this camera?" and the server knows because the camera has connected to Reolink and said where it lives on the Internet. This may be critical, because one of the things the PC client and the NVR do is broadcast a query on the local subnet asking, "if there are any Reolink cameras out there, please check in."4. When you write, "sent a letter", you mean emailed support@reolink.com?Don't know if any of these questions make sense, or will be helpful.My other question is, "are you SURE that the Reolink NVR will work with battery cameras? (solar power comes under the general heading of "battery.") I may be incorrect, but my sense is that the NVR is designed to continuously collect whatever the camera is viewing. Since battery cameras would run dry in only a day if left on continuously, there is not much point in connecting them to an NVR. I would check that out by directing a question to support@reolink.com.
I have listed this as a request to Reolink for a LONG time. I doubt that programming can do much about clouds or trees moving shadows around, or foliage moving in the wind. They detect how many pixels have changed, and if we lower the sensitivity enough to ignore those events, we'll miss almost everything. I deal with some of this by masking parts of the picture, but have learned to live with it. When the camera changes modes, however, is TOTALLY something the programmer can detect and accommodate. This is just lazy, OR Reolink has to take whatever firmware their supplier produces and the supplier isn't interested.I also find it unfortunate that the cameras which are NOT able to turn off their IR LEDs switch to black and white mode when the LEDs come on, even if there is enough light to record in color. I have an Argus mounted close to a RLC-410WS. I have disabled the LEDs on the Argus and mounted a separate IR illuminator several feet away. This solves the "bugs drawn to the LEDs problem." Since I cannot turn off the LEDs on the 410, I covered them with tape. When the separate IR illuminator turns on, the Argus continues to record in color until the ambient light totally fades, but the 410 switches to black and white when it turns on its own LEDs (that I have covered and aren't doing anything useful). So, exactly same lighting, but Argus is color and 410 is black & white.
I, also, assign static IP addresses to all my Reolink cameras using the DNS table in my router. (I have Netgear, but I am 90% certain that all modern routers have the same ability.) I do not configure the camera itself with a fixed IP. I let the camera use DHCP to ask for an IP, and it always get the IP I want it to have. If, for some reason, I want to change the IP, I have only to update the router table rather than unmount the camera and plug in an ethernet cable.
Since The Argus cameras are designed from the outset to conserve battery life, my guess is the answer is going to come back, "sorry, no". I do not have access to technical information, but I would not be confident that the solar power unit will produce enough energy to keep the camera running constantly all night. As an example, there are lots of solar powered garden lights, where the solar panels are supposed to keep the light running all night. None of them last that long. And, while there may be more than 12 hours of daylight in the summer, there is a lot less daylight in the winter. It also might depend on whether you want the IR illumination at night when it is recording 24/7. That burns considerable battery.Anyway, what an interesting questions. I'll be fascinated to see what Reolink says.
My understanding is "yes, the Reolink devices (cameras, NVR) open IP connections to the Reolink cloud servers." Once a connection is opened "outbound", it is open for return traffic from that IP. Like, when you connect to a web site, that web site can send packets back to you. The unique user name and password are used to look up the connection to a particular UID that is associated with that customer. Port forwarding allows anyone, anywhere to attempt to connect to your cameras. The only thing stopping them is knowing the user name/password for the camera. (Just like they need to know the user name/password for the Reolink app.)I would email the question to "support@reolink.com", rather than asking Community members. We users have opinions, whereas the support staff are usually pretty knowledgeable.People who are "totally paranoid" about security do not register their cameras using UID, and probably do not set up port forwarding. They either do not allow access from outside their LAN, or they set up VPN's to tunnel into their network.
This is a significant difference between the Reolink NVR and Reolink client software for Windows (Mac, too?) The heart of NVR is the PoE connected cameras. The NVR "sees them" because they are directly connected. (Like the NVR's that connected cameras over coax cables) Because people have WiFi and cameras that are not PoE, the NVR broadcasts to find them.The client software allows cameras to be added by IP address. Sort of wish that option had been programmed into the NVR. My guess it's not coming any time soon, or at all.Putting the NVR and cameras in a VLAN is an excellent solution. I just did a quick Google search and was surprised to find how many inexpensive switches support VLAN's. That would have the benefit of isolating the NVR/camera network from the rest of the network, with only the devices you allow through having access. You never mentioned how your two building networks are connected or what kind of switches are deployed.
Could you be more specific about how you "configured the routers" to allow traffic from one sub-net to the other?(I enjoy the minutia of networking, but have not reached any significant degree of expertise.)My naive understanding is that when a device wants to send packets to an IP address that is on the same sub-net, it does an ARP request to get the MAC address of the device. Then, it sends packets directly to that MAC address. When the IP is not on the same sub-net, it sends those packets to the MAC address of the gateway device, which then knows which router port knows where to find that IP. So, your Windows machine says, "I want 192.168.2.x, and sends that packet to 192.168.1.1, which knows where to find 192.168.2.x" If your Windows machine had a sub-net mask of 255.255.0.0, it would say, "192.168.2.x is on my sub-net, so I'll do an ARP request to find its MAC address. Once I get the MAC address, I'll address my packets to it." But, nobody answers the ARP request, because ARP requests don't go across routers.Have you tried setting your Windows machine mask to 255.255.0.0, and you can still communicate with the camera on the other sub-net?Or, have I just displayed horrible ignorance?p.s. I agree that it seems reasonable that people might want to connect their NVR to cameras on a different LAN.
I do not know of any 3rd party apps that will work with Reolink cameras. Have you considered this:Power the Reolink camera with a "Smart Plug". Several companies sell devices that plug into a wall outlet and turn their own outlet "on" and "off" according to schedules or events you set up. The TP-Link Mini WiFi Smart Plug says that you can set up a schedule to turn things on and off. https://www.amazon.com/TP-Link-Occupies-HS105-Wall-Light-Electronic-Component-switches/dp/B01K1JVZOE/ref=sr_1_3?ie=UTF8&qid=1543884955&sr=8-3&keywords=tp-link+smart+plug. The user manual on page 7 talks about setting up schedules for when it turns on and off. TP-Link's "Kasa" system allows you to group plugs into "scenes" and have a bunch of them do things together (like four cameras). They also claim to interface with IFTTT (If This Then That) which might allow you to turn them all on when you leave the house and off when you return.I've glanced at reviews of Smart Plugs and people seem to think some have more or better features in one area or another.I do not own any Smart Plugs (yet), so I have no experience with how they work (or what about them drives people crazy).Anyway, you could try one for under $20 and see if it is useful.
The RLC-410W product page claims it works with Reolink NVR's. (Down at the bottom of the page.) The NVR product page mentions numerous cameras, none of which are WiFi models, but it also says, "etc."I downloaded the NVR User Manual. The zip file includes manuals for several types of NVR's. On page 23 of the PoE manual, it says the NVR can detect cameras connected to the NVR's PoE ports and also cameras connected to the same router sub-net as the NVR.So, my guess is "yes". Before making an order, I would email "support@reolink.com" with your question. They answer pretty quickly and seem to know their products.
That is so cool. Thanks for explaining. Sorry that you bought a product that doesn't work for this purpose. Reolink sells solid hardware at an attractive price. Software development is not their strong suit. Good luck finding what other ski sites use.
What an interesting project. We used to put some outdoor cameras on our website so all the employees who had no windows could see what was going on outside (weather, foot traffic, etc.) Of course, our web server and the cameras were on the same internal network. My guess is that your web server is "hosted" somewhere. Reliance on Flash is one of Reolink's major obstacles to overcome, and they don't seem to be making any progress in that direction.I was wondering what the purpose of having a camera stream on a corporate website is. Don't see many with that.
I'm a bit confused. Question 2 seems to indicate that you know the answer to question 1. Please forgive me if this response is not what you are asking for.Reolink Windows client 7.2.2.20. Click on the Gear Icon in the upper right corner (see attachment GearIcon). This opens a box with two tabs. Tab 1 has locations for the Capture and Download files. (see attachment Box1). Tab 2 has location for the Recordings. (see attachment Box 2). In the middle of Box 2 is a selection to open up a typical Reolink "schedule" panel. (see attachment Box3).In my case, I left these disk locations set to the defaults (C:Capture, C:DownloadFile, C:RecordFile) I do not typically use these functions because I use FTP to transfer recordings directly from my cameras to an FTP server and then use VLC Media Player to look through them later. (I also have a Windows script that runs every night to delete files that are "too short" to be of any use.)Just to experiment, I opened the Reolink client, which opened my three cameras, and I clicked on the "Capture" icon in the lower left. Sure enough, three pictures appeared in C:Capture with titles like "Preview_camera-name_date.... Then, I clicked on the movie camera icon and saw the red recording icon appear in each window. Sure enough, inside C:RecordFile, there appeared a folder "11162018", and inside that folder are three mp4 files, one for each camera.I believe when the viewing window is in "Playback Mode", the "capture" icon inside each camera window takes a snapshot of whatever recording is being viewed. The floppy disk icon brings up a list of all of the motion recordings for the day. Selecting them causes them to be copied to C:DownloadFile.That's question 1 the way I understand it.Question 2 is more difficult. Maybe you are looking at a different folder than the one defined. Sometimes I get annoyed with Windows Folders when I change something and it doesn't look like it "happened." Then I have to "View... Refresh" to update the screen. Maybe the folder with today's date is there and will appear if you close the C:RecordFile and reopen it.I waited a couple of hours before responding, hoping that someone who "knows things" would have the answer. Sorry if my contribution isn't helpful.The Download folder is used to copy entire motion files to the hard drive. Clicking on the Gear-Icon-1.jpgBox1-1.jpgBox2-1.jpgBox3-1.jpg
I'm a bit confused. Question 2 seems to indicate that you know the answer to question 1. Please forgive me if this response is not what you are asking for.Reolink Windows client 7.2.2.20. Click on the Gear Icon in the upper right corner (see attachment GearIcon). This opens a box with two tabs. Tab 1 has locations for the Capture and Download files. (see attachment Box1). Tab 2 has location for the Recordings. (see attachment Box 2). In the middle of Box 2 is a selection to open up a typical Reolink "schedule" panel. (see attachment Box3).In my case, I left these disk locations set to the defaults (C:Capture, C:DownloadFile, C:RecordFile) I do not typically use these functions because I use FTP to transfer recordings directly from my cameras to an FTP server and then use VLC Media Player to look through them later. (I also have a Windows script that runs every night to delete files that are "too short" to be of any use.)Just to experiment, I opened the Reolink client, which opened my three cameras, and I clicked on the "Capture" icon in the lower left. Sure enough, three pictures appeared in C:Capture with titles like "Preview_camera-name_date.... Then, I clicked on the movie camera icon and saw the red recording icon appear in each window. Sure enough, inside C:RecordFile, there appeared a folder "11162018", and inside that folder are three mp4 files, one for each camera.I believe when the viewing window is in "Playback Mode", the "capture" icon inside each camera window takes a snapshot of whatever recording is being viewed. The floppy disk icon brings up a list of all of the motion recordings for the day. Selecting them causes them to be copied to C:DownloadFile.That's question 1 the way I understand it.Question 2 is more difficult. Maybe you are looking at a different folder than the one defined. Sometimes I get annoyed with Windows Folders when I change something and it doesn't look like it "happened." Then I have to "View... Refresh" to update the screen. Maybe the folder with today's date is there and will appear if you close the C:RecordFile and reopen it.I waited a couple of hours before responding, hoping that someone who "knows things" would have the answer. Sorry if my contribution isn't helpful.The Download folder is used to copy entire motion files to the hard drive. Clicking on the Gear-Icon.jpgBox1.jpgBox2.jpgBox3.jpg
Oh, dear. Reolink cameras that are powered support lots of interface standards. In addition to Reolink's Windows, Mac, Android, & Apple applications, regular web browsers can connect directly to the cameras, and they also support streaming standards. The battery-powered cameras can be accessed ONLY with Reolink's software. The battery cameras simply do not have the "power" (humor) to run all that software.I think what you are attempting is impossible.
One of my biggest disappointments with Reolink's RLC cameras is how flying insects are attracted to the IR LED's and trigger motion events. Up close to the camera lens, a bug appears to be BIG and BRIGHT (totally white). Have to turn off email notifications because insects generate hundreds. SD card fills up quickly. I deal with it a bit by FTPing files and using a script to erase any file that has only one second of motion. Personally, it seems to me that the camera firmware could be programmed to (a) ignore any motion less than a certain number of seconds, or (b) ignore motion caused by something so bright. I fear that Reolink doesn't actually create firmware for the cameras. Anyway, it doesn't look like any solution coming soon.So.... I purchased a separate "IR illuminator" and mounted it about 8 feet away from the Reolink camera, but where it covered the same general area. Since my RLC-410WS cameras do not have software control of the IR LED's, I masked off the LED's with tape (leaving the light sensor at the bottom uncovered). Ta-Da! No more insect triggers.There are dozens of inexpensive IR lights. Mine is a Tendlux purchased from Amazon for $20. https://www.amazon.com/gp/product/B075ZYG89D/ref=oh_aui_detailpage_o05_s00?ie=UTF8&psc=1. I read an interesting review of the light on a web site: https://networkcameratech.com/tendelux-ai4-ir-illuminator-review. I figured, "what's the down side?" For $20 I can see what happens. Turns out it worked.Is this the solution for everyone? Don't know. For me, I was able to increase the nighttime sensitivity and now record the cats, possums, etc. who come through that part of the yard. But NO FLYING INSECTS.
Just to confirm what Brad reported: Reolink support confirms that yes, the Reolink client software searches for Reolink devices on the network by broadcasting UDP packets. Brad reported broadcasts with port 2000. My Wireshark capture seemed to indicate that the first broadcast was to port 2000 and the remaining broadcasts were to port 2018. (I did not keep it running very long.)I know of no way to tell the client software not to search for devices.This appears (to me) to be inconsistent with the whole process of "Add Device" and "Remove Device" (the trash can icon). Maybe the software searches for ANY device on the network that responds to UDP broadcasts on port (2000 or 2018), but it only displays the devices which have been "added". I guess the test would be to put a new Reolink camera on the network and see if the software finds it before it has been "added".What did Brad learn from support?
When you get a resolution, please post an update here. I just used Wireshark to capture packets on my PC when I started the Reolink client software (Windows). Sure enough, there is a constant stream of UDP packets, in my case to 255.255.255.255 port 2018 (not 2000). I notice that the source port increments by one each time, although the destination port remains 2018.Looks like it is hoping "somebody is listening" for a UDP broadcast and will respond with "I'm at IP address xx.xx.xx.xx" Maybe looking for a Reolink NVR?
Could you please clarify a few points?1. You say "at first...". Does that mean that the camera in this position DID recognize people coming to the door, but NOW it does not? In other words, the same camera in the same position behaved one way at first, and now behaves differently? If so, it might be worth cleaning the front of the camera. Perhaps the PIR sensor is dirty.2. What is the distance from the camera (a) to the front door and (b) to the far end of the sidewalk? 3. You mention recording someone as they "step down" to the sidewalk. PIR sensors appear to have difficulty recognizing movement "toward" the camera and are more capable with movement "across" the picture. RLC cameras which have constant power record continuously, and when motion is detected they can record starting 5 seconds before the motion begins. Battery operated cameras, like the Argus (and Netgear's Arlo), do not begin recording until motion is detected. Thus, the camera might not detect motion as a person comes up the sidewalk, detect motion when they step up and move across the picture, and then begin recording as the person turns around and steps down back to the sidewalk. Scanning user forums, I see a lot of complaints that battery cameras "miss the event" because, for example, the UPS delivery person walks up, drops a package, walks off, and THEN the camera starts recording.4. You have more than one Argus 2 camera. If you change to a different camera, does it also behave the same way?(I thought installing security cameras was going to be quick and easy. It has been neither, but I'm glad I kept at it. Good Luck!)
Alas, I fear your suggestion will be impossible to implement. PIR devices are cheap, self-contained devices, manufactured by the millions. They appear in things as cheap as a $7 nightlight. The reason they are included in battery operated security cameras is the low cost and the low current drain. Seriously, one AA battery can power a PIR sensor for nearly a year.PIR's work by detecting when Infrared intensity changes from one sector to another. That's why they do pretty well when something moves "across" the camera, and significantly less well when something moves "toward" the camera.Having low, medium, high settings is about all that can be done.Doubt that I'm wrong, and would be VERY happy if Reolink says, "we can do that!"
Welcome Back!
Hi there! Join the Commnunity to get all the latest news, tips and more!