The saga with Reolink 4k cameras and Blue Iris continues
I have two RLC-810A and two RLC- 820A cameras and they were installed yesterday. I am running Blue Iris on Windows 10 under proxmox on an i7 NUC allocating 8gb ram and 2 sockets, 2 cores. I have Open Media Vault on the same machine sharing a 10tb HDD using SMB. I also have HA OS on it.
The good news
-
All the cameras work well with PoE, even the one that has 120m run of CAT5e cable. I am using a tp-link TL-SF1005P switch which supports up to 250m POE transmission.
-
I have a very clear image when using the Reolink app on the phone or OSX or directly on a browser using the IP address.

-
I have installed the Home Assistant Reolionk integration on HACs and I can get a camera image onto my HA dashboard and have several entities including motion sensors working.
The bad news
Blue Iris looks awesome, I really want to get it working but…
1. The still images look great, but when there is motion, much of the still areas get greyed out or I get lots of pixels over the motion.
Here is a video from the gate
2. I set up the cameras using the settings recommended by this guy https://bit.ly/3jh89AC on the Blue Iris forums and they made things better but still getting lots of problems. The user sbaker1106 later recommends contracting Reolink for beta software which I have done.
3. Under the beta software things are worse, I can’t get a “clear” stream form the cameras at all, not even on a browser. This is what I get using the Reolink app when viewing the clear stream
I have contacted Reolink Support and none of their suggestions so far have helped.
On a slightly side note I have got nowhere getting Frigate working either, but I’m trying to get Blue Iris fixed first.
I would love to hear from anybody that has got these cameras working with Blue Iris with suggestions.
My next step is either to
-
replace the cameras completely or give up on Blue Iris and buy a reolink NVR. This would be a shame as Blue Iiris seems to have good functionality (and I have paid for it!)
-
bin the cameras and replace them (I mean sell, return or whatever)
Any more thoughts hints suggestions would be welcome.
30/10/21
Update –
I have gone down the path of using Frigate rather than Blue Iris.
I have detailed my solution here.


Did you find a solution? I have exactly your problem with my RLC-410W.
Unfortunately not, I am going down the path of using Frigate instead, to be honest I wish I had bought different cameras/
I’m having the same issue with Blue Iris as well for these cameras, but I did get this to work for frigate. I hope my yaml will help some people here. Good day!
———
cameras:
kidcam:
ffmpeg:
inputs:
– path: rtsp://REDACTED:REDACTED:554//h265Preview_01_main
roles:
– record
– path: rtsp://REDACTED:REDACTED:554//h264Preview_01_sub
roles:
– detect
– rtmp
detect:
width: 640
height: 360
fps: 4
motion:
mask:
– 0,0,1920,0,1920,389,0,386
– 0,0,0,821,177,686,455,480,441,0
– 1873,1015,1876,1059,1732,1059,1738,1008
record:
enabled: True
retain_days: 7
events:
retain:
default: 10
objects:
track:
– person
snapshots:
enabled: True
timestamp: False
bounding_box: False
crop: False
height: 175
retain:
default: 10
objects:
person: 15
Hi Jason,
Thank you so much for your message!
I also gave up on Blue Iris and went down the frigate route and now have it working really well.
I wanted to save 24/7 to an external HD so had to reinstall home assistant on Debian and I have Frigate on docker/Portainer rather than supervisor.
It would not have worked on my previous install with a VM on proxmox.
Maybe I should do an update to the blog post !