Reolink updates Learn More
Meet Reolink at IFA 2024! Learn More
Reolink Q&A 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).
@reolink-oskar I have some WP DTNVG's for running around in the dark but that tech is far too cost prohibitive for residential and commercial cameras. I think low LUX cameras are the way to go. My RLC-843A's far out perform my 1240A's in low lighting. In the suburbs with skyline glow, my 843's do not need IR while my 1240's do. I don't like color NV as it requires white light. As a result, depth of field is only as good as the throw of the light. On one of my 843's I have disabled the spot light for this reason. If low LUX cameras are not an option, external IR flood lights. I have a Duo2 mounted on my second story roofline for overwatch of my back yard. At that distance, the built-in IR is useless so I splash the property with two IR floods.For tactical use, companies are mixing thermal over one eye and NV over the other. The tubes are matched and calibrated and the end result is amazing recognition ability in the dark for the operator. Not sure if that could be incorporated cost effectively into a security camera, but it would be sweet.
@radioastronomy_410111540293820 I have two external IR flood lights in my back yard for this reason. I have the cameras IR turned off and my two external out of view from the cameras while still splashing the the grounds. Reolink already makes an external camera controlled flood light so I don't see why they could not do the same with an IR light.
270-360 degree PIR for PT cameras.
@joseph_1979 hahaha. They put me in the cool kids club.
@icancyou_596163611529276 I do not have that camera model however I do have seven of their cameras which some have audio recording enabled and others do not. Never had an issue with the settings reverting themselves back to on. You might try to submit a trouble ticket via the website.
@user_715874138988770_715874138988770 I have had my own issues with support but never them not being responsive. Did you submit your ticket via their website?Regardless, bullet camera or dome? Dome cameras have a seal that is easily damaged of not reassembled with care. Also, the cover retention cable can easily get caught in the seal during reassembly. I had one that kept fogging and upon examination saw that I pinched the cable in the seal. I cleared the pinch and have not had issues since. Do you know the IP rating of your cameras?
@alan_909533752111327 I have found the same occurrence with the Windows client. To resolve it I had to do the following:1) Open up a max grid view to find cameras that are not on sequential channels. Often times when I add a camera, I find that the NVR will drop it in some random channel way down the list. I have had to drag/drop my cameras to be sequential.2) Change the live view resolution. I have found that often times when adding a camera, the Windows client will choose a preview resolution that the camera does not support. This causes the preview to be missing.
I am not aware of a Reolink branded extender although I also call my kids by the wrong names sometimes. I am wondering if the firmware is simply future proofed for an extender that is in development.
@boomish_893913578897601 I too noticed that ALL my iOS clients stopped getting notifications sometime in the past week. The solution was to delete the clients and reinstall. In my case, I have all my cameras connected to a Home Hub Pro so the app reinstall was easy... just connect to the HHP and back in business. If you don't have a HH/NVR, you'll have to add each camera back to the app. As for cellular, when the notifications stopped it stopped on both Wi-Fi and cellular but after the reinstall, it started working on both again. If you can access the camera via the app while on cellular then there should not be anything preventing notifications over cellular. At least not that I am aware of.Yes, understand now what you mean by it not being a native iPad app... apps camera preview screen does indeed stay on portrait. We have multiple cameras and my wife uses the grid view feature which always follows the orientation of the her tablet so it has never been an issue for her. If you only have the doorbell, make sure in the app settings to check the box "Auto Live View". It will launch the last used camera (in your case, the doorbell) automatically in whatever orientation your tablet is in. Hang in there!
@joseph_1979 I returned both a Duo 3 and Duo 3V for this exact reason. I ended up using Duo 2's for front and rear overwatch.
Is the bar wider than the distance between two of the 3 camera mounting holes? if not, orient the camera mount so that one hole is either at 12 or 6 o'clock. Use a screw to fasten the mount directly to the bar through that hole.The other two holes will now be on each side of the bar. Use a flexible pipe strap (or flat stock) across the back of the pipe to secure the other two holes.
We use the iOS client from the App Store. My wife has it on her iPad Pro without issue. Yes, the app is default to portrait mode as is the iPad's default orientation. You must rotate to landscape for full screen. We have never had an issue with video quality (we set ours to HIGH) even over cellular.Change is often times difficult with software especially if you have developed a routine. We came from Vivint so we find the Reolink app refreshing even with its quirks. I encourage you to give it a chance. Cheers.
The tracking works well. I am surprised that the lights/sound of the camera did not startle it. It must be used to the area.
Unfortunately, when I go to view the devices/cameras, I can find no setting on the mobile app to select a preferred band.
@user_829609175638167_829609175638167 Odd. My cameras allow me to switch networks as well as set a preferred band. If you factory reset the camera, can you then choose the 2.4G network during initial setup?
You said you swapped ports. Does the issue follow the same cameras? Have you factory reset your DVR as well?
Is the Amcrest connected via an external PoE switch? You can not use 3rd party cameras on the built-in switch unless the RLN36 supports the feature of disabling the internal private network 172.16.25.x and bridging the internal switch to the external LAN.
Not sure if the Duo Wi-Fi has this option (mine are PoE) but my other WiFi cameras have a "Wi-Fi Band Preference" setting to switch between 2.5/5. It's under Settings-->Wi-Fi in the Reolink mobile app. Again, not sure if the Duo Wi-Fi has that option.
@reolink-oskar a tazer. Only partially joking. I do not know how it is in other countries, but in the US, theft of delivery packages from one's porch is a common problem.
@joseph_1979 It's been 15+ years since I've dealt with the programming side of unicast/broadcast/multicast, but if memory serves, with direct broadcast you must specify the destination subnet. So in my example, a host on 172.20.1.x broadcasting to 172.20.1.255 will go no further than the local subnet even if broadcast forwarding in enabled on the switch. In order to reach the cameras on 172.18.250.x, the client must broadcast to 172.18.250.255 -OR- to 172.255.255.255.Ultimately as long as the client finds the cameras in other subnets without UID, it doesn't really matter what the broadcast address is. The actual address is more for my own curiosity. I'll dust off Wireshark after the holidays and have a peek.Thanks for the chat!Cheers,Joe
@joseph_1979 I did speak with Oskar a couple of weeks ago, but please do speak with him as well. I have been a network and system engineer since the days of Windows 3.1 and LANtastic... Windows server technologies and Cisco products in particular. Also a few years of SQL database and web development sprinkled in. I would be glad to help out where I can with more than 1 post every 24 hrs.Interesting that Reolink chose to utilize direct broadcast... How does the app know what direct address to broadcast to? What I mean is, assume the cameras are on 192.168.10.x and the Reolink client is on 192.168.20.x and let's also assume there is no Internet access so UID is not in play here. How does the client know to net-direct broadcast to 192.168.10.255? Even with the possibility that it is based on the client IP address, a broadcast to 192.168.255.255 or even 192.255.255.255 would only work if the both the cameras and client are on the same class private network.That is actually what I need to test... I have some sandbox cameras on 172.18.250.x and the Reolink client on 172.20.1.x with Internet access and UID. I need to disable Internet and enable direct broadcast forwarding on the switch and see if the client can connect to the cameras. I suspect that it will based on what we have been discussing, only now curious on what address it will use... 172.255.255.255 perhaps? It has been well over a decade since I have used Wireshark but I may need to dust off the cobwebs and fire it up.
Welcome Back!
Hi there! Join the Commnunity to get all the latest news, tips and more!