Full ALPR Database System for Blue Iris!

Just set this up - had a few alerts in BlueIris but not seeing anything in the ALPR Database just yet, followed the instructions shown here: GitHub - algertc/ALPR-Database: Fully-Featured Automated License Plate Recognition Database Platform for Blue Iris + CodeProject AI Server for the docker container setup.
In the web interface, the MQTT/HTTP section is not modified, do I need to do anything here? i.e. do I need to fill out MQTT Broker URL/IP?
I edited the Blue Iris Configuration to point to the Blue Iris IP address and port number, that should probably be added to the instructions.

In the logs, I see this:
4/29/2025, 12:08:41 PM [INFO] Checking IP: 172.19.0.1 <- this is not an IP in my local network, did I miss a setting somewhere?
 
Last edited:
Ok I saw a plate come through in the logs but it's not hitting the dashboard etc. just yet. Here's what the logs show:
1745944879556.png
 
Janhaus said:
In the web interface, the MQTT/HTTP section is not modified, do I need to do anything here? i.e. do I need to fill out MQTT Broker URL/IP?
I edited the Blue Iris Configuration to point to the Blue Iris IP address and port number, that should probably be added to the instructions.

In the logs, I see this:
4/29/2025, 12:08:41 PM [INFO] Checking IP: 172.19.0.1 <- this is not an IP in my local network, did I miss a setting somewhere?
Click to expand...
There are two ways of sending data to the database. One is via MQTT and the other is to use the API key. The API key is the preferred method so if you have it configured correctly you don't need anything in the MQTT section. The 172.19.0.1 you are seeing in your log file is the internal IP of your docker application so this is normal.

The errors in your log file indicates the app is not receiving plate data. Are you seeing plate captures in BI?

A normal log file should look like this:

Screen Shot 2025-04-29 at 2.01.16 PM.png
 
Thanks for the clarification! It seems that the default docker image has some permission issues with the database, see thread here:
github.com

Error processing request: error: there is no unique or exclusion constraint matching the ON CONFLICT specification · algertc ALPR-Database · Discussion #55

Seems like everything is working except the data being added to the database. The App receives and saves the image. Not sure what I'm doing wrong I followed the install instructions exactly. I can ...
github.com github.com

At first I was getting this error:
[ERROR] Error processing request: error: there is no unique or exclusion constraint matching the ON CONFLICT specification
After running psql -d postgres -U postgres -f /docker-entrypoint-initdb.d/schema.sql
I now get this error in the logs:
Error processing request: error: null value in column "plate_number" of relation "plate_reads" violates not-null constraint

Both In CodeProject and BI, I'm getting the plate recognized, i.e. the plate number is showing up in my LPR alert, so it's just an issue of saving to the ALPR database. Unfortunately I'm not familiar enough with postgres to figure out how to fix this.
 
Janhaus said:
Thanks for the clarification! It seems that the default docker image has some permission issues with the database, see thread here:
github.com

Error processing request: error: there is no unique or exclusion constraint matching the ON CONFLICT specification · algertc ALPR-Database · Discussion #55

Seems like everything is working except the data being added to the database. The App receives and saves the image. Not sure what I'm doing wrong I followed the install instructions exactly. I can ...
github.com github.com

At first I was getting this error:
[ERROR] Error processing request: error: there is no unique or exclusion constraint matching the ON CONFLICT specification
After running psql -d postgres -U postgres -f /docker-entrypoint-initdb.d/schema.sql
I now get this error in the logs:
Error processing request: error: null value in column "plate_number" of relation "plate_reads" violates not-null constraint

Both In CodeProject and BI, I'm getting the plate recognized, i.e. the plate number is showing up in my LPR alert, so it's just an issue of saving to the ALPR database. Unfortunately I'm not familiar enough with postgres to figure out how to fix this.
Click to expand...
Try downloading the update script to the same directory your app is in and run it using PowerShell with admin rights.
 
Janhaus said:
Thanks for the tip! I ran it earlier and updated successfully but didn't solve the error, trying it now to upgrade to nightly release and see if that works.
Click to expand...
algertc

Post in thread 'Full ALPR Database System for Blue Iris!'

svalvasori said:
I've done this:
Bash: 
root@alpr:/opt/ALPR_Database# docker compose down
[+] Running 3/3
 ✔ Container alpr_database-app-1  Removed         [URL='https://github.com/algertc/ALPR-Database']GitHub Repository[/URL]                                                                             1.2s
 ✔ Container alpr_database-db-1   Removed                                                                                     11.2s
 ✔ Network alpr_database_default  Removed                                                                                      0.3s
root@alpr:/opt/ALPR_Database# docker compose pull
[+] Pulling 2/2
 ✔ db Pulled...
Click to expand...

Did you see this post, and the ones surrounding it?
 
And this:
algertc

Post in thread 'Full ALPR Database System for Blue Iris!'

svalvasori said:
I downloaded directly from GitHub and compared md5 between the new and existing files, no difference.
Code: 
root@alpr:/opt/ALPR_Database# md5sum new/*
68299a0cc953f95cf27525b3c3023d41  new/migrations.sql
9caab0fb987b904a13f3e325f5fa5fbe  new/schema.sql
root@alpr:/opt/ALPR_Database# md5sum *.sql
68299a0cc953f95cf27525b3c3023d41  migrations.sql
9caab0fb987b904a13f3e325f5fa5fbe  schema.sql

The error does seem DB related:

3/25/2025, 11:32:31 AM [INFO] POST /api/plate-reads
3/25/2025, 11:32:31 AM [INFO] Received plate read data: [object Object]
3/25/2025, 11:32:31 AM [INFO] Database connection...
Click to expand...
 
Thanks so much @PeteJ @VideoDad - I did not see these earlier, but I did find the discussions on the Git project with several similar comments and same issues on my end. I'll go through a sequence of testing to see if I can get this to work, I'm running the current version of Docker Desktop, on Windows 10.
For beginners, I started with a completely new directory and installed the docker image again. Verified that my .sql files are identical to the ones in the latest branch
migrations.sql: 68299A0CC953F95CF27525B3C3023D41
schema.sql: 9560C7EA414F7787F82E704FF379A69D

Saw a plate come through just now, the good news is that I'm not seeing any database errors this time around with my fresh install, but the bad news is that the images are not being stored in the folders. My previous install had database errors, but did get the images stored...

Log from CodeProjectAI:
14:58:22:Response rec'd from License Plate Reader command 'alpr' (...bed481) ['Found Plate: 68770K'] took 653ms

Log from ALPR Database:
1746039603668.png
 
Janhaus said:
Thanks so much @PeteJ @VideoDad - I did not see these earlier, but I did find the discussions on the Git project with several similar comments and same issues on my end. I'll go through a sequence of testing to see if I can get this to work, I'm running the current version of Docker Desktop, on Windows 10.
For beginners, I started with a completely new directory and installed the docker image again. Verified that my .sql files are identical to the ones in the latest branch
migrations.sql: 68299A0CC953F95CF27525B3C3023D41
schema.sql: 9560C7EA414F7787F82E704FF379A69D

Saw a plate come through just now, the good news is that I'm not seeing any database errors this time around with my fresh install, but the bad news is that the images are not being stored in the folders. My previous install had database errors, but did get the images stored...

Log from CodeProjectAI:
14:58:22:Response rec'd from License Plate Reader command 'alpr' (...bed481) ['Found Plate: 68770K'] took 653ms

Log from ALPR Database:
View attachment 220163
Click to expand...
So you've confirmed the storage directory exists, I assume. If not manually create it.
 
^^
I had to tear down my installation a few weeks ago, and I found that it wasn't enough just docker-compose down, which deletes the Container(s). I also had to go into Docker Desktop and delete all the Images and Volumes, manually. Then docker-compose pull and docker-compose up -d worked.

n=1, YMMV.
 
Janhaus said:
Ok I saw a plate come through in the logs but it's not hitting the dashboard etc. just yet. Here's what the logs show:
View attachment 220097
Click to expand...
Just wanted to add that I was playing with this all last night trying to get it installed and running. I am getting the same error despite running the update script several times, some docker compose pull, and even scrapping everything and starting fresh.

I set up the MQTT and confirmed BI is sending the valid JSON information. On first install I had an issue where I was presented the "update" page after first login and it wouldn't allow me beyond it with an error of "relation plate_reads does not exist". After starting fresh and running the update script a few times, that was resolved. I am just stuck on this apparent database issue now.

Won't have time to troubleshoot anymore myself until this weekend but wanted to mention that you are not alone in this!
 
Ok so on my subsequent wipe (full delete of directory, removal of containers/images/volumes in docker before re-installing using the docker image and also checking the MD5 of schema.sql and migrations.sql to match the official ones from the latest main Github), I forgot to update the API key in the ALPR Database settings, which was what led to the:
Received plate read data: [object Object]
error of not getting plates saved to the database nor being saved in ALPR Database.

After updating the API key, I'm back to where I was on my first install, where the file is stored, but not saved to the database:
4/30/2025, 4:53:43 PM [INFO] POST /api/plate-reads
4/30/2025, 4:53:43 PM [INFO] Received plate read data: [object Object]
4/30/2025, 4:53:43 PM [INFO] Database connection established
4/30/2025, 4:53:43 PM [INFO] [FileStorage] Successfully saved image
4/30/2025, 4:53:43 PM [ERROR] Error processing request: error: there is no unique or exclusion constraint matching the ON CONFLICT specification

Can somebody with a working install verify a couple of items? In the Web Request or MQTT, the Post/Payload I have is copied from the instructions:
{ "ai_dump":&JSON, "Image":"&ALERT_JPEG", "camera":"&CAM", "ALERT_PATH": "&ALERT_PATH", "ALERT_CLIP": "&ALERT_CLIP", "timestamp":"&ALERT_TIME" }
Is this what you have?

Secondly, the stored file names I have appear like so:
undefined_1746046806816_d5cf3c51.jpg
Is this what you get as well?

Trying to see if the issue lies in a config item within BlueIris vs within the ALPR Database config...

@th182 - how do I verify if the JSON is correct?
 
Where you have "undefined", I have the plate name.
A quick way to check the contents of the &JSON is to send an email alert when a plate is detected that contains &JSON in the body of the email.
 
You must log in or register to reply here.
Top Bottom