Okay, I've found the issue and adding it here in case someone runs into this in the future. On this system, I was still running the older 0.18 code and when I upgraded to 0.19, it fixed the problem partially. It seems in newer versions of BI (certainly in 5.9.9.73, but NOT in 5.9.9.33), the AI handling was changed slightly.
Essentially, if you have object detection enabled at the BI main settings, and even if you did not enable it on a camera, it is still do it, and the results will be sent via the &JSON macro. In 0.18 of the ALPR Database, it would result in the error above, but in 0.19, it handles it fine. If you have BI burn the detection into the image, you will see:
View attachment 229371
The fix is:
1) Upgrade to 0.19 of ALPR Database, and/or
2) On BI, turn off object detection at the main settings menu, and maybe enable it the individual camera if you need it, but not on your ALPR camera.
Recent similar GitHub issue: getting error in alpr · Issue #72 · algertc/ALPR-Database
Like you mention, and I say in that GitHub issue, I made changes that seem to fix part of this in the last update. Seems like I still need to make the parsing more robust. It’s the multiple plate numbers in one image part that makes it a bit tricky. Shouldn’t be hard to fix though.
If you could paste the AI_dump that causes the issue, that would be very helpful.