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).
SUCCESS. This time, I left the Reolink Client (Windows) "open", but hidden behind other windows.Set the hour 5-6 for 'timed' and 6-7 for 'motion', and both worked.All of my five RLC cameras produced mp4 files in the identified directory. From 5-6, each file was 311MB, one every five minutes.84 files times 311MB chews through storage in a hurry.Starting at 6pm, only motion is being recorded. (Neighbor's cat. Cars driving by. etc.) These motion files begin about 8-10 seconds before motion begins and stop the INSTANT that motion ends. (Unlike SD Card recordings which go on for some time.)Both VLC Media Player and 5KPlayer display these files, "no problem."This recording option is certainly quick and easy to set up, but having to keep the client app open all the time would be impractical for me. I'd rather use FTP, which happens directly between camera and FTP server.There are LOTS of differences between PC and Mac. Could be the Mac version has a bug.
My experiment is a total failure. So far, there are zero files in the folder specified in the Windows Client settings for Record. To be fair, the client window has been minimized at the bottom of the screen. Maybe that makes the Client "dormant" or something. I will give it one last shot with the Client actually OPEN on the screen (totally in the way, but what the heck).
Well, the experiment is not going well. I set up "Timing" record in the Client for the hour of 6pm today and expected all of my PoE cameras to product one file each. And got.... Nada. No files at all. Then, I noticed the inconsistent parameters. Maximum video file length of 5 minutes. But... I just said to record for an hour! Which is correct?Have reset the video file length to 61 minutes and to record for an hour later this evening. Will report.
Thanks for the explanation. I was aimed at the individual camera FTP configurations, which have the same options.The general configuration does not mention FTP, so my guess is that you are correct. The client must be doing the recording.I will try that as well.
I will test this with the Windows client. Just to be sure that I understand, on the FTP screen I set some time "blocks" to "Timer" rather than "motion", correct?
I have advocated for a "minimum length of motion" setting for years precisely because of objects that do not appear on the camera long enough to make any sense looking at.Unfortunately, this type of setting will probably not be effective for avoiding rain. There is not "one drop" of rain that comes and goes away. There are hundreds of drops appearing constantly for (hours?) and they may appear over a large part of the area viewed by the camera. That would seem to call for a different type of artificial intelligence, i.e. if cameras can now detect "cars", "animals", and even "packages" (not Reolink), they should be able to detect "rain."
There has been no change to the WD Cloud server software? Each of my cameras FTP's to a different folder in my Filezilla FTP server, and I use a dedicated folder for transfers from the SD cards to my PC.What are the three MPEG programs that complain?
The (very slick) web page clearly shows "Argus" as one of the available cameras, which is not correct. I was a Kickstarter backer of that first battery camera and still have two of them. They are NOT included in this capability.Alas, the exercise is moot unless you have an Echo Show to view the camera feed on. The Alexa App on my phone refuses to play camera video. It would be easier to watch the front door if I could just tell Alexa (or Google) "Play front door cam", rather than open the Reolink app, hit the down arrow 10 times until it finally decides to open the list of cameras, and then... oh, darn. whoever was at the door is gone now.
I am confused by the combination of (a) file viewers and (b) Reolink Client. I have RLC-410-5MP, RLC-420-5MP, and RLC-510WS cameras on my network. I use the Reolink Windows Client to view them live and also in Playback. I also can download from the camera SD cards to my PC. These cameras also FTP motion recordings to a FileZilla FTP server on my PC.I use VLC Player and 5KPlayer to view the FTP recordings. Both report that they are MPEG-4. (See the descriptions from 5KPlayer and Media-Info below.)My confusion is because the Reolink Client is not involved in FTP file transfer. The file goes directly from the camera to the FTP server. My Reolink Client is almost never open, yet my motion records transfer via FTP all the time.I am probably missing something. Sorry.5K PlayerGeneralComplete name : D:\Reolink\FrontDoorCam\2021\10\01\Front Door Cam_00_20211001144606.mp4Format : MPEG-4Format profile : Base Media / Version 2Codec ID : mp42 (mp41/iso2/avc1/dash)File size : 56.5 MiBDuration : 56s 0msOverall bit rate : 8 456 KbpsEncoded date : UTC 2021-10-01 21:46:07Tagged date : UTC 2021-10-01 21:46:07VideoID : 1Format : AVCFormat/Info : Advanced Video CodecFormat profile : High@L5.1Format settings, CABAC : YesFormat settings, ReFrames : 1 frameFormat settings, GOP : M=1, N=60Media InfoGeneralComplete name : D:\Reolink\FrontDoorCam\2021\10\01\Front Door Cam_00_20211001144606.mp4Format : MPEG-4Format profile : Base Media / Version 2Codec ID : mp42 (mp41/iso2/avc1/dash)File size : 56.5 MiBDuration : 56 s 0 msOverall bit rate : 8 456 kb/sEncoded date : UTC 2021-10-01 21:46:07Tagged date : UTC 2021-10-01 21:46:07VideoID : 1Format : AVCFormat/Info : Advanced Video CodecFormat profile : High@L5.1Format settings : CABAC / 1 Ref FramesFormat settings, CABAC : YesFormat settings, Reference frames : 1 frameFormat settings, GOP : M=1, N=60Codec ID : avc1Codec ID/Info : Advanced Video CodingDuration : 55 s 976 msBit rate : 8 389 kb/sWidth : 2 560 pixelsHeight : 1 920 pixelsDisplay aspect ratio : 4:3Frame rate mode : VariableFrame rate : 30.000 FPSMinimum frame rate : 29.412 FPSMaximum frame rate : 40.000 FPSColor space : YUVChroma subsampling : 4:2:0Bit depth : 8 bitsScan type : ProgressiveBits/(Pixel*Frame) : 0.057Stream size : 56.0 MiB (99%)Language : EnglishCodec configuration box : avcCAudioID : 2Format : AAC LCFormat/Info : Advanced Audio Codec Low ComplexityCodec ID : mp4a-40-2Duration : 56 s 0 msBit rate mode : ConstantBit rate : 64.0 kb/sNominal bit rate : 127 kb/sChannel(s) : 1 channelChannel layout : CSampling rate : 16.0 kHzFrame rate : 15.625 FPS (1024 SPF)Compression mode : LossyStream size : 438 KiB (1%)Language : English
Sort of disappointing that the Windows Client states that 8.3.1 "This is the most current version available", whereas the Reolink web site says that Client 8.3.2 was posted on Sept 24 (5 days ago).So Sad.
Do not see an attachment?
Also interested in predicted time line. My RLC-510WA (ends with "A") camera does not support this feature. Can someone please remind me how users learn of new firmware for cameras?I see that the previous Support Center link to Firmware Updates no longer appears. (It was very handly to pull up that page and see, "Still no new firmware since April 7".) Should customers now bookmark the firmware page for each of their cameras and open those pages from time-to-time?
It was a good idea to test the camera before mounting it on the roof. The RLC-423 camera specifies a cable length of up to 330 ft. (100 Meters) I suspect there may be a flaw in the cable of the PoE injector. I would test the camera with a different cable (of any length). If that works, there is something wrong with the cable besides length.
If an ICMP packet does not arrive at an E1 camera, the camera cannot respond.How can ICMP packets get to a Chromecast when they cannot get to an E1 camera?
Will Papertrail collect ICMP packets? That would be an ideal substitute for Wireshark.The "fixed IP's" are done (a) by setting a Static IP on the camera, or (b) by entering the camera MACaddress into a router table so that it always assigned the same IP?
Dang. I wish I had a way to create multiple subnets. My WiFi router creates only one /24 subnet for all devices (wired, primary WiFi, Guest WiFi). Would love to capture packets on that 192.168.10.0/24 subnet and see if the E1 responds to those pings at all, or if it responds and they do not make it back to 192.168.1.0/24.Since the E1 does not have a web interface, the goal is to monitor the E1 using the Windows or Mac client software?I am pretty certain that RLC cameras accept connections from anywhere, so it seems strange that the E1's would be "different".
(Please forgive my ignorance. I got buried in the Unify user manual and made little progress.)The Apple/Android phone being used to 'cast' to the Chromecast is on one WiFi SSID in a 192.168.1.0/24 subnet and the Chromecast is on a different WiFi SSID in a 192.168.10.0/24 subnet.Can some OTHER device in the 192.168.1.0/24 subnet ping the Chromecast by the Chromecast IP?i.e. a PC in 192.168.1.0/24 can ping the Chromecast on its 192.168.10.0/24 subnet IP address?
Could you give examples of other IoT devices that are easily accessible from different IP subnets?I was not aware that the Ubiquiti Dream Machine could create different subnets. That is quite a step up from the normal residential router.
Trying as in* Seeking a way to do it? or* Trying to make the app work for them?I have the Reolink app loaded on four different Android devices (two phones, two tablets). All four devices can view and play back from my seven cameras
If they install the Reolink 'app' (Android or Apple) and you tell them the UID, user name, and password to the camera they can use the app to live stream and do playback.When you want them to stop, changing the user name/password will lock them out.
Welcome Back!
Hi there! Join the Commnunity to get all the latest news, tips and more!