out of curiosity, how many hours have you put into OnGuard so far?It is time for testing of a new Beta version. To get this test version go to: Ken98045/On-Guard. Download the "Code" zip file, and install it from src\installer.
There are quite few changes here some of them are visible, some not.
Here is a partial list of the changes:
1. If you have multiple AIs and one of them goes down, that AI will be taken out of rotation and the app will continue to function. However, one of the things I noticed when testing is that you must give an explicit IP address (192.168.1.2 for instance) for your local computer. Using "localhost" for the IP Address causes this to fail.
2. AIs requests are dispatched to the next AI available in the pool of free AIs. The previous version would go 1 - 5/repeat if you had multiple. This may be a slight performance gain.
3. Pictures are now displayed in date/time order. The previous version showed them in file name order. While it was often the case that this equaled date/time order, this wasn't always the case, particularly with respect to the test images.
4. There is now a display on the main screen of the last time it took the AI to process a picture. This was a request from someone here. It is shown the form of a color coded bar with the specific time overlaying that bar.
5. Several UI bugs were fixed. This includes the fact that the previous version did not update the search object list for an area if you updated an item. Also, things were fixed related to the MQTT settings.
6. Several other bugs were fixed.
7. Objects that are irrelevant to your areas are filtered out as the first step in object detection. For instance, if you never request "potted plants" as an object they will never show up in the UI. You probably won't notice this, but you should be aware of if. If any area in your camera references an object they will be displayed and outlined everywhere.
8. There was a problem where objects were excluded/included within an area if you have pictures at a different resolution from the area in which the defined. While this isn't often the case in "real life" was definitely a problem with the test images. Those images are all at a different resolutions.
9. The database installation included in setup is now SQL Server LocalDB 2016. There were some complaints that the previous 2019 version wasn't appropriate, and I think this is an easier version to install. So, running Setup you may well see the database install/modify itself.
I think that this version is quite stable, and does fix several bugs I noticed while testing. I would like a least a couple of you to test it before I make it a "release" version. The data from the 1.7.x versions is all compatible with this version (1.8.1).
Ken,The data from the 1.7.x versions is all compatible with this version (1.8.1).
I also had another Windows Server 2019 VM on my Hyper-V host so I decided to try it. Well it worked!!! So it turns out that I have some DLL issues on my main Windows Server host that I'll have to sort out. Thanks all.I'm no windows server dude...but couldn't you just to a VMware of windows10 instance just for OnGuard?
Ken, when viewing the image of the first log the bottom portion is not visible so you need to download it to see the object was identified as interesting and the MQTT message was sent.I have more information about the problem I am seeing with 184.108.40.206 were objects are not being identified and no alerts are sent. Below is the portion of the log.
View attachment 81719
The top portion is from an image processed that did not find the person as an interesting object and for the second test I changed the name and ran it through again. There were 2 clips in a row were the person was not identified but in both cases there were identified on the second pass. The log is identical until it gets to "Adding interesting object before 2nd chance ignore: person". Is this were the code is getting hung up? Is this related to AOI where objects are ignored? Below are my AOI for this camera. The bush to the right and the dish at the bottom are AOI that I ignore objects. The red X is were the person was identified with an 81% confidence.
View attachment 81721
Do you see anything that needs modified in the AOI settings?
View attachment 81722View attachment 81724View attachment 81723View attachment 81725
I had a question above about the snapshot interval. I changed it to 1 to see if that would make a difference. Below are those settings.
View attachment 81726
Once a camera stops logging objects as interesting it does not get corrected until an OnGuard restart or a AIO setting change.
I am running 1.8.1 for a single camera on a laptop over wireless so I don't have enough data to see if this problem exists in the beta.
If your object size and contrast are low check the make time and object must travel X pixels. Try lowering 1 or both of those. Do you have more than 1 zone setup? If you do check if you use zone crossing. I know some of the tutorials say not to use zones but I don't want the camera to trigger from motion in some areas so I adjust the mask for the zone to ignore those areas.Anyone have good settings on the Blue Iris side for this type of situation? My front door camera faces directly down the sidewalk leading up to my house. I easily get snapshots taken of people walking back and forth, left to right or right to left in front of my house, but when someone walks straight down the sidewalk to my house, or straight away, blue iris doesn't seem to detect this as motion. I've already made the settings almost as sensitive as possible, but these two cases don't seem to trip the trigger. So anyone approaching or leaving doesn't even have a chance to get analyzed by deepstack since no screenshots are taken
left <> right motion is much easier to detect. Straight incoming/outgoing is more challenging. Especially at night.Anyone have good settings on the Blue Iris side for this type of situation? My front door camera faces directly down the sidewalk leading up to my house. I easily get snapshots taken of people walking back and forth, left to right or right to left in front of my house, but when someone walks straight down the sidewalk to my house, or straight away, blue iris doesn't seem to detect this as motion. I've already made the settings almost as sensitive as possible, but these two cases don't seem to trip the trigger. So anyone approaching or leaving doesn't even have a chance to get analyzed by deepstack since no screenshots are taken
Sorry I'm late getting back to you. I did try the latest (220.127.116.11-- which is not yet a release) appears to work with both. Right now I'm trying to catch up with messages and get 18.104.22.168 released plus working on 2.0.
Yes. I looked at it briefly and it doesn't seem too bad, but you are the first to ask so it isn't a super high priority. Right now I have some higher priority items to work on. Right now that means making a release of 22.214.171.124, and making sure it is stable.any chance for telegram integration ?