Recent content by curtis-r

If you don't have BI MQTT Reset and are monitoring MQTT outside of Home Assistant (such as MQTT Explorer), I suspect the initial alert would stay 'ON'. Of course this may not matter to anyone but probably safest to just have BI reset the MQTT to 'OFF'. But @actran I wasn't aware of the Home...

But then wouldn't that often be a false MQTT in the cases that AI doesn't confirm? Or are you just suggesting this as a test?

Turning off a bunch of cameras had zero impact. MQTT took 12 seconds after AI was done. CPU with only 3 cams active: 2%. CPU with all cameras active: 4-8%. Support @ BI wanted my .dat file, so we'll see what they have to say.

Specifying custom-models on the primary cameras did not help. Still taking 10-18 seconds after AI to MQTT. At least I'm down to 2 seconds for the AI process. EDIT: I'm going to try disabling the 8 other cameras that I'm not using MQTT on to see if it's a CPU thing.

CodeProject is on another box running Docker, and I think it's CPU load is reasonable. The PC running BI is AMD Ryzen 7 5700G, 16GB RAM. Can't imagine the hardware is causing the MQTT delay. The two cam's with the MQTT alerts are both duplicate cam's and I just realized on the primary...

I also have another cam with an MQTT alert with similar lag. Disabling other Actions didn't help. Still large delays before the MQTT's fire. Weird. ]

Changing the MQTT to "vehicle" didn't help. Only 2 seconds for the AI to process, but another 12 for MQTT. Damn.

On one hand, I'm thrilled at the possibility that I could get an MQTT a second or so after motion. I just need to get there! Anyhow, the MQTT is first in line. I'm going to change Required to "vehicle" only and see what happens.

So, much improved with everyone's help. If you see the AI data and the Log, it's <5 sec from motion for AI to confirm a vehicle. But why is it another 8 seconds before the MQTT fires? It is the first item for Alert Actions. Also, why in the global AI in the (grayed-out) custom models, I can...

So far a huge speed improvement. About 5 seconds for AI to process a trigger when it was well over 20 before. I removed the models I'm not interested in. But with ipcam-general AI, why all the red-circle 'X's when it returned >90% chance of being a vehicle? Objects clearly works...

Yeah, I just found the Docker custom-models director, and indeed all five it's been trying to use are there. Instead of deleting them, I wonder if specifying in each camera like this will work. BTW, thanks!

Thanks! Well that explains my confusion on all those .dat entries, and might explain my slowdown, but I haven't specified any models, and the custom model area is grayed-out.

Running Codeproject.AI Sever on Docker with YOLOv5.NET (but also tried YOLOv5 3.1). Do NOT have AI using Main Stream. Applying to motion triggers only for all cams. Codeproject responses typically take 400-1200ms (log attached) but you can see here, it detects A>B motion but AI doesn't...

I have an MQTT motion alert set up with Home Assistant and it's working properly, but I want to try something different and need to do some MQTT testing and I can't get it to work. I'm monitoring Home Assistant and there is not change with a test alert. Twice while I was trying to get this to...