Not really adding anything here other than agreement with all of the above, reolinks are nice cameras but they are without question craptastic when used with BI. I wanted to upgrade a couple of my cheaper cameras and unknowingly bought a few reolinks. Nothing but issues.Let me give you an example as to why Blue Iris and Reolinks do not work well together, and why it then makes it even more problematic with a Reolink to try a third party application like AI Tools...just because you saw it on YouTube doesn't mean the person is an expert LOL....between paid testimonial from a camera manufacturer and ad revenue for hits...At least you found this site and the creator of AI Tools that hookup mentioned...
This was a screenshot of a user's Blue Iris status where they had set the cameras to 15FPS within the cameras and they were missing motion:
Even though they have set it for 15FPS, look at what the camera is doing - dropped some down to below 1FPS but none are 15FPS. 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.
Now compare the BI camera status above to cameras that follow industry standards that allow you to actually set parameters and they don't manipulate them. You will see that the FPS match what is set in the camera, and the 1.00 key means the iframe matches:
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 should equal the FPS (something these cameras do not allow you to set), but at worse case be no more than double. This example shows the cameras going down to a keyrate of 0.24 means that the iframe rates are over 4 times the FPS and that is why motion 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...and thus the difficulty it will have with any Deepstack program
This is totally out of control of Blue Iris and there is nothing that can be done about it - it is clearly a limitation of the cameras. All the updating in the world on Blue Iris will not correct this deficiency as it isn't a deficiency of Blue Iris.
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.