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).
I just set mine to the default of 5 minutes, still the same problem.Screen-Shot-2021-10-05-at-07.00.50.pngScreen-Shot-2021-10-05-at-07.01.33.png
No, leave the camera settings alone. Work only with the client side. On the client side do the following:Client settings>Record>Enable RecordNow you can either set a "Timer" (which records from all POE cameras) for the block(s) of time you select or you can select "Motion" (which records from all POE cameras) for the block(s) of time you want to record. I have not found it to make any difference for the end result, a MP4 file is generated with a camera name but zero bytes in it.
Finally figured it out and yes it is the Client as I suspected but it is NOT the FTP function of the camera. In the client you can turn essentially continuous recording on and of course provide a path and schedule for that function. The client is NOT recording but is generating a file with zero bytes in it and labeled as a mp4. All FTP function on the camera side is fine, all "Local Recording" is junk. A file exists but nothing in the file.
I understand the confusion, particularly with the title.True that the client is not doing the recording that the camera FTP's to a server, the camera "should" just be transferring a file via protocol. I had no problems prior to the last two released versions of the client. Once I returned (at REOLINK supports request) to the older version the videos were fine from that point on. Since they have no open source I cannot unwrap the exec they use to see what they are doing but I have quite a few people that use everything from WSFTp to Filezilla to upload files to my server with no issues. So it has to be something in the client, at least that is what I believe right now.Now with the client you do have the option to provide a path to download recordings to a specific location and I keep that location separate from the cameras FTP location. No reason to have to do that but I am doing so as a part of troubleshooting. Isolate and modify one option at a time.
Let me start with the specifics:Mac Big Sur 11.6, Reolink Client 8.3.1/8.3.2, Camera's 820A, 822A, 520A all with latest software and all with at least 30Gb SD sticks.Problem:When using FTP to a WD Cloud server the format of the MP4 file will not view in at least 3 viewers that had been used in the past under version Reolink Client 8.2.6!File on SD stick views fine within Reolink client. Error code from video viewer reads that the MP4 is NOT in a MP4 format. Videos downloaded from the SD sticks are viewable.
Running Mac 11.2.3Installed Reolink 8.2.0No battery level indicator, have to go use mobile app to get battery level ... needing to use two apps on two different devices is rather stupid!Battery operated (solar powered) cameras automatically connect, start recording and stay on until battery runs dead, no timeout. Already running one camera down every other day. If running app and the computer is powered off once you restore power, either by running app at startup or by initiating it manually, it comes on connects all the cameras starts recording. Not a bright move for a battery powered camera.Still no fixed setpoints for battery operated PT cameras, strange.
Welcome Back!
Hi there! Join the Commnunity to get all the latest news, tips and more!