[tool] [tutorial] Free AI Person Detection for Blue Iris

Being really lazy I’ve found a HP util which claims to be able to make changes to the BIOS, will be useful if it works.
 
  • Love
Reactions: neile
The util actually works, just enabled virtualisation and virtualisation direct i/o and restarted the PC

Do I need WSL 2 installed and enabled?
 
The util actually works, just enabled virtualisation and virtualisation direct i/o and restarted the PC

Do I need WSL 2 installed and enabled?

You don't but since you're doing install/upgrades anyway I would. Make sure you're on Windows 10 version 2004, then install WSL2 and enable it. You may want it down the line and it is amazing :)
 
Right have DeepStack running within Docker, can access the DQAI webpage using localhost and the port number but I'm getting the following errors in the log file for AI Tools?

[22.06.2020, 15:46:56.117]: Starting analysis of C:\BlueIris\AI-Input/AI-Drive1_C.20200622_154656086.jpg
[22.06.2020, 15:46:56.123]: System.IO.IOException | The process cannot access the file 'C:\BlueIris\AI-Input\AI-Drive1_C.20200622_154656086.jpg' because it is being used by another process. (code: -2147024864 )
[22.06.2020, 15:46:56.129]: Could not access file - will retry after 10 ms delay
[22.06.2020, 15:46:56.157]: Retrying image processing - retry 1
[22.06.2020, 15:46:56.163]: (1/6) Uploading image to DeepQuestAI Server
[22.06.2020, 15:46:56.174]: (2/6) Waiting for results
[22.06.2020, 15:46:56.178]: (3/6) Processing results:
[22.06.2020, 15:46:56.184]: System.NullReferenceException | Object reference not set to an instance of an object. (code: -2147467261 )
[22.06.2020, 15:46:56.188]: ERROR: Processing the following image 'C:\BlueIris\AI-Input/AI-Drive1_C.20200622_154656086.jpg' failed. Failure in AI Tool processing the image.
 
Right got it working, I thought that if I didn’t specify the type of detection it would just work but it need VISION-DETECTION set to true.

Struggling to now get docker to auto start, works fine when I’m logged on, tried using NSSM to create a service to start the desktop but I then can’t access the DQAI web server.
 
Right got it working, I thought that if I didn’t specify the type of detection it would just work but it need VISION-DETECTION set to true.

Struggling to now get docker to auto start, works fine when I’m logged on, tried using NSSM to create a service to start the desktop but I then can’t access the DQAI web server.
How is your CPU usage now that you're on Docker?
 
When I looked it was at around 35% so much better but I’ve not managed to get it to auto start after which I’ll start doing some proper testing and monitoring.
 
  • Like
Reactions: pmcross
I'm finding that most of the time the system is tagging things as false alerts even though they are not. Here is one example of a car driving by. Why would that be happening

1592849785848.png
 
Managed to get it all working with docker and the container now auto starting when windows boots.

How can I reset the stats so that I can now start to check and monitor?
 
Looks to me like it hasn’t detected the car as there’s no box around it.
Yes. That's exactly my point. I would have thought the system would pick up cars and label them as such, however the vast majority of the time, they are labeled as false alerts.
 
I’ve had something similar when playing around with it, it flagged most of the cars in the pic except the ones further away which appeared smaller.
 
I think I’ve finally gotten AI Tool to process and trigger consistently and within a reasonable time. However I’m still having issues with MQTT.

So my MQTT is on a different server (Synology NAS) than Blue Iris and AI Tool (Windows Server). My MQTT topics are received by NodeRed and Home Assistant.

  • MQTT test button from setup works
  • AI Tool triggers the cameras to record with motion
  • MQTT test button from individual camera works

    An AI Tool trigger from motion DOES NOT trigger the MQTT payload, or push notifications for that matter
I don’t know what I’m missing or where the disconnect is coming from. Anyone have any ideas?

UPDATE: I set up an MQTT for some other cameras I have which are not running on AI Tool. The MQTT triggered as it should. So since it is not a connection between Blue Iris and MQTT it must be related to AI Tool. I am currently using AI Tool 1.64 because 1.65 was causing errors writing to history.csv.

@GentlePumpkin do you have any ideas why AI Tool would trigger a recording in BI but somehow prevent alerts using MQTT or push notificaiton?

I was able to fix my MQTT &push notification issue! I'm not sure if this is the only setting that needed changed but it's the one that worked. I unchecked motion zones and only checked Extern in the alert page. This got everything working.

Screen Shot 2020-06-22 at 6.01.39 PM.png
 
  • Like
Reactions: neile
I'm finding that most of the time the system is tagging things as false alerts even though they are not. Here is one example of a car driving by. Why would that be happening

View attachment 64375

It could be that the car is obscured by the timestamp so Deepstack doesn't recognise it. Can you disable the time stamp or move the camera a bit so it's not over that section?
 
  • Like
Reactions: Tanaban
It could be that the car is obscured by the timestamp so Deepstack doesn't recognise it. Can you disable the time stamp or move the camera a bit so it's not over that section?
I think that is it. I removed the timestamp and things seem to be getting recognized properly.
 
Hi everyone,
First of all thank you @GentlePumpkin for creating this amazing tool.

I was following Robs (The Hook Up) video


and got it working on a Ubuntu 20.04 Desktop Laptop with Docker and Homeassistant.
I wanted to move it to my new server and no matter what I try I cannot get it to work.

1. Case Proxmox Server - Ubuntu Server - Docker - Deepstack
2. Case Proxmox Server - Homeassitant - Docker
3, Case Windows 10 (newest) where Blue Iris is installed as localhost

In all cases when I chose the wrong Ai I see a connection from the too to the Server (in all 3 cases) but when I try the right detection api

[24.06.2020, 00:51:13.299]: Starting analysis of D:\aiinput/drivewaysd.20200624_001903007.jpg ## local storage ##
[24.06.2020, 00:51:13.305]: (1/6) Uploading image to DeepQuestAI Server
[24.06.2020, 00:52:53.315]: System.Threading.Tasks.TaskCanceledException | A task was canceled. (code: -2146233029 )
[24.06.2020, 00:52:53.330]: ERROR: Processing the following image 'D:\aiinput/drivewaysd.20200624_001903007.jpg' failed. Can't reach DeepQuestAI Server at 192.168.0.81:5000

UPDATE: I found the error which might help others.

I tested this morning again a bit more, and I can install it on my Windows workstation and it works, so I assume it has something to do with the Virtualisation and Hardware Settings the Deepstack Server needs.

Solution:
For those who run Deepstack in a virtual enviroment like Proxmox.
When creating the machine for example Ubuntu with Docker and Deepstack in Docker need to choose the CPU they have or want to emulate and not just kvm64.
Deepstack seems to atart the analysis with hardware commands to the cpu and needs the architecture. When switched from kvm64 to Sandybridge (in my case the Intel CPU) it works.


Thanks
Arthur
 
Last edited:
  • Like
Reactions: Spaldo
When I looked it was at around 35% so much better but I’ve not managed to get it to auto start after which I’ll start doing some proper testing and monitoring.

Just wanted to see if your CPU usage has stayed down since switching to Docker? I’m considering changing mine to the same but I was waiting to see your findings.


Sent from my iPhone using Tapatalk
 
Just wanted to see if your CPU usage has stayed down since switching to Docker? I’m considering changing mine to the same but I was waiting to see your findings.


Sent from my iPhone using Tapatalk

Yes it is, it can spike to 40% occasionally but I still only have 3 of my cams configured at the mo. I’ve also realised yesterday that when I cloned the cams I for some reason decided to remove the sub stream settings so am planning on making my 3 cams live, they’ve been sort of running as a test up to now. So hopefully setting the sub stream will hopefully lower the CPU usage a bit more.
 
Just configured 3 of my cams and switched them over to fully trigger on AI detection and switched all the clones to now use substreams.

Will monitor over the next few days to make sure that the cameras trigger as expected.

I have 2 queries, the first is that the file history.csv doesn’t appear to get written to, so if I restart the AITools service all previous history is lost and secondly, the Stats tab, how can I reset those stats back to zero so that I can monitor and reset over the next few days?