The util actually works, just enabled virtualisation and virtualisation direct i/o and restarted the PC
Do I need WSL 2 installed and enabled?
How is your CPU usage now that you're on Docker?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.
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.Looks to me like it hasn’t detected the car as there’s no box around it.
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.
I don’t know what I’m missing or where the disconnect is coming from. Anyone have any ideas?
- 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
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'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
I think that is it. I removed the timestamp and things seem to be getting recognized properly.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?
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