There has to be some better information than that. It would be impossible to produce cameras without this being written down somewhere. Isn't there some detailed technical docs?

Thanks, I am aware of that. I have some running 48V POE and some 12V via the bullet. What I'm asking is what is the voltage range of each of those? For the POE power I'm guessing it's the standard 802.3af voltage range (37V to 57V) although maybe it accepts lower voltage. For the 12V input what is the min and max voltage that can be supplied? Does it all feed into the same circuit so I could supply say 10V through to 57V to either?

Thanks, that I know, that's what's written in the specs. But what is the voltage RANGE? It can't possibly require exactly 12V and explode if it gets 12.1V, it must have a working range. Most things are fairly tolerant of a small change in voltage.

@stefan8853_885395552829605 They did fix this, in a way. They made the "Auto Add" option on by default, so cameras should be added automatically. For me, the issue was that I had old firmware on the NVR. Both the android app and windows say it was up to date when it wasn't, so check your versions on the web.. There is one possibility, in that the auto add option is off by default from an old firmware. The only way I know of to turn that on remotely is to make sure the NVR is on the latest firmware and then factory reset it. You don't lose all that much factory resetting it, assuming it gets its IP from DHCP.

EDIT: Just to be clear, the issue was the new cameras would not work with the old firmware. That could likely be your problem too.

@joseph_1979 It's an odd failing. On the android app it kind of gives a hint but on the windows up it just plain says it's up to date. It seems like it would be fairly simple to fix, check the web for the latest version and at least raise a message that the updates needs to be done manually.

@reolink_333507142684871 Actually seems the auto add option is turned on by default now. If not you could update firmware remotely then factory reset it. Assuming DHCP is used with a fixed IP, it doesn't actually wipe that much. The footage remains and all camera names remain, just the order gets messed up.

@reolink_333507142684871

I found the root cause of the problem, firmware on the NVR needed updating. This is something I checked several times however both the android app and the windows app tell you the device is up to date, plus auto update is enabled. I checked the camera firmware version letter for letter but I didn't do the same with the NVR. I think this is pretty poor on Reolinks part. Wasted many hours of my time and their support staffs time. That could be resolved with a simple change to their software.

I have purchased 3 refurbished rlc-510a. I can find no way to add them to the NVR. When I add them the NVR detects them but shows as connection failed. When I click modify it asks for a username password. Password should be blank, right? I thought maybe it's asking for a new password, but anything I give it fails. I've reset the cameras over and over with no luck. I've put the cams on the Lan and can add them via the app, but I want to connect them to the NVR. I've tried setting a password via the Lan, which works, but then connecting them to the NVR and entering the same password doesn't work. I've tried resetting the cams via the app and then connecting to the NVR with no luck. Basically nothing works.

@diegoisra_839854535635142 plus 1 on this. What a crap thing to need to do. I have never had a monitor or keyboard plugged into mine. One possible workaround is to factory reset the NVR. This can be done remotely.
Edit, just tried it and it didn't work.

@kimchigun you could investigate those things and maybe find a solution, but putting the cameras on the cam side of the NVR solved all problems straight off with no messing about. It reduces config (no need for static IPs), it allows the NVR to set camera IPs and so the NVR knows the camera IPs straight up. To me it's the way the NVR is designed to work and it works better in the app that way. You can also have WiFi cams come into a camera port (I haven't tested that as I don't have any WiFi cams).

@westgate it's possible, I have the NVR connected to a Netgear switch GS728 from memory and then that goes off to a tp link TL-SG1210P that has the cameras connected. I actually added another device, a mikrotik RB791 in the middle to add the VLan tag. Since then it's been 100% rock solid with all the same switches and cables, so not sure what the issue was. I think it just works better with cams on the camera side of the NVR.

@kimchigun I'm not sure what the mechanism reolink uses for discovering cameras that are on the LAN side. Possibly the NVR needs to talk to the cloud to get the camera local IP, or possibly it sends out broadcasts who knows. You'd think it would do that once and then know the cameras IP but seems not. You should try doing it the way I've done it, it works so much better having the cams on the camera side of the NVR. Even just from a config point of view in the app.

@kimchigun the network is fine besides the cameras that were on the LAN side of the NVR. Once I moved them to the camera ports they ran fine over the same cables, same switches etc. Are your remote cameras connecting to the NVR via the LAN port of the NVR or camera port?