Posts made by carbonita_23339214035

C1 (1080p resolution version) appears to be failing with snapshot of flickering image attached. Hard reset to no avail. Anyone have a resolution?

Model C1
build 18081414
IPC_36S16MHSM
Cfg version v2.0.0.0
Fw Version v2.0.0.1389_18081414
Annotation-2018-12-14-152836.jpg

FYSA, I brought the RLC-410ws inside, and it started working fine after 2 days, which support confirmed. I've mounted the camera back outside, and will monitor for failures.

One of my RLC-410ws appears to have failed last night, reverting to the default blank admin password after reboots. Installed this camera in June2017, and have been running latest fw for months. Neither hard reset (button press through power cycle per this thread) nor soft reset (windows client) has remedied the issue. Also reformatted card, alas to no avail. Importing configuration via windows client does not restore settings. All other cameras (8) working as expected. Anyone else have this issue?

Build No. build 18081403
Hw No. IPC_3816M
Cfg version v2.0.0.0
Fw Version v2.0.0.1389_18081403

I'm thinking about picking up a Chrome OS system (e.g., Pixelbook or Google Slate), and would like to know if the Reolink Android app runs on this OS. I don't see Chrome OS on the Reolink supported list, but it may just work -- I don't have access to a Chrome OS system to try it out. Has anyone got this combo running?

Web client available via ip address? AFAIK, only windows and macos thick clients available.

SSH to your camera -- you're spoiled by your raspicam Agreed on the robustness of the raspberry pi camera. My AI rpi cam is good for tinkering, comedic for the spouse, but the camera/sensor module is not good for my use-cases. For reolink (AFAIK) there are no APIs, so you're stuck with proprietary reolink clients, but the windows and android apps are OK and have good WAF. There are cameras available (other brands) that get closer to meeting your use-case, which can be CURL'd and scripted. Haven't found a system that has a good sensor (e.g., IMX291) that one can SSH into though.

Message Notifier Pro on Google Play store, with unique emails from each camera works well for my situation.

+1 for support of 802.1x for external PoE cameras. So far, I've implemented a router script to alert for unplug events -- clearly would be better to authenticate each client.

Yeah, in a similar situation here, albeit in my case needing an IMX291 Sony STARVIS sensor for low-light ALPR/ANPR. Any ideas on how you'll integrate the streams? Blue Iris (limited functionality with Reolinks) or an app for each camera manufacturer seems to be the only options.

Pretty clever way of reducing false positives! Watch out for false negatives though -- the things the motion sensing doesn't detect may be a surprise. Dawn and dusk are the toughest times (sunlight turns IR off, but still very dim light for a small camera sensor). I've had some luck placing a boundary area only, say, at the entrance of the driveway -- pets can wander freely in the driveway without alerting the master.

+1. IFTTT integration is available on many other camera brands, even at low price-points.

Is it possible to connect the IR illuminator directly to the camera? I have my cameras powered by POE from switch.

The camera probably (caveat tinkerer) can be opened up and the illuminator (or power wires) routed out of the housing. Waterproofing the modded system would be tricky. Many illuminators are 12VDC powered, as are the RLC410's when powered by the barrel connector. The 802.3af (PoE) is 48V for the 410 though. There are PoE splitters (PoE powered single input, multiple PoE output) I've heard rumours might work. IIRC, PoE powered illuminators exist, but one needs to run more ethernet.

But wait, there's more solutions we have yet to try! I'm thinking an Arduino board with PIR (or microwave!) sensor, which flashes an LED when triggered. This LED flash, in turn, would then (hopefully?) cause the Reolink cam motion sensor to activate.

Mounting a separate IR illuminator and toggling off (or masking) the RLC camera IR LEDs reduces false positives for bugs. Windy/rainy maelstroms are still also mail-storms

Firmware update 1389_180814* visible on download site, with note:

Fixes and Improvements:
• Fixed the FTP issue on the router
• Fixed the DST bug with the playback
• General bug fixes and improvements

Several, C1, 410s, 410ws, 411ws upgraded. http ui and uid access successful again with this fw.

I'd be interested in hearing what the resolution for this is (and curious as to the purpose of the broadcast). A workaround might be to use http client for the cams.

Looks like other IP camera makers have integrated with IFTTT -- would be good if Reolink did as well.

PC client freeze issue appears resolved, after a few days soak time on 2 PCs. Has anyone found docs for interpreting the System State information?

New version of thick client V7.2.2.20 may work (clear is an FTP option)?

Change Log:
1. Supports more Reolink camera models
2. Add "System State"
3. Add "File Type" for FTP Settings
4. Some bug fixes

I was hoping to see a microphone and a Sony starlight sensor (like Argus 2).