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.

@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?

@lafunamor I've found everything today supports VLans. I bought a USB powered $5 switch for one application and it passed VLans.

@joseph_1979 the idea wasn't to put the cameras and NVR on a different subnet, the idea is to make the NVR think the cameras are attached to a camera port and not coming in the LAN port.

I have 3 reolink cameras connected direct to a reolink NVR and 5 cameras connected to another switch that connect back to the NVR across the LAN. The cameras connected direct to the NVR have always worked better, picture comes up quicker, work better in the app etc. One camera on the remote switch would always take 5 goes of pushing the play button to appear. After running it like that for over a year I had the idea to trunk the 5 cameras back to the NVR via a VLan. This way the NVR thinks the camera are plugged into one of the camera ports. Now everything runs brilliantly, all cameras appear as part of the NVR, they all come up first go, config/management of the cameras is better etc. My question, does reolink have some sort of existing functionality to replicate this? Eg some way to set a VLan on the camera and then some way to set a camera VLan on the LAN port of the NVR? The advantage of being able to do it in the reolink side is you wouldn't need managed switches and in my case I could have 1 less device in the network.

For anyone asking why I don't run the remote switch back to a camera port, it's because the remote switch has non reolink devices on it and I only have 1 underground cable running to the remote switch.

Have you tried doing a ”reset” on the E1 camera and setting it up when 4ft from the desired access point? Often, powering off and back on does not ”reset”. That requires sticking something into that tiny ”reset” hole on the camera.

I could try that but I don't think it's a solution. It has connected to the closer AP before but for some reason seems to prefer the AP that is further away. It will jump to the other AP after a day or so.

I have 3 ubiquiti WiFi access points at my house. One of them is in my shed and a WiFi camera is about 4 metres from that access point. There is another access point outdoors that is much further away through 2 layers of tin and a brick wall. For some reason it always connects to the access point further away. The signal isn't that great but it struggles to the grim death to hold on to that access point. I have posted on the Ubiquiti forum but they have said ultimately it's the camera's decision which AP it connects to and likely the WiFi code on the camera is poor. Camera model is E1

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, 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.