@cynthia_124785627824270 Any update on this issue?

Can Reolink just add a disclaimer that users should not import configurations from a different camera model? I think it's fairly obvious that different cameras will have different options and compatibility requirements. I hate to see a very useful feature removed due to the ignorance of a subset of users. Without config import/export, setting up cameras is a very time consuming process.

I upgraded one of my cameras before knowing this feature had been removed. There is no link to download older firmware versions, so now I'm stuck with this missing feature.

@cynthia_124785627824270 Any update on this issue?

Can Reolink just add a disclaimer that users should not import configurations from a different camera model? I think it's fairly obvious that different cameras will have different options and compatibility requirements. I hate to see a very useful feature removed due to the ignorance of a subset of users. Without config import/export, setting up cameras is a very time consuming process.

I upgraded one of my cameras before knowing this feature had been removed. There is no link to download older firmware versions, so now I'm stuck with this missing feature.

Great, thanks a lot. Please report back if you hear of any changes. On another note, do you know if there is a way to get email alerts when certain threads receive new replies? Currently I just have to go back and check every thread I'm active in to see if anyone responded.

I click done and it takes me back to the device list. Again, I cannot login because I have not entered the username/password. (Please these details back to the new device page. I should not have to add the device and then edit the device to put in the credentials).



I enter the username and password and save it.



Device login is finally successful when I go back to the device list.



I test the cameras and they work. So I close the Reolink application, then I re-open the application immediately. It tries to log back into the same device, but it fails.



This happens over and over again. There was a similar issue on the previous version of the app, but the screens were slightly different.
So in summary, we need a fix for the following items.

1. Username/password fields to the "add new device" screen. The "add new device" screen should like the same as the "edit device" screen.


2. Add a prompt for username/password whenever a device is automatically added to the device list.


3. Find out why the application is trying to use the UID instead of IP on both the local network and a remote network (over the internet using DDNS and port forwarding)


4. Change the settings for the Android application so the physical "back" button on the phone will function the same as the button at the top left corner of the screen. When I try to use the physical "back" button on the phone, the application tries to shut down instead.

I just wanted to provide an update of the Android app issue I have. I have emailed this to Reolink support as well, so hopefully they'll come up with a fix. I'm waiting to hear back.

Please see the following list of screenshots and I will explain each one.
I have deleted all of my devices, so the app is empty.




Now the software automatically sees my NVR on the local network and adds it. But login failed. (It did not ask for a username/password yet, so I'll try that. It should ask for one automatically).



I open the device configuration page and put in the username & password. You can see that the UID and the IP both show up. However, I have UID disabled in the NVR so it should not be broadcasting at all.



Now that I have put the password in, I try to log into my NVR. But login still fails because it is trying to use the UID instead of the local IP.



So I delete the device again, and then I click "Add New Device" before it automatically adds again. I put in the details making sure to choose IP instead of UID/P2P.





 

I will continue in the next post since I can't add any more attachments.
Screenshot_2017-01-20-13-55-32.png
Screenshot_2017-01-20-13-55-41.png
Screenshot_2017-01-20-13-55-49.png
Screenshot_2017-01-20-13-56-24.png
Screenshot_2017-01-20-13-57-11.png
Screenshot_2017-01-20-13-55-32-Resized.jpg
Screenshot_2017-01-20-13-55-41-Resized.jpg
Screenshot_2017-01-20-13-55-49-Resized.jpg
Screenshot_2017-01-20-13-56-24-Resized.jpg
Screenshot_2017-01-20-13-57-11-Resized.jpg

Thanks for the response Cracky.

However, when I try to use HTTPS, I get this:



I tried Internet Explorer and Chrome. Is there a setting I missed somewhere? In looking at the protocols supported by the NVR, HTTPS was not listed. I'm not sure if the next screenshot will show properly or be stretched, but I'm showing that under my "Network Advanced" tab on the Reolink desktop software, the HTTPS Port is set to '0' and is grayed out so I can't modify it.



This still doesn't address the concerns with the desktop/mobile apps since it's very likely they are not using any type of encryption to hand off the credentials during the login process. Thanks again.
2017-01-20_14-35-53.png
2017-01-20_14-38-38.png

Can we please get HTTPS added at least? Most very basic and cheap systems have this protocol built in. Thanks!

Just following up. I'd still like to know more about the encryption, if there is any at all. Encryption is very important so that others are not able to easily hack the cameras.

Do the cameras/NVRs have encryption of any type when being viewed from the mobile or desktop applications? The web browser only uses HTTP, so no encryption is being used there. If not, that means the mobile app would be passing the username/password over clear text each time it logs in.

Thanks. Under the camera RLC-410S specs on the Reolink website, it says

Power Supply DC12V PoE (802.3af) (optional)

But your chart says it should be 802.3AT.

802.3af standard supplies between 12 & 15W per port so that should be sufficient for all cameras except for the RLC-423 according to the chart.

Crackybiscuits, the only downside I see to using the separate POE switch is this - If the NVR is ever stolen, it's unlikely the thief will destroy the cameras as well so you'd have the footage there. However, with only 16GB in each camera, on an outdoor camera the footage will be overwritten very quickly. If there cameras are connected to the NVR and it gets stolen, the cameras lose power immediately when they take the NVR so the footage on the SD cards is frozen due to lack of power. If they are connected to an alternate switch, it's likely they'll not get unplugged and continue to record until the footage of the thief is erased. If combined with some type of alarm system there may be enough time to rush home or remote in to stop the recordings or save the footage.

It would be nice to manage them separately, but due to that fact I'll probably just setup the SD cards and then move the cameras back to the NVR.

So assuming that I do this for each camera, will the camera continue to record to both the SD card and do the NVR once it is connected back to the NVR?

It looks like I may have more flexibility if I just install a POE switch and connect all of the cameras to that so I can access them directly and the NVR will still see them and record.