No, that does not need to be checked unless you're using the plate recognizer app.
Full ALPR Database System for Blue Iris!
- Thread starter algertc
- Start date
TheWaterbug
Known around here
My last .dat file was saved on 01/16/26, which is the day everything stopped working, so it looks my problem is relatively early in the process, because I'm not even generating them any more.
TheWaterbug
Known around here
Correct. I checked all 3 LPR cameras on this system, and all 3 had this box un-checked:
Somehow this setting didn't make the migration from 5.9.9.99999999 to 6.0.
I've checked this box on all 3 cameras, and now I'm getting AI alerts, but they're finding nothing. But at least one step is fixed.
I need to fix my focus, but I would have thought it would make this plate on the trash truck:
But I got:
Code:
[
{
"api":"alpr",
"found":{
"error":"Yolo returned null.",
"inferenceMs":0,
"processMs":0,
"analysisRoundTripMs":13,
"success":false,
"moduleName":"Object Detection (YOLOv5 .NET)",
"moduleId":"ObjectDetectionYOLOv5Net",
"command":"custom",
"requestId":"f85de88f-0175-49ba-b760-5989a6f0cd09",
"processedBy":"localhost",
"timestampUTC":"Sat,
31 Jan 2026 14:59:04 GMT"}
}
]TheWaterbug
Known around here
Thanks! This was probably the problem. The "License Plates" box was unchecked on all 3 cameras.
So there were multiple settings that didn't survive the migration from 5 to 6. Anyone know how Ken stores camera configs? The configs are not readable in a text editor, so it's not XML or JSON or anything like that. It is something fragile like StucturedStorage?
TheWaterbug
Known around here
I have plates again!!!!
Thanks!
I'm having a hard time understanding BI's internal workflow on AI in general and for LPR in particular. "License plates" appears in two different places in the general Settings and two other places in the camera-specific settings, plus LPR needs to be enabled in the 3rd-party CPAI, plus specifically configured in the Alert.
It would be nice to have some sort of flow-chart illustrating the setup from start to finish, and what to look for to confirm each step before proceeding with the next. If I knew more, I'd write one
Thanks!
I'm having a hard time understanding BI's internal workflow on AI in general and for LPR in particular. "License plates" appears in two different places in the general Settings and two other places in the camera-specific settings, plus LPR needs to be enabled in the 3rd-party CPAI, plus specifically configured in the Alert.
It would be nice to have some sort of flow-chart illustrating the setup from start to finish, and what to look for to confirm each step before proceeding with the next. If I knew more, I'd write one
I’m a bit out of the loop currently. Does this mean the new built-in AI in Blue Iris also do license plate recognition/reading, and keeps the ALPR database workflow in tact?
TheWaterbug
Known around here
Is there a list of things that change and things that don't change when we swap AI engines?
TheWaterbug
Known around here
Hmm. Then it's strange that certain settings don't survive the migration, since they're named keys that should map 1:1.
Not that I'm aware of. I just know that when I first Installed BI6 there were some settings that had changed so I went through all of my cameras and verified everything. Unfortunately I didn't document the changes I found.
TheWaterbug
Known around here
LOL! I just noticed that you're using the built-in YOLOv8, whereas I'm using CPAI and its YOLOv5. I copied the rest of your settings, and it's working, so maybe it's as simple as that one radio button for AI engine.
I'll wait until I collect a Monday's run of plates, and then switch and see if it still works.
I'm actually using yolov10. I have found it significantly outperforms yolov5.
TheWaterbug
Known around here
Do you have to specify YOLOv10 somewhere else?You might want to check all of your other settings as well.
