Posts made by Chopstix

@jfcouture007_645096358552133 the only thing I can think of is perhaps network issues. Are you seeing this in the "Streams" setting in the cameras? Odd that it is happening to two different cameras. Do you have other camers?

@oakmont_633419891937300 best to email Reolink Support for that request. We Global Moderators are not Reolink employees. We are end users just like you that volunteer our time to help the community.

@oakmont_633419891937300 HyBridge removes the Reolink private LAN (172.16.25.x) and bridges the NVR's camera ports to the NVR's single LAN port so that the NVR and all the cameras can be on your home network segment.

For NVR's without HyBridge, the same result can be accomplished by connecting the cameras directly to your home's router/PoE/Wi-Fi switch, not to the NVR's camera ports. You will have to factory reset all your cameras and set them up as standalone. Then, you can add each camera to your home's automation. Once all that is done, you can use the Reolink app to add them to the NVR.

@user_921292635025597_921292635025597 Sorry for the delay. I can confirm that in daytime B/W mode, mine does the exact same thing as yours.

@gailsmule_905391527133360 there are so very man many factors that dictate how far a Wi-Fi signal will reach. In the absolute most ideal conditions, 2.4G Wi-Fi will reach maybe 300 feet. Add walls and environmental RF interference, that number begins to drop considerably. Bump to 5GHz, it drops even more so.

@user_909487502692587_909487502692587 hmmm. I am wondering if your cellular provider has some ports blocked -OR- the cellular provider is translating the camera's IP address (using NAT).

Just some background, when the camera is setup, it's IP address and other info is registered with the Reolink cloud servers. When the client app attempts to connect to a camera, it does so through the cloud servers. So it sounds like after registration when the camera goes to sleep, it can not be contacted again. When you setup the camera are you initially able to live view?

FYI Global Moderators are not Reolink employees. We're end-users just like you that are trying to help others via our own experiences with the products

@user_909487502692587_909487502692587 I do not use LTE cameras but I do not believe this camera does 24x7 recording thus will go into standby and disconnect from the app. Did you check the memory card to see if it recorded your presence? Did you give the app adequate time to reconnect? Additionally, even with no detection, you should be able to connect to the camera for live view.

@branman_824706912129181 us Global Moderators are not Reolink representatives. We are end user's just like you that have been asked to simply help out with the online community. If there are enough requests to Reolink support about it, they may escalate to the dev team.

@markroseuk_852823011377331 In the app settings, turn on Auto Live View. The app with then open whatever camera it was on when it was closed.

@reocam_448003255267488 If connecting to a DVR during initial setup, the DVR will assign the camera a password. The password setting is for stand-alone use of the camera.

@user_922334313095395_922334313095395 Has there been recent changes to the environment?... new equipment, moving of equipment, etc? Since you said it is affecting all the cameras, I would troubleshoot closer to the NVR for possible interference.

You could start with an inline RFI filter for the NVR's power cord. You could also try replacing one of the ethernet cables with a shielded type to see if it solves the issue with that specific camera.

@timmins-home_90898281234040 you will need to connect all the cameras to a PoE switch or get PoE injectors to connect them to a non-PoE switch. You are NOT connecting the NVR at this point. Get all of your cameras setup as stand alone cameras on your home network. Alexa functionality should then work. Once you get all the cameras setup the way you want, connect the NVR to the network and add the cameras to the NVR via the app. DO NOT plug the cameras' ethernet cables to the NVR. Everything gets plugged into your PoE switch.

@user_921292635025597_921292635025597 Oh so that video is B/W daytime footage? I know you stated it is B/W for plate capture, but does it do the same in daytime color? It does look like the exposure adjustment happening. Open a ticket with support and attached that video. They may say that it is normal or they may have a firmware update for it. I have set my camera to B/W and will check my captures from the day hours tomorrow to see if they are as drastic as yours.

I will tell you however that I miss the first few seconds of a person walking so the Altas PT Ultra with continuous recording might be a better camera for you.

@user_878766570258573_878766570258573 I do not believe it is possible to disable one of the streams. At least not so on the model cameras I have. I suggest that you open a ticket with Reolink Support. As for the default stream that opens, hmmm, both my iOS and Windows clients open to the last used stream. The only exception is the preview... the preview is always low. Selecting a camera to view however will result in the last used stream for that camera to be opened.

@coconutdog_101409440162028 unless @joseph_1979 has an idea, you might want to try opening a ticket with Reolink Support.

@user_921292635025597_921292635025597 upon wakeup, my Argus PT Ultra does the same, although most of our triggers occur during the day so the effect is nowhere near that drastic. Have you tried with various IR and spot light combinations to see if one of the lights is causing it?

@reolink-system_824158258282663 my recommendation is to take the camera and D20 plate to a hardware store and ask a knowledgeable clerk for assistance. You will want stainless steel machine screws with washers and nylon locking nuts to attach the camera. Alternatively, you may use stainless steel self-tapping sheet metal screws. A knowledgeable store clerk should be able to advise you.

@gotyatoolz_707830456418551 on the PC client, you can choose different grid sizes to minimize the number of blank boxes.

Having deployed Reolink NVR's for customers, I found the Home Hub (Pro) initially confusing. On the NVR's the camera ports are labeled 1-16 and the network port is labeled LAN. In the HHP, the LAN port is effectively the ports 1-16 equivalent (Reolink private LAN) and the WAN port is effectively the NVR's LAN port. I feel that this cross of labels could be released better as to minimize confusion for those that have previous experience with Reolink NVR's.

Here at home with HHP, I have Wi-Fi cameras connected to the Reolink private Wi-Fi on 172.16.25.x. I have a Layer-2 PoE switch that is segmented into 2 VLANs... one for PoE cameras and the HHP's LAN port (VLAN25), and the other for general access for my home VLAN1). I have the HHP's WAN port connected to VLAN1. This isolates all Reolink traffic on VLAN25 and the HHP's NAT handles all the traffic routing to VLAN1. For me, I could not have asked for a simpler setup. If the HHP did not have it's own private LAN, I would have had to upgrade to a Layer-3 switch for the VLAN routing. The topology that the HHP offers is near perfection in my opinion.

From the perspective of a "non-techie", I think some of the advantages of this are lost. In fact, it might even come across as confusing. After spending some time here on this Community page, I do see that there are users that do not easily comprehend the Reolink private LAN concept.

The Home Hub series is definitely geared for Wi-Fi cameras. The setup process is simple and easy to follow and Wi-Fi cameras integrate easily for creating the Reolink private LAN within the user's existing home network. This ease of setup is a great talking point as well.

@user_620089981972582_620089981972582 Netgear's "Good" might work well for UDP services but not so much for TCP services. With streaming audio/video (UDP), small connection drops might not even been noticed due to buffering. If I am not mistaken @joseph_1979 mentioned in another post that Reolink uses TCP, which can experience more noticeable interruptions if the data stream is weak.