Reolink Year in Review 2023 Learn More
How ColorX Technology Turn Night into Day Learn More
Reolink App v4.43 Released 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).
I have mentioned this several times. It makes SO much sense.I also think there is no reason not to have SETTINGS for several parameters."Prerecord", for example, seems to be a fixed number of seconds or none at all.The user should be able to set up to some maximum value, say 0-20 seconds.Post record is the same.I finally solved the "flying insect problem" by purchasing separate Infrared LED lights and placing them 6-8 ft. away from the camera. Bugs are drawn to them and do not appear to be BIG BRIGHT OBJECTS to the camera.
I believe under Profile... Settings (gear symbol) there are options for what notifications to receive.
I believe that all important settings are kept on the cameras themselves. When the Client program starts on the new computer, it will scan the LAN looking for cameras and import the settings from them.
I agree with Fiona that FTP is based entirely on the server IP address. When the server is on the LAN, FTP will not attempt to access the internet.(caveat: I have no NVR. My individual cameras FTP motion recordings directly to the LAN FTP server.)On the cameras, there is an option in the FTP setup to "Test" the FTP settings. Took me several tries to get the FTP logon information/p[censored]word/directory parameters correct.Should be relatively simple to do a "Test" with a live internet connection and also without a live internet connection.
Absolutely. I have two "battery" cameras that are USB powered. The battery cannot possible run down, so this alert is not useful.
I know of no method to set a constant FTP file name on the Reolink RLC cameras. (Battery powered cameras do not support FTP at all.)(Lack broad experience with web cams, but some brands such as Wyze and Arlo also lack FTP.)The effect you seek may be possible some other way, such as:
support.reolink.com/hc/en-us/articles/360007011233-How-to-Capture-Live-JPEG-Image-of-Reolink-Cameras-via-Web-Browsers
Click on the Plus sign ("+") and the Reolink Windows Client application will automatically search the local IP subnet for cameras and display any that it finds.To add cameras that the program does not find on the local network, enter the UID code for the camera in the box and the program will search the Reolink "Cloud" for the camera, similar to the way the Reolink Apple or Android app does.
My guess: People will be ice skating in.... (that place) before Reolink releases a camera with PowerLine built in. That's not their 'niche'.A subs[censored]ute would be either:
Would you mind sharing the reasoning for not using Google to watch for and notify of new Reolink app versions?
@reolink-fiona And, there is now a Beta version of Windows Client 8.4. My guess is that Reolink engineers will be more likely to respond to problem reports about the latest software version.
Agree. A wired connection is better in a number of ways, provided that it is convenient to install the Ethernet cable. "outside home about 40ft away" raises some flags.
Wireshark captures that the Reolink camera sends out NTP requests and no NTP responses come back.There must be something different about the way the Reolink camera is being networked that is stopping the NTP responses from getting through to the camera.Is this camera on the same switch as the other cameras and the port based VLAN is defined the same way?
I agree that this is a very strange situation.
My thought is that "if everything is set up correctly", then the Reolink Doorbell should perform NTP just like every other device. (The forum is not flooded with posts complaining that, "my doorbell doesn't know what time it is!") The question about network architecture is simply because most consumer networking products do not provide VLAN capability. My "guess" is that there are managed switches involved and that the Reolink doorbell is connected to one of them and that switch port is defined to be in a specific VLAN. There is a gateway somewhere that connects that VLAN to the internet.Would it be possible, for example, to temporarily place the Reolink doorbell in the default VLAN that has internet access? (like most other devices).In a way, it is fortunate that the Reolink doorbell is a PoE model, which makes it much easier to capture the port 123 traffic to/from the doorbell. (I have found that capturing communications with WiFi devices a lot more difficult than 'wired' devices.
Very strange. When I set the NTP server on a Reolink camera to time1(dot)google(dot)com, it synchronizes correctly.(When I set the NTP server to garbage(dot)com, it fails - as it should because that is not an NTP server.)I agree that capturing the actual packets is the best way forward. Either the doorbell sends the request using port 123 or it doesn't.Mention of VLAN in the problem description "raises a flag" for me. Reolink cameras are like most consumer devices. They have no concept of VLAN tagging. What sort of network are these cameras part of?
My understanding is that cameras connected directly to the NVR do DHCP against the NVR. The NVR can function with no network connection at all. (not practical for most of us, but....)
The entire purpose of Virtual Local Area Network (VLAN) is to have one physical network, but create virtual networks within that network which are entirely separate.To have communication between devices on one VLAN and devices on a different VLAN, there must be a router that is connected to both VLANs and has static routes defined to allow the desired communication. Most consumer routers do not support VLAN technology. More business oriented routers often include VLAN capability, as it appears this installation does.I would start with the user manual for the router that has defined the VLANs to understand how to create static routes linking two of the VLANs and perhaps restricting which devices can use the static routes.
Please provide more detail, such as:
It is really unusual for someone to purchase just one stand-alone Reolink camera.
The enormous difference between line powered and battery powered cameras is the use of a P[censored]ive InfRed Sensor (PIR) module. (search Wikipedia for "p[censored]ive infrared sensor")Whereas the line powered camera can consume power to compare every pixel of the camera view from one frame to the next and count the number of pixels that have changed, battery powered cameras are in a "semi-idle" state waiting for the PIR sensor to detect enough change in the infrared picture to signal "movement". That is the only way to make the battery last any length of time at all.When the camera is in Live View (or when playing a recorded motion video) it can use the "feature" to draw a box around objects (cars, people, pets). I tested this just now on an Argus 3 Pro which did not have the feature enabled. It had recorded very few videos so far today (the sensitivity was set at 80). As is typical of PIR cameras, moving cars were often almost "out of view" before the camera began recording. (Remember, line powered RLC cameras typically begin the recording 5 seconds before the object even appears. That is because they are constantly recording a 'loop' and can 'back up' to start recording before motion was detected.) Once I enabled the motion detection feature on the Argus 3 Pro and played back the same recordings, NOW those goofy boxes appear around things.My disappointment with Reolink's motion boxes is that they appear around objects that are not moving at all. i.e. every automobile in the picture has a box around it, even though all but one are parked and not moving.My sense is:
My first step would be to contact Reolink support via email. (support <at sign> reolink.com) and request a Return Material Authorization (RMA). Would love to hear how they respond.My understanding is that Reolink provides a two-year warranty on new products. Click on Support at the bottom of the page and then click on Warranty and Support.
Welcome Back!
Hi there! Join the Commnunity to get all the latest news, tips and more!