Codeproject Blue Iris Verified -

| Problem | Solution | |---------|----------| | No checkmark ever | Check Blue Iris log (window → Log) for "AI: timeout" | | AI module not running | Open CodeProject.AI dashboard → restart module | | High CPU | Switch to GPU or reduce camera AI triggers to every 5th frame | | Detects everything as "object" | Update custom models → download ipcam-general from CodeProject.AI module library |

The "verified detection" workflow in Blue Iris is a two-stage process: codeproject blue iris verified

Only if the AI confirms a relevant object does Blue Iris register a "verified alert" and perform actions such as recording, push notification, or email. This architecture reduces system load by 80–90% compared to constant AI analysis, while simultaneously eliminating virtually all false positives from natural motion. | Problem | Solution | |---------|----------| | No

Blue Iris alone uses pixel-based motion detection. A cloud passing by creates a massive "motion event." A tree swaying triggers a recording. This wastes硬盘空间 and trains you to ignore notifications. Only if the AI confirms a relevant object

CodeProject.AI runs locally on your Blue Iris machine (CPU, GPU, or even a Coral TPU). It analyzes the triggered motion images and asks: "Is this a human? A car? A tumbleweed?"

The benefits of a verified setup include:

Why use it? Without AI, a moth, rain, or light change triggers recording. With CodeProject.AI, you only get alerts for real threats.