Posts made by Chopstix

@denverbenve73 as far as I know, enabling Hybridge mode on the NVR should not have affected your ability to port forward to the NVR as long as your NVR still has the same private IP address 192.168.0.x and your Internet connection IP (public) address has not changed. If your public IP is a dynamic IP address, then you will need to see if your router/CPE supports Dynamic DNS (DDNS) as @joseph_1979 indicated. If it does not, you will need to manually monitor your public IP for changes.

Assuming nothing has changed, check to see if the HTTP/HTTPS access settings in the NVR has remained on. NOTE: You will not be able to access each camera directly via the web browser. Port forwarding does not allow multiple private devices to be forwarded on a single port. Thus, you must still access the cameras via the NVR. Remember that you still have the option of enabling UID and using the Reolink mobile client.

@flarad_910011091763400 you will get drastically more of these false triggers if the IR is on. As noted, you can also use AI detection to tweak sensitivity. In many cases, you will also need to disable alerts for general (non AI detected) motion.

@denverbenve73 if the NVR is in Hybridge mode, you can connect them to the NVR ports.

@joseph_1979 yep yep. I was just curious if there was password-less view only access. Your information paired with my testing confirmed that this is not the case. Thanks brother! Cheers.

@celina_867750978158811 @joseph_1979 yes, MX query resolves to root domain IP address. Full zone file query does show mail<dot> as an A record that resolves the same IP address. I have found over the years that using a FQDN versus root name only can often times solve issues. It doesn't hurt to try.

@denverbenve73 unfortunately, you will have to factory reset the cameras and follow these steps...

1) Remove all the cameras from the NVR settings.
2) Reset all the cameras.
3) Setup the cameras as stand alone (this will allow to to create your own camera passwords).
4) Add your cameras to Google Home.
5) Add your cameras to the NVR.

When you configure the cameras first in the NVR, the NVR sets a private password for each camera. That is why you can not add them to Google Home. By configuring the cameras a standalone first, YOU set the password.

@celina_867750978158811 your SMTP server address is incomplete. It is missing the host. Try using mail<dot>disroot<dot>org for the SMTP server address.

@joseph_1979 From an infrastructure perspective, I understand... the Reolink private LAN is not accessible thus no camera will be accessible. However, if connected via PoE switch, the IP address is reachable thus the camera is reachable. However, would the camera not be password protected from the HHP/DVR? Or is view-only not protected?

EDIT: I just realized that I have 1 camera that is not on my private VLAN. I am going to see if I can connect to it.

EDIT: I was unable to access the camera from web browser. I attempted to add the camera to a different app installation using its UID however it prompts me for a password. Of course we do not want people to attempt to hack our cameras, however the UID alone does not grant access to the camera feed.

@joseph_1979 So for clarity, camera + HHP/NVR on the Reolink private LAN switch, no access with UID. But if camera + HHP/NVR on home network switch, the camera can still be accessed with UID?

@joseph_1979 Totally missed that! Thank you! Can a camera connected to HHP/NVR still be access via UID without account password?

@user_884734665736402_884734665736402 There should be no issues using the Reolink app to access your DVR/cameras that are behind a dynamic IP since remote access is via the Reolink cloud servers. If you are not planning on using the Reolink app, sure, it is a bit more complex to use a dynamic IP.

Too soon to laugh?

@user_933989755908283_933989755908283 When you are on your LAN, you communicate directly with the NVR. When you are away, you communicate with the Reolink cloud servers. Since you are experiencing intermittent connection issues on both 5G and remote Wi-Fi, it is possible that A) The LAN that your DVR is on is having router/Internet issues with the Reolink cloud servers -OR- B) The issue is larger and perhaps regionally you have poor connectivity to the Reolink Servers.

I would try rebooting your LAN router/Internet modem/CPE and see if the helps. If it does not, I would open a ticket with Reolink Support. Make sure that you give them as much detail as you can including steps you have taken (reboots, 5G, remote WiFi, etc).

@sunshine-web_933834616910061 Get two doorbells and two chimes. Each chime can have a different sound. Yes, you can have multiple doorbells in the same WiFi/LAN.

@gahoak_900061514571953 I am running the same version. Expand the device list of camera on the left side pane. Click the setting cog for the camera you wish to check firmware then click Info.

@joseph_1979 I am guessing that mine is beta camera as it seems like only the Reolink Trial participants have them.

@ilenia_932159192342750 I do not use the camera share feature however, if you are sharing it to your own phone, why not just install the app on your phone?

@zjga1951_57983139328235 DC power cable? I believe that they are 3.5mm x 1.35mm. Just check Amazon.

@user_933989755908283_933989755908283 how are your cellular data speeds? 4G? 5G? If possible, connect to a high-speed Wi-Fi network away from the DVR location. If it works fine, then it is a speed issue with your cellular service.

@joseph_1979 no, it is a battery/solar Argus PT Ultra with motion-tracking. Same one that @KimchiGUN has... we got them through the Reolink Trial program.