Posts made by Crimp On_62210811129

(Caveat: I have only stand-alone cameras, no DVR.) When I want to set up cameras to view remotely, I have to define them by their UID, not their IP address. Each of my cameras automatically contacts the Reolink "Cloud" and registers using the UID.
Maybe what happened when the Reolink App was activated was it learned a similar identifier, maybe an NVR UID.

Not having one to look at, I do not know if DVR's have a unique identifier that can be used for remote access.

My advice is to email support@reolink.com and ask, "How do I set up my Windows Reolink Client software to access a Reolink at a remote location?"

There was a question previously about this and the answer is, "No. Not on the NVR."

If this were a stand-alone camera with internet access, there are things you could do to grant access to others, but the NVR appears to be "all or nothing."

Reolink gathers suggestions for product improvement. You could find that previous post and "Second it". Or, send email directly to support@reolink.com and make the suggestion.

I would have to climb a ladder to reset either of my Argus cameras, and I cannot remember (so long ago).
Is the Argus setup one of those screens where the password is shown only as "dots" and not the actual letters?
I have this vague memory of my pudgy fingers entering characters that I did not intend to enter and being very frustrated. I might have even had a period in the password and my phone would "autocorrect" and add a space.

On my Reolink Windows Client, when I click on the "Stop" icon in the lower left (looks like a square), my camera pictures all go blank. This matches the images above. When I click on the "Start" icon (triangle), they appear.

Can you try clicking on the triangle?

Yes, the Argus camera should have got a new IP address by itself.

The Reolink battery cameras connect to 2.4G WiFi because that is the only radio in them. When I set up my (first generation) Argus cameras, the setup process had me enter the WiFi name (SSID) and password in my smartphone app and then point the camera at the code that appeared. There is no need to fool around with the router 5G channel, changing channels, etc. Once the camera learns the SSID and password from the app, it looks at the available WiFi networks, picks the one with that SSID, and connects.

Can you relate what happened at each step of the camera factory reset and setup?

This is one of the annoying features of products which detect "motion" by counting how many pixels in the image are different from one frame to another. Moving shadows definitely "change pixels". I opted to keep making (mostly useless) recordings, but no longer send alerts. I also did some minor adjustments to the motion area. i.e. we have some plants near the front door that constantly move in the breeze, so I blanked them out. Did the same thing with the hummingbird feeder. For a while, I blocked out where cars would pass in the street, but then decided we have little traffic and it is kind of interesting to see how many actually do drive down our street. If this annoys you too much, be happy you only invested in two cameras.

Just a note: I saw a new item that Wyze was forced to remove their "person detection" code from their $25 cameras because whoever owned the patent had sold it to somebody (Google? Apple? Nest? don't remember).

There are other cameras with an antenna connector on the outside of the case. It is relatively simple to disconnect the antenna from those and attach an antenna with a long cord. (Argos Eco is one.) The Argus 2 WiFi antenna is located inside the case, and is probably wired directly to the radio chip. Even if someone could get the case apart and locate the antenna, it would take a lot of technical knowledge to connect an external antenna, run the cord through the case, and seal it back up again. Would totally void the warranty.

I suggest deploying the Argus 2 somewhere else and installing an Argos Eco with an external antenna. The Eco needs only a single 2.4G antenna.

"As I try to explain it works within my own network. I can see all cameras etc. Everything is fine. But if I move to another network and try remote access via internet it doesn´t work anymore..."

BatMan is correct. Provided that you have only one router (i.e. not both a modem/router from the ISP and a router of your own) then you must "Port Forward" an external port to a camera port. However, most routers forward a specific external port to ONE computer inside the LAN. So, if you have five cameras you want to access, then you have to set up five forwarding rules. To access the camera web interfaces (HTTP), you would do something like this:

External port 81, forward to (IP of camera 1), port 80
External port 82, forward to (IP of camera 2), port 80
External port 83, forward to (IP of camera 3), port 80

Then, when you want to access camera 1, you would web browse to: http://(your public IP):81

Do a similar thing if port 9000 is the destination. set up forwards from 9001 to 9000, 9002 to 9000, 9003 to 9000, etc.

And... Most of us have Dynamic IP addresses from our internet suppliers. In order to ensure that we always know what our current IP address is, we sign up for a DDNS (Dynamic DNS) service (I use No-IP.com There are lots of them.)

This all gets pretty complicated and tedious, which is why the camera manufacturers have turned to the "cloud" solution. Instead of carrying around a list of "Camera 4 is port xxx4. My public IP is now..." we just open the app and it shows us the "name" of each camera. We click, and we're connected.

I have had good results with questions like this by emailing support@reolink.com. Answering questions is their job. On this forum, most of the participants are "users like me" who have random knowledge and opinions, but no access to engineers.

Depending on the model, I believe the IR lights are controlled by a light sensor. In other words, "It's too dark, so I'll turn on the IR lights now." On some models, there is a setting to prevent the IR lights from every coming on. I actually use that feature because I realized that flying insects are drawn to the IR lights and show up as VERY BRIGHT IMAGES to the camera, which records them as "motion." What I did was purchase separate "IR illuminators" and mounted them at least 5-6 ft. away from the camera. Bugs can fly near them all they want and do not influence my cameras.

For remote access, cameras have to be added to the Windows client app using their UID's, not IP addresses. The UID is the key into Reolink's "cloud" that the app queries to find the camera.

If a person were to breach security (i.e. learn the UID/password, they could use the app to turn recording back on.)
The Reolink cameras all include a "schedule" function of one type or another. You could, for example, set the cameras to record only when you expect the house to be empty and not record when you expect someone to be home.
A number of systems have enabled "geofencing", where the camera turns on only when the cell phone is away, and turns off when the cell phone returns. This, of course, is little help when more than one person could be home.
The Simplisafe camera addresses this issue by having a way to cover the lens (https://simplisafe.com/simplicam-security-camera)

I am afraid that this issue is too complicated for simple solutions. "I want the cameras to view and record when no one is home (security). But, I don't want it to view or record when my wife or I are home. But, I do want it to view/record when a housekeeper comes in (and turns off the alarm!), or when the kids are home with a babysitter, or...."

Reolink is a fantastic purchase for price and quality. In terms of software development, not so much. If it doesn't do what you want, chances are it never will.

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.

You could be correct. My Sony Android streams both live and playback from my RLC-410, RLC-420 and from my (original) Argus cameras. What a bummer!

Might help to identify by model number the cameras that the app cannot show recording from.

The specification page I looked at very clearly says "Web Browser - No". Here's a link to the PDF version of the specs:
https://home-cdn.reolink.us/files/docs/specs/E1-IP-Camera-Specifications.pdf

What I see is that the camera works with the Reolink "app", not with a web browser.

The difference between "ordinary" and "administrative" users is that only administrators can modify settings. Ordinary can only view. Playback is part of view. If you happen across some NVR that has a provision to allow only live view, please post about it.

There are any number of web sites explaining the different types of twisted pair ethernet cables. If you want to "future proof" to the extreme, then Cat8 cables may be worth the extra cost, especially considering that labor cost will be a huge percentage of the total installation cost.

HOWEVER, even 8MP cameras ("4K") will not come close to the capacity of ordinary Cat 5e or Cat 6 cable. There are usually markings on ethernet cable. What do the marking say? (All it says on the web site is "18m network cable".) Whatever cable they include in the box is certainly "good enough."

Looks like only certain models of Argo support the "Look Back" feature, and only if the camera is plugged into a power source, and the solar panel does not count as a power source.

https://kb.arlo.com/000062053/How-does-the-Look-Back-feature-work-on-my-Arlo-camera

The Argus PT has only a 2.4G radio in it. (Most of the battery powered cameras I have seen are 2.4G.)
Even if it is physically possible to install a 5G antenna, all that will do is produce a "miss match" which will reduce performance.

The video resolution on the Argus PT is 1080p at 15 frames/sec. 2.4G WiFi is perfectly capable of providing enough bandwidth to carry that signal. My original Argus cameras are connected at 2.4G and they work just fine. If the camera is reporting "full bars" and does not transmit video correctly, there is likely some other issue. I would contact Reolink support directly at mailto://support@reolink.com