Best posts made by Crimp On_62210811129

@user_629594821148673_629594821148673 I believe "new deals" will appear on the main Reolink web page as they happen. Today, for instance, the main page has a link to Black Friday deals.
Slide the page to see the Coupon Deals. (meh) Slide again for....

@nomahisssss_477125106348271 Oh, yes. Interested for sure. My "cheapo" Wyze cameras draw a rectangle around what has caused recordings. Would LOVE to see this on Reolink cameras.

Most people let the router handle IP assignments:

• Device (camera) is set to use DHCP
• Router is set to assign a specific IP to the device by hardware MAC address

Trying to "do both" is a receipt for disaster (eventually you will create a conflict without meaning to and debugging it will be frustrating)

It would improve the community forum a lot if Reolink would eliminate the dozens of bogus marketing posts that appear every day. Hire some teenager to watch the community and delete these posts as soon as they appear. (and kill the accounts that post them). Instead of every user individually skipping over posts, just make them disappear!

I am getting very close to the point of saying, "the heck with this" and never visiting this forum again. If enough frequent contributors give up, there will be no one left to help anyone.

I fear you will be disappointed. The E1 Outdoor specs are clear. Power is 12vDC, which is not the same as Power over Ethernet (PoE), which is more than 44V. The Ethernet jack is intended for initial setup (a common feature of Reolink cameras) and is not a PoE jack.

Thanks for the tip. Just opened the Windows Client, which prompted "New Version Available". Installed. Seems fine so far.
(but then, I had no problems with 8.16.8, either)

@bakkenkl_524424574742716 I believe all of Reolink's RLC cameras support FTP, which copies motion recording to an FTP server which can be ANYWHERE.
i.e. you can build your own "cloud". Not as slick and fancy, but certainly more secure than having an NVR on the premises.

I have installed several Tendelux 850nm IR illuminators purchased from Amazon (under $25). Placed them at least 4-5 ft. away from the camera, powered from a regular electrical outlet.
What I had found was that flying insects seem to be drawn to the camera infrared LEDs and appeared (to the camera) as VERY BRIGHT and PRETTY LARGE (because they were so close). Created lots of motion recordings that were essentially worthless.

Once the separate IR lights were installed and the camera IR LEDs disabled, those insect problems went away.

I agree. The FTP file appears to be "shorter in length (time)" than the Download File.
The utility Media Info confirms that the files are consistently different. (see mediaArea(dot)net)

I see no valid reason for this to be the case.

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.

To houser: I think you have it backward. Set the sensitivity "high" (i.e. detect more rather than less). This way, you will get not only the LARGE cloud movements, but also the (relatively) small "people objects". At my location, when the sun goes behind my nieghbors trees, My Reolink cameras record constant 'motion'.

I have asked (several times) for Reolink to let users know what the "trigger value" was for each recording. Would be helpful to know, "oh, THIS ONE registered 57, and the previous one was 12. Maybe if I set the cut-off to 40 I would not get the 12 but would get the 57." As it is, we have NO DATA to make a decision on.

I agree that this is a very strange situation.

• The Reolink Client must be able to communicate with the doorbell camera because it is able to open the Network Settings, navigate to Advanced, NTP, and change the NTP server to time1(dot)google(dot)com. Then the user can navigate to Maintenance, Date & Time, and select Synchronize. (I do not have a Reolink doorbell, so I am assuming that the settings menu is approximately similar to the RLC cameras.)
• When the user attempts to synchronize, the response is Failure. We have both verified that Reolink cameras are able to use the Google time server.
• Thus, how can it not work? One explanation might be that the Reolink Doorbell simply does not perform NTP lookup. That seems absurd because customers would be going crazy complaining about their doorbell cameras not displaying the correct time. The only explanation I can see is that the NTP packets (UDP, port 123) are either (a) not going from the camera to the time server or (b) the responses are not coming back. UDP is a connectionless protocol.
• If I were to investigate this situation, I would connect the Reolink Doorbell to a managed switch so that I could mirror the port and capture every packet that goes to and from the Doorbell with Wireshark. (That is why Ethernet devices are so much easier to work with than WiFi devices.)
• Once it can be documented how the NTP packets are failing, then the investigation can move toward what is blocking them.

@user_836203193905368_836203193905368 Yes. Reolink customers DO read posts on the user forum. All of my Reolink cameras are "stand-alone" (no NVR). Balancing the Cost vs. Performance, I am satisfied.

I would suggest starting with a single camera before investing in a complete "package" (more expensive).

FTP is a feature built in to the RLC cameras. (not the battery powered cameras). I use it to store recordings from 8-10 cameras using FileZilla FTP server. Provides backup for the camera SD card and (I know this is goofy) allows me to use VLC to view motion recordings.
There are no fees to use Reolink products unless one subscribes to a "cloud storage" plan (I have not)
Looking forward to someone reporting actual temperature experience. My guess is the cameras might function at lower temperatures, but if they don't then Reolink's answer will be "told you so."

Absolutely, 100% guaranteed, no.
Reasonably certain, yes.
Unless you have deliberately opened ports through your home router, the only pathway into the modem is through the connection that the camera has set up to the Reolink cloud using the camera UID. Then, the person wanting to view the camera has to have the password to log in.

When I asked Reolink support to troubleshoot an issue for me, they needed to know the UID (There are thousands of cameras. How do they know which one is mine? UID), and they had me set a temporary password on the camera so they could log in. (I actually created a new login ID/password. When they finished, I erased both.)

So, if someone learns the UID and password of your camera, they can install the Reolink app and look at your camera feed.