DeepStack: Alert cancelled [occupied] 713ms
I have only reolink camera... !!!!
so blue iris is just not the right NVR for it if I read this correctly?
(apart from dropping my camera to the bin, any fallback solution?
and other screenshot of cam parameters. thoughts?
Also just tried a manual trigger and got the message:
DeepStack: Alert cancelled [occupied] 713ms
OK- Motion settings isn't the problem, you need to match FPS with iframe. So if you are running 15FPS, then the iframes need to be 15.
But I see that many of your cameras are dropping down to 6 FPS and a KEY of 0.13. What FPS and iframes did you set in those cameras (if the camera even lets you adjust)?
What brand(s) of cameras are they?
If the cameras are dropping FPS and increasing iframes regardless of what you tell it to do, not much you can do in the BI motion settings to catch all the motion.
The biggest issue is your KEY frames are horrible and you are probably missing motion and do not even know it. KEY should be 1.00 which means FPS and iframes match.
A KEY of 0.13 means if an object can pass through your field of view in 8 seconds, you could miss it completely. BI recommends a KEY no less than 0.5 but suggests 1.00. I suspect you are using cameras that are changing it to what they see fit to try to give a bright static image. But that is another issue to tackle later LOL.
The most famous cameras that do this switching of FPS and iframes is Reolink.
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):
View attachment 100542
Now look at they 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...try to do DeepStack 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...DeepStack probably won't work at all...
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:
View attachment 100544
Sms failure cannot be related to poor detection. Poor detection would result in alert or trigger failure. If BI sends the email to your mobile provider and you dont get it, its not BI related. To get your keyframe up to 1 you need to match your iframe interval to your frame rate.I am curious to learn more about this as I have been having issues with sms alerts not going through and find that it may be related to poor detection and now your feedback on frames and keys is an area to look into based on your description of the possible effects. I am running amcrest and annke cameras and one Logitech C920 and until recently the alerts were being sent but now it seems like BI and or DS are not seeing anything and I am seeing a ton of DeepStack: Alert cancelled [occupied] in my log. Only 2 cameras are sending text alerts one is an amcrest and the other is the logitech (circled in red) , I tried adjusting the camera settings to see if I can get a better ratio than .50 but this seems to be the best I can get at the moment. Any help would be greatly appreciated.
View attachment 118570
Just got the iframes to 1.00, so am happy on that. As for sms I get the texts when I do the test message so that to me says the end to end piece is working.Sms failure cannot be related to poor detection. Poor detection would result in alert or trigger failure. If BI sends the email to your mobile provider and you dont get it, its not BI related. To get your keyframe up to 1 you need to match your iframe interval to your frame rate.
If BI is sending SMS too quickly, your mobile provider thinks it is SPAM.
Once BI sends the SMS message, it is out of BI control. It is confirmed above that BI sent the SMS.
To further prove it, go to your email that you are using to have BI send out the SMS messages and look in the sent folder and you will see that your email provider sent the SMS, but it was then blocked by your mobile provider.
If it isn't showing in the BI log, then there is an issue in your setup for that particular camera.
There are lots of threads here where this issue with SMS is happening. It comes and goes. Sometimes mine are instant with the push notification, and sometimes they are hours later or not at all. Many of us here gave up on that being a reliable alert method.
Either cough up the $10 for the BI app and get push notifications or cough up $5 for the Pushover app to send you push notifications. That is the only way to ensure your mobile provider doesn't block it as SPAM.
The Alert cancelled [occupied] means that there is an object in your field of view that is stationary (occupied) so it isn't triggering, something like a parked car.
Good move to another product, if you were a nasty demanding prick in your emails as in your post, I would not expect a reply. You spent 60 dollars or less on the software, stop pretending you paid a thousand. In the VMS space 60 dollars is nothing. PLEASE look at other vms options. Buy them tell us how they worked out for you. You might be shocked at the cost, even more shocked by the cost of support. Blue iris is run by a one person and as of late an additional tech support person. They dont become your bitch because you paid 60 bux. You have an obligation to read the manual. Your initial post (falsely implying an sms issue) and your follow up screenshot where you dont provide any shots of your alert settings are indicative that you dont understand how alerts work and have not read the help file. Its not a blue iris issue, its a user settings issue. Delete the cameras and start over.Thanks for feedback. I am not willing to put any more $$ into BI products until they get off their a**es and start honoring their tech support responsibilities. I submitted an issue with them a week ago with a follow up after 3 days and they still have not responded. I like the Pushover idea and may give that a try and see how it works. As I am receiving texts from 3 other cameras I dont see their being an issue with the provider or the mail server (the domain and services are owned/controlled by me) from which the sms emails are sent so I am still leaning towards a local issue. I will be posting screen shots of the alerts and trigger settings which I hope may shed some light on the issue.
View attachment 118596
Good move to another product, if you were a nasty demanding prick in your emails as in your post, I would not expect a reply. You spent 60 dollars or less on the software, stop pretending you paid a thousand. In the VMS space 60 dollars is nothing. PLEASE look at other vms options. Buy them tell us how they worked out for you. You might be shocked at the cost, even more shocked by the cost of support. Blue iris is run by a one person and as of late an additional tech support person. They dont become your bitch because you paid 60 bux. You have an obligation to read the manual. Your initial post (falsely implying an sms issue) and your follow up screenshot where you dont provide any shots of your alert settings are indicative that you dont understand how alerts work and have not read the help file. Its not a blue iris issue, its a user settings issue. Delete the cameras and start over.
Thanks for the info. Yes I checked the log and those that are not working correctly (ones that DS has ID'd with required % confidence) dont show the sms attempt. I am going to start a new log and capture data over next day or so and do a last sanity check and confirm all is as it should be. I appreciate the community putting a second set of eyes on things as I tend to get tunnel vision from the back and forth within the system or get info on something I wasnt aware of.Yeah based on your copy/paste above, it is a local issue if BI isn't even sending out the SMS. Do check the actual .TXT file though and not the one that pops up in BI status page - the .TXT file will have more info, so make sure that it doesn't show a SMS being sent.
I suspect your occupied objects are probably sending out alerts at night? If so, that is a common problem. Every vehicle that passes shines a different hue of headlight, angle, etc., so even though you know the car isn't moving, to DS it looks different.
If it is happening in the day time, then would need to see some fields of view to determine why that is - perhaps object too far out of center of frame?