Posts made by z0mbie_262929972969680

Related, but not exact. Do you guys still plan on releasing new firmware updates for the C1-Pros? They are IPC_51316 and I'm sitting on 6 of these that haven't seen a firmware update since 06/19 ??

I agree with fluidnyc and talkohavy that we should be allowed to extend, potentially up to 5 minutes of recording time for the cameras. I personally have the RLC-410W, RLC-511W, E1 Zoom, C1 Pros and Lumos models that could all benefit from this.

I also came here to point out that sometimes the cameras DO record for longer than 30 seconds... Scrolling through my RLC-511W, I see videos that are shorter than 30 seconds, and longer: 47, 57, 50.. and on my RLC-410W I have one that is 1 minute and 26 seconds long...

So in point fluidnyc and talkohavy, I think whatever algorithm Reolink is using to 'detect' motion on these cameras will allow it to continue recording if that aglorithm's criteria is met and it still thinks motion is occurring. I'd love to see more documentation on this maybe but as a quick user fix, allowing us to extend the recording time post trigger would be awesome..

That doesn't explain the recordings on my RLC-410W that are only 9 or 11 seconds long... I just updated to the lastest firmware last night. so maybe there is a fix in there

I agree, this would be a great feature add to ALL of the Reolink cameras. Those Wyze cameras are cheap too so it would be nice to see these Reolinks incorporate a feature like this that other cheaper brands are pushing. +1

Currently if you log into a Reolink camera with a 'guest' account via the camera's URL, you can see the entire camera's configuration to include but no limited to:

• * Network information (now I know what the internal network looks like)


• * FTP username and server address (now I can brute force this)


• * Email accounts used (information gathering and potentially people's names)


• * Camera's recording schedule (now I know when I won't be detected if i'm a person with malicious intent)

There should be really no reason at all to allow a 'guest' user to even access the configuration settings or 'gear' icon through the web page at all. I can understand allowing them to change their password but guests should be treated with 'zero trust'. It is not enough that they aren't allowed to change anything but you can take this one step further and not provide them viewing access to important/critical configuration settings. Thinking from a pentester's point of view, you can gain a lot of information if a guest account is compromised on these Reolink cameras.

I agree with Peter. a page with the latest stable firmware for each camera would be fantastic instead of having to search through the links that match my hardware version, but I don't know if my model is a part of that firmware until I dig through the links. Cleaning up the firmware page to have that stuff 'automagically' formatted would be a huge quality of life improvement for the end users.


Also, why doesn't the camera or the app (I'm using the reolink app on Android) tell you that there is an update(s) available for the camera(s). The camera settings page "System => Maintenance" Should know if it had an update and be allowed to pull the correct firmware for itself right there. Saves me from having to download, check the sha hash, etc. Or the app should say 'you have firmware updates for the following cameras' and then allow you to upgrade them through the app. would be pretty slick. I would love to see this

Keymaster Cynthia.. What kind of antiquated feature request / suggestion box setup is this? It's 2020 and you don't have an easy system set up for tracking issues/tickets? It seems backwards for me to have to open a new feature request to get a status update on an existing feature request.. I feel like this is creating duplicates and more noise for you all to filter through.

Please I would suggest looking into modern CM software like Gitlab or GitHub. Allowing the community to open and track issues would be better. It would allow you do track features like this: https://gitlab.com/gitlab-org/gitlab-foss/-/issues/49288

I will go submit a new request

This is a feature I would also like to see implemented across the board. I have several C1 Pros and an RC 410W that all provide me with false alerts when transitioning from day to night mode or night to day. Also some of the C1 Pros I have are in locations where the light during the morning causes them to transition several times before stabilizing so I get a lot of false detects. I am very interested in a fix for this!!! When do you think the 'senior engineer' will have an update for us?