Product Roadmap: What's Coming Next
How ColorX Technology Turn Night into Day
Reolink App v4.41 Released
To whom it may concern @ Reolink, I'd would like to report which seems to be a bug to me and also some nice to have features that are handy in my opinion and that could potentially be added in future firmware revisions.The BUG I have noticed is related to FTP motion uploading, which affects, at least RLC-423, RLC-410 and RLC-511 models with the latest firmware updates running on them (I believe the bug was already present on previous firmware releases so it's not something new). BUG description: When using FTP to upload motion events to a remote/local server, I noticed that even if I select "IMAGE ONLY" as the "FYLE TYPE", it always still upload a video file along with the picture/image/screenshot file of the event. When choosing this method I guess we were supposed to get an upload of an image only with no video file being uploaded as well.As nice to have features for the future, I would suggest, for now, the following:1. Regarding the Infrared, besides the AUTO and OFF options, please also provide an ON option. It would be nice to be able to toggle the infrared OFF/ON manually if necessary and not simply rely on AUTO/OFF.2. Still regarding the infrared, if for some reason we don't want to rely simply on the AUTO option, it would be nice to be able to set a scheduling (day/time) when we want to have them ON or OFF.3. Regarding the RLC-423, it would be nice if we could have more than 1 CRUISE. It would also be nice to be able to automatically switch between different cruises depending on the day/time. Let's say I would like to have one cruise for daytime and a different cruise for night time, or one cruise for week days and another for weekends.I hope you can take into account some of these suggestions. They would be valuable for my use case and I believe for many others as well.
Regarding the Bug report: My experience is "mixed". I was able to set an RLC-420 camera to FTP "images only", and that is exactly what it did. My FTP server contains only jpg files. No MP4 files. None.HOWEVER, the process was "confused". When I used the new Reolink client (Windows), it appeared that setting "Images only" did not "take". I tried the new Client, the old Client, and the web interface. So, (a) I am able to confirm that it IS possible to set the camera to FTP "images only", but I am NOT able to confirm that there is "no bug."It would take more experiments to determine if one or the other camera management options does not operate correctly.(i.e. is it the new Client? is it the new camera web access firmware? or....)Yes, I should have been more careful and documented each step. (sigh) "Is there actually a "bug"? Beats me.
What I observed just now when attempting to set the camera back to "clear video and images" was that clicking on the "Save" b**ton appears to not do anything. I think that the "bug" is that the "Save" b**ton does not work.
What I observed just now when attempting to set the camera back to ”clear video and images” was that clicking on the ”Save” b**ton appears to not do anything. I think that the ”bug” is that the ”Save” b**ton does not work.
Thank you for your comments. I don't use windows (Linux instead) so I used the web interface to set the cameras up, including the FTP setting. No matter what I do in terms of settings, I can't have only images being uploaded, it always upload video as well. It seems that "IMAGE ONLY" mode uploads image and a sub channel video clip.
We really appreciate your suggestions. We will forward it to our R&Dteam and help them make improvements in the future!For the FTP issue, it seems a little strange. If you need, please contact our support team at email@example.com to see if they can help you solve the problem.
Thank you. I will drop them an e-mail.
Thanks for clarifying that the issue exists with the web interface. I have been able to duplicate that.What I notice on the FTP parameters page is that the "Save" b**ton is set to "disabled", which is why it appears grayed out.I tried to edit the HTML code, which did seem to activate the Save b**ton, but clicking on it did not update the actual camera settings.The original Windows Client continues to update the FTP settings correctly, whereas my experience is that both the new 8.1.24 Client and the new web client do not.
Thanks for clarifying that the issue exists with the web interface. I have been able to duplicate that.What I notice on the FTP parameters page is that the ”Save” b**ton is set to ”disabled”, which is why it appears grayed out.I tried to edit the HTML code, which did seem to activate the Save b**ton, but clicking on it did not update the actual camera settings.The original Windows Client continues to update the FTP settings correctly, whereas my experience is that both the new 8.1.24 Client and the new web client do not.
I don't have an issue with the SAVE b**ton. The b**ton works ok and it sends the proper XHR request to the camera.That XHR request basically changes one parameter (streamType) to the value "3" when file type is changed to "IMAGE ONLY". The bug seems to be on the camera side (either on the web API or the ftp routine itself), not on the client/browser side.
Hi there! Join the Commnunity to get all the latest news, tips and more!