Posts made by RIPRengineer

@joseph_1979 why indeed I am!

@riprengineer BTW I was using a PoE injector and then connecting it to the local LAN/router. I tried the UID code in the Reolink windows client software and it can't detect it either. Whatever's wrong with this thing, it's fatal.

@joseph_1979 thanks but I realized why this camera was on the shelf: this was the one that just constantly hard-resets itself every three or four minutes. I tried snipping off the reset button in case it was a physical problem but that didn't help. Into the trash it goes; it's not worth the time to keep fiddling with it.

@joseph_1979 do you mean Network/Advanced/Server Settings in the camera itself? I can't do that. I can't get into the web GUI at all. Even after a hard reset.

FWIW, I did let it do DHCP on its own, no MAC address reservation, at the beginning of this process. That's when I realized I couldn't get in.

I have an RLC-810A camera that is just acting plain weird. Sometimes it'll work fine for a few days, then it just stops working, period. It will grab an IP address from my local router; I have it set to give it a specific IP (like 192.168.99.101, for example) based on the camera's MAC address...and I can see in the router that it IS getting that IP on a DHCP lease. But the web GUI doesn't work; I can't open the IP address in any web browser. It just says "This site can't be reached; (IP address) refused to connect." That's the sort of thing you often see when a device with a built-in web server will only respond to https queries, but the http forwarder isn't working. Still, I tried putting "https" and "http" at the beginning of the IP address and no luck. My Reolink RLN8-410 NVR cannot detect the camera either. Doing a hard reset on the camera does not fix the problem, but I can tell the camera HAS been reset because the router now says the device getting the IP address is "Camera" instead of the name I originally gave it. Any ideas to try?

@riprengineer Oh one more: I used a SanDisk SDSQUA4-400G-GN6MA 400GB Ultra microSDXC card. (UHS-I Memory Card with Adapter - 120MB/s, C10, U1, Full HD, A1)

This page (https://support.reolink.com/hc/en-us/articles/900002154746-The-Battery-Powered-Camera-Starts-Recording-Too-Late) recommends a 16 or 32GB SD Card, which seems absurdly little capacity to me, but does it really make that big a difference in the time-until-recording speed? The camera and SD card are both new, purchased and installed in early November 2022.

@reolink-lorenz Was this feature ever added? I have found that my Argus PT does not actually record anything until the moving object / person is almost completely out of the field of view of the camera. It's not very useful at all. Seems like the lag time between when a person is detected and when recording starts is at least three or four seconds, maybe more like five or six.

For reference, I'm trying to capture video of anyone walking (in either direction, but especially from right to left) on the gravel path in this screencap below. The camera is maybe 8-10ft above ground, which is about as low as I can go without making it too easy for someone to grab at and mess with (and they will). It's mounted to the tree that's just visible in the bottom left, and the path is within 1ft of the tree.

Camera info
UID: 95270004P4PT7Z1X
Build: 22061301
H/W: BIPC_523MIX32M35SD94MP
F/W: v3.0.0.1045_22061301
Details: BIPC_523MIX32M35SD94MPS19E0W911

@crimp-on_62210811129 is the PIR the only means it can detect motion?

Hi folks, I searched a bit but didn't see anything in the forums on this topic (forgive me if I missed it) and the help FAQ's don't really answer this. I have an Argus PT solar-battery wifi camera. It cannot record continuously (boo!) so it only records on motion detection. Problem is, it stinks at detecting motion! Both at night and by day. I have my PIR enabled and Sensitivity at 95 (I tried higher but got many false positives). There are no privacy zones. And no minimum/maximum size settings for detection either. What am I doing wrong here? The camera is pretty new; purchased two months ago from B&H Photo Video. Build No is 22061301, Hardware Ver is BIPC_523MIX32M35SD94MP, Config Ver 3.0.0.0, Firmware Ver 3.0.0.1045_22061301. (I tried to "upgrade manually" and it says this is the most current version available)

Below is a screencap. The yellow zone it detects motion maybe 25-30% of the time, and usually it takes so long to start recording that the object/person has already moved out-of-view. That yellow zone is perhaps 50ft out? The camera is mounted on a pole 14ft up to ensure a wide field-of-view but also because it's the only place where I can reliably get direct sunlight on the solar panel in winter. The red zone is where I'd like it to reach, that's more like 75-100ft. The little "nub" of red is a concrete bridge over a creek. There's multiple solar-powered LED floodlights that clearly illuminate people walking past; but the camera doesn't record them. You'd think the appearance/disappearance of the lights themselves would trigger the motion detector, but they don't. Also, while it's 200ft away, I have a huge infrared floodlight aimed towards this location - you can see it in the shadows cast on the ground. So even if the Argus-PT's I.R. lights were off? Things would still be illuminated at night.

Any suggestions on what I could be doing differently? Other than "move the camera", of course - I can't do that. Partly because there's no spot to really mount it that's closer to the red zone. But even if I installed a new pole there? It would still be in a very tree-shaded area, which is no good for a solar-charged camera like the Argus-PT.

If the Argus could be set to record continuously, that alone would likely solve the problem. Even if I didn't get warnings as often, I could still go back and review the footage manually. But Reolink, for some reason, does not allow this. I don't know why; my camera has never reported anything but 100% battery. Clearly it's got battery power to spare. And I've got a 400GB SD Card in there; plenty of room to record at least a few days' worth of medium-quality video. Can we get a firmware that allows constant recording?