Posts made by user_645880601444421_645880601444421

If you have performed a reset and it doesn't read the QR, then perhaps try using a different device. Virtually all of my Reolink cameras are unable to "see" the QR code on my Microsoft Surface Duo 2 phone. They have no problems with my other phones

1 If minimized for a while the client will go black, even if hardware decode first is disabled
2 If left open for while it'll sometimes freeze, other times it will go black
3 In either case the client will not restart unless you open task manage and terminate the Reolink processes (I usually need to kill 4)
4 It doesn't remember video quality settings after switching single video to tile and vise versa

I've gone back to 8.8.2. If you click on update it doesn't know 8.8.4 exists, which is an excellent thing since I wouldn't recommend it to anybody, at least not on WIndows

@user_645880601444421_645880601444421 A second related method is to start the client and click on Playback as fast as you can. If you are successful, you'll circumvent initial stream processing and have ample time to disable Hardware Decoding First. Might have to make several attempts before you get good at it

IMHO there is an even easier method. Since the client is crashing trying to process a video stream, simply disable WiFi and/or Ethernet, then start the client. It won't crash since there are no streams available to process. You can then leisurely navigate to Settings to disable Hardware Decoding First.

@reolink-fiona Can you supply a link to 8.8.2 please? There was no need for this before, there is no need for this on the Android and iOS now, and there is no need to flood the router logs with 86,000 events every day

Since installing 8.8.4 any time it is running (anywhere on my LAN) my router reports/logs a never-ending stream of possible DNS re-bind attacks. Here is a small snippet from the log:

Feb 2 18:16:33 dnsmasq[4075]: possible DNS-rebind attack detected: p2p14.reolink.com
Feb 2 18:16:34 dnsmasq[4075]: possible DNS-rebind attack detected: p2pm-abr.reolink.com
Feb 2 18:16:35 dnsmasq[4075]: possible DNS-rebind attack detected: p2p11.reolink.com
Feb 2 18:16:35 dnsmasq[4075]: possible DNS-rebind attack detected: p2p15.reolink.com
Feb 2 18:16:36 dnsmasq[4075]: possible DNS-rebind attack detected: p2p12.reolink.com
Feb 2 18:16:37 dnsmasq[4075]: possible DNS-rebind attack detected: p2p13.reolink.com
Feb 2 18:16:37 dnsmasq[4075]: possible DNS-rebind attack detected: p2p16.reolink.com
Feb 2 18:16:38 dnsmasq[4075]: possible DNS-rebind attack detected: p2p14.reolink.com
Feb 2 18:16:39 dnsmasq[4075]: possible DNS-rebind attack detected: p2pm-abr.reolink.com
Feb 2 18:16:40 dnsmasq[4075]: possible DNS-rebind attack detected: p2p11.reolink.com
Feb 2 18:16:40 dnsmasq[4075]: possible DNS-rebind attack detected: p2p15.reolink.com
Feb 2 18:16:41 dnsmasq[4075]: possible DNS-rebind attack detected: p2p12.reolink.com
Feb 2 18:16:42 dnsmasq[4075]: possible DNS-rebind attack detected: p2p13.reolink.com

I hope you can understand that I do not find disabling the router's re-bind protection and/or whitelisting a slew of reolink web sites that I will never intrinsically trust viable options. Can you provide a link to 8.8.2 so I can get rid of this version ASAP please? My bad for not saving a copy....

@joseph-chircop_497308027822318 I'm not sure I understand. I installed over 8.8.2 and every camera remained populated, i.e. there was no need to add cameras from scratch. Also, all of my preset thumbnails are present and working fine. What am I missing?

@joseph-chircop_497308027822318 Does Reolink offer any IR illuminator recommendations? Brands? Lumens? Optimal wavelength? I have 3x RLC-532WAs that I would consider augmenting with IR illumination - so ideally the illuminator would be very wide angle if possible, say 180 degrees

A related issue - the Windows desktop app does not respond well if at all to arrow finger touches on a tablet (in my case Surface Pros). It would be nice if the app better supported tablet use including point & click

Interestingly enough if the camera supports patrol/scout mode the order of those patrol presets can be rearranged. It should be easy to extend this functionality to the presets

I have 13 cameras, all on 2.4GHz + ~15-25 other devices depending on time of day. My config is

1. Fixed channel
2. Fixed 40MHz BW
3. N only.
4. 3x3 radio (Asus RT-AX86U, soon to be an Asus GT-AX6000 with 4x4 2.4GHz radio

This config is super stable (all devices) except for three cameras. Of those three two will periodically disconnect and then reconnect within minutes. The third one however, would eventually (minutes to a couple of hours) get into some weird state that leaves it unable to send WiFi beacons. This in turn causes the router to think the camera has left followed by disassociation. The router logs show that once this happens the camera never again makes an attempt to rejoin the network. The only cure is to pull the power plug and reboot the camera. You can easily deduce this by looking specifically for DHCP events (request, offer, discover) associated with the troublesome camera's MAC address. Wireshark is great, but it always helps to know what the router thinks is happening as well. I am currently in the process of RMAing this camera (E1 Pro V2). There is such a thing as being TOO close to a router/mesh/AP - exceptionally high signal strength can saturate the device's radio. You might try increasing separation, even if only a foot or two

@user_645880601444421_645880601444421 But... CPU load is actually 6x higher when using Hardware Decode first! I have disabled it on both test PCs. Otherwise no problems found so far

Hardware decoding first is working on my Surface Pro 7 (Iris Plus graphics) but not on my Surface Pro 9 (Iris Xe graphics)

Any plans for a "high power" stand-alone solar panel that could be used with the TrackMix Smart Battery?

I have to protect/monitor a perimeter that is 300+ feet in all directions. During the day this is sometimes possible, but at night it is very unrealistic since the IR/spotlight range is much less. A preset optimized for range during the day doesn't work all that well at night. There is also a seasonal aspect to the challenge - during the summer my cameras can't see as far due to foliage (I have a heavily wooded property) while during the late fall and winter months the cameras can see farther. There is also a time-of-day aspect to the challenge - during the day I ideally want cameras focused on delivery vehicle/persons, cars driving down the road, and people walking on the road - things happening in front of the property - but at night I would ideally like my cameras to focus more on other parts of the property looking for more nefarious activity. I would like this feature addition for my 3x RLC-532WA cameras (which I selected for decent IR/no spotlight range at night) and perhaps my TrackMix Smart Battery - but only if a solar panel becomes available for it (I REALLY hope that is does!).

@user_623346741346376_623346741346376 Seems like the algorithm is missing a key routine: Is the person or vehicle falling from the sky? If yes it's not likely a person or vehicle. I'm being serious - direction of travel seems like an easy thing to determine. My cameras typically don't false alarm on average rain (or snow), but they do false alarm when they see "monster" water drops that fall from the edge of the roof/gutter during a rain. These aren't just large, they are slow moving and easily detected by the camera. I have had success in these cases by moving cameras from under eaves to somewhere else where the monster drops fall behind them. The only camera I have still under an eave is an E1 OD simply because Reolink recommends it be there.

I'm not sure if this is a continuing bug or newly introduced with beta 4.0 but the Windows app 8.8.2 doesn't show the WiFi symbol under the settings "gear" for my 2 RLC-523WA units even though they are WiFi connected (only).