It is a known fact that Reolink doesn't play well with BI. Plus they don't completely follow the ONVIF standard.
There are videos here of someone pulling their car into the garage and the reolink camera completely missed it.
This was a screenshot of a member here where they had set Reolink cameras to 15FPS 15 iframes within the cameras:
Now look at they key - that is the iframes.
Blue Iris works best when the FPS and the iframes match. Now this is a ratio, so it should be a 1 if it matches the FPS. The iframes not matching (that you cannot fix or change with a reolink) is why they miss motion in
Blue Iris and why people have problems. This is mainly why people are having issues with these cameras and there are many threads showing the issues people have with this manufacturer and
Blue Iris. It is these same games that make the camera look great as a still image or video but turn to crap once motion is introduced.
The
Blue Iris developer has indicated that for best reliability, sub stream frame rate should be equal to the main stream frame rate and these cameras cannot do that and there is nothing you can do about that with these cameras... The iframe rates (something these cameras do not allow you to set) should equal the FPS, but at worse case be no more than double. This example shows the cameras going down to a keyrate of 0.25 means that the iframe rates are over 4 times the FPS and that is why motion detection is a disaster with these cameras and
Blue Iris...
A value of 0.5 or less is considered insufficient to trust for motion triggers reliably...try to do CodeProject AI and it will be useless...
Compounding the matter even worse...motion detection is based on the substream and look at the substream FPS - they dropped down to below 6 FPS with an iframe/key rate of 0.25 - you will miss motion most of the time with that issue... A KEY of 0.25 means any object that can be in and out of the field of view within 4 seconds may be completely missed.
We have seen people come here with a KEY of 0.1, which means any object that can be in and out of the camera view in under 10 seconds will be missed as a trigger.
Blue Iris is great and works with probably more camera brands than most VMS programs, but there are brands that don't work well or not at all - Rings, Arlos, Nest, Some Zmodo cams use proprietary systems and cannot be used with
Blue Iris, and for a lot of people Reolink doesn't work well either.
Now compare above to mine and cameras that follow industry standards that allow you to actually set parameters and they don't manipulate them. You will see that my FPS match what I set in the camera, and the 1.00 key means the iframe matches: