That is your problem. Reolinks do not work well with
Blue Iris and is even worse with DeepStack. Was the YT you watched the hookup by any chance...
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.
Blue Iris and Reolinks do not work well together, but the same principles applies for almost any low end consumer grade camera. It is just Reolinks is one of the more consumer end cameras people buy and come to this site as to why it is pointed out often about. I have a cheapo camera for overview purposes so it doesn't matter, but it exhibits this same behavior even though in the settings I can set an iframe...
This was a screenshot of a member here where they had set these cameras to 15FPS within the cameras (and look some of the sub FPS were dropped to 5 and KEY of 0.25 which is a recipe for missed motion):
Now look at the key - that is the iframes ratio.
Blue Iris works best when the FPS and the iframes match. Now this is a ratio, so it should be a 1.00 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...we have seen people come here where the reo/BI combo missed them pulling their car into their garage, so it would probably miss your little thief LOL.
A key of 0.25 means that if the object can be in and off of your camera view in under 4 seconds, it will miss the motion. Folks have seen the key drop to 0.10 with these cams, which means if an object is not on your screen for longer than 10 seconds, it will miss the motion.
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...
DeepStack probably won't work at all...
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:
Return them if you can.
Here is the unofficial thread showing all the issues folks have with Reolinks. Despite our repeated attempts to ask people to share a good quality night time motion video, as you will see, it doesn't exist. If all you care about knowing is what time something happened, then maybe these are the right cameras if the person is in the field of view long enough, but you will never be able to IDENTIFY them...
Executive Summary: DO NOT be a sheep. Ask what a reviewer can be missing, ask if a reviewer is using hype words to sell the cheapest product. Test your cameras and kits right away. Just do a bench test. Test real world conditions. Test moving suspects. Test at night, test at day. Use a test rig...
ipcamtalk.com
