I'm having trouble getting Blue Iris to recognize incoming cars on my (long) driveway coming straight toward the camera. It will get them, but not until they are about 100++ pixels high. I've yet to come up with settings that will work for that.
Yet Another Free Extension for Blue Iris Adding AI Object Dectection/Reduction in False Alarms/Enhanced Notification of Activity/On Guard
- Thread starter Ken98045
- Start date
I think that I have identified and fixed part of the problem where it stops identifying objects. I was finally able to re-create that here. It is related to a failure in the Microsoft engine that watches the directory for new picture files. Version 1.8.2.2 (not a release, but I'm working on it) addresses the issue by increasing the buffer size (pre-allocated memory) that holds data that engine uses. That should at least help, and may well completely fix the problem. I am also working on a little more comprehensive fix that recreates the watching engine if it breaks. I may also put in the capability to have On Guard periodically post an image to the watched folders to make sure that the engine is still active. That may be a little longer term.
Vettester
Getting comfortable
- Feb 5, 2017
- 799
- 814
2021.02.12 16:57:09:1869 - 1 interesting objects found in file: D:\AI\AI_Entrance2.20210212_165708605.jpg
2021.02.12 16:57:09:1889 - MQTT Message Sent
2021.02.13 17:10:01:8873 - Out of memory.
2021.02.13 17:10:18:3619 - An AI at Port: 8090 Died Or Was Not Found - Remaining: 1
2021.02.13 17:10:18:3619 - The AI List Is Empty!
2021.02.13 17:10:27:9278 - The AI List Is Empty!
2021.02.13 17:10:31:0914 - Exception of type 'System.OutOfMemoryException' was thrown.
This is why I reboot my Blue Iris / OnGuard / Deepstack AI machine at least once a week. Maybe v2.0 fixes as Ken said something about increasing a memory value.
This is v1.8.2 (not 1.8.2.2).
2021.02.12 16:57:09:1889 - MQTT Message Sent
2021.02.13 17:10:01:8873 - Out of memory.
2021.02.13 17:10:18:3619 - An AI at Port: 8090 Died Or Was Not Found - Remaining: 1
2021.02.13 17:10:18:3619 - The AI List Is Empty!
2021.02.13 17:10:27:9278 - The AI List Is Empty!
2021.02.13 17:10:31:0914 - Exception of type 'System.OutOfMemoryException' was thrown.
This is why I reboot my Blue Iris / OnGuard / Deepstack AI machine at least once a week. Maybe v2.0 fixes as Ken said something about increasing a memory value.
This is v1.8.2 (not 1.8.2.2).
There is a new release version 1.8.2.2 at: Release On Guard Security Assistant Version 1.8.2.2 · Ken98045/On-Guard
This is the formal release of version 1.8. It contains multiple bug fixes and a few new features. It should be much more stable than the 1.7.x releases.
This is the formal release of version 1.8. It contains multiple bug fixes and a few new features. It should be much more stable than the 1.7.x releases.
If you use "localhost" for the AI when one instance dies they all will. When you use an explicit IP Address fail-over should work as long as DeepStack isn't completely buggered. The 1.8.1+ releases all suggest that. However, if I recall correctly you weren't able to use localhost anyway?
My DeepStack has been very stable overall. I rarely see an instance die. I also very rarely restart the services (other than when testing or I reboot the PC, but maybe that is a about once a week or so).
Vettester
Getting comfortable
- Feb 5, 2017
- 799
- 814
Vettester
Getting comfortable
- Feb 5, 2017
- 799
- 814
Assuming you are using Mosquitto as your mqtt broker, have you noticed an excessive number of Home Assistant users in BI when you see these out of memory errors?
I have been working on Version 2.0. While it offers a few new features, mostly things have changed in the technology used. The reason for this change is that it offers more long term flexibility and enhances development features. Incidentally, it also adds support for use in Linux, and probably Android. While nobody has been requesting this, it is a nice side effect of the change, and maybe there is a hidden demand.
One of the more useful new features is the ability to get notified via email and MQTT if all your DeepStack servers die. Using MQTT you should be able to close down any non-functional AIs and recreate good ones. Version 2.X also offers the ability to optionally store settings using XML. While most of you won't care about that it is necessary for Linux/Android support since those platforms don't support the Windows Registry (where the current settings are kept). Using XML also makes it easy to copy settings from one computer to another.
I am doing some final testing of Version 2.0, and I expect to release it within the next day to two on a test basis.
I'm sorry, but I have been away from this forum for a few weeks, and I haven't done much in the way of 1.X support. Once I get done with Version 2.0 I will be back here more often and will be able to (hopefully) support both the 1.8.X and 2.x versions. The change to Version 2.0 was much more time consuming than I expected.
Note that while I will continue to support 1.8.x for a few months all new features will be in the 2.0 branch after it is released.
Last edited:
Linux would be nice future aspect, for sure. Less programs using CPU on my Blue Iris machine the better. Android? What use would putting OnGuard on a smartphone do? Or am I missing something?
I like the notification of Deepstack offline idea, especially via MQTT so my Home Assistant can act upon it.
Android -- because it can be done (I think) more than anything. While I wouldn't want to run it on Android full time, it might be nice to be able to use it to fix something that has gone wrong. It would be more useful on a tablet than a phone, but I haven't had a chance to try it yet.
Vettester
Getting comfortable
- Feb 5, 2017
- 799
- 814
Hi Ken, I updated to the prerelease of 2.0 yesterday and today I noticed a couple of errors, The first occurred after I added a new camera and try to use either the Snapshot or Continuous options under "Live Image - On Demand".
The second error occurred after I closed out the first error. Closing out the second error shuts down the application,
The SQL support in the new tools no longer support "async" options in the database connection string/settings. You will need to go to Application Settings and press the Use Default Settings button under SQL Connection String. Alternatively, if you have a custom SQL setup you will need to remove references to "async" in the connection string.
The problem with the Snapshot or Continuous Video is one I can't replicate, but I guess I can kind of/sort of see how it could have happened. I will update the executable shortly.
Well, it looks like Linux, etc. will be much more difficult than I thought. That will be on hold for the foreseeable future. Originally it looked like it would be a more-or-less free feature.
The pre-release on GitHub has been updated. The Snapshot/Video problem should be fixed.