Full ALPR Database System for Blue Iris!

P

Qual o modelo da câmera usado amigo ?
The purpose of this thread is to talk about the ALPR Database. In order to send data and use the application, you will need ALREADY WORKING ALPR within Blue Iris.

If you haven't done that much, you should look in other threads on choosing cameras and tuning their settings.
 
  • Like
Reactions: PeteJ
As an Amazon Associate IPCamTalk earns from qualifying purchases.
  • Like
Reactions: Skinny1
@algertc, Any news on an upcoming release? Inquiring minds want to know.

Apologies for the absence guys. I’ve been preoccupied with a slew of other stuff, both work and life.

I’ve tried to resolve the installation issue a few different times, but I haven’t been able to reproduce it myself. If anyone knows what’s actually wrong with the db files, please PR.

Hoping to crank out some new features and use the training uploads some time over the next couple weeks.
 
Would this database be able to work on a dedicated raspberry pi, or would it not be powerful enough?

I think it might depends on version of rpi. I am running both the database and codeproject on the same RK3588 (16G, nvme ssd) and it works flawlessly. The RK3588 is probably similar to a pi5 in performance.
 
I just posted a long, very interesting thread in Blue Iris AI that heavily relates to this app and what's to come next. I highly recommend checking it out. I'd love to hear anyone's ideas or feedback.

 
  • Like
Reactions: Gimmons and Skinny1
So I recently blew away my ALPR docker and restored it. I have the same API key. I am getting this error....

5/25/2025, 1:27:38 PM [INFO] POST /database
5/25/2025, 1:27:38 PM [INFO] POST /api/verify-session
5/25/2025, 1:27:38 PM [INFO] GET /api/check-update
5/25/2025, 1:27:38 PM [INFO] GET /notifications
5/25/2025, 1:27:38 PM [INFO] POST /api/verify-session
5/25/2025, 1:27:38 PM [INFO] GET /api/check-update
5/25/2025, 1:27:38 PM [INFO] Checking notification plates
5/25/2025, 1:27:38 PM [ERROR] Error fetching notification plates: error: relation "tags" does not exist
5/25/2025, 1:27:38 PM [ERROR] Error in getNotificationPlates action: error: relation "tags" does not exist
 
So I recently blew away my ALPR docker and restored it. I have the same API key. I am getting this error....

5/25/2025, 1:27:38 PM [INFO] POST /database
5/25/2025, 1:27:38 PM [INFO] POST /api/verify-session
5/25/2025, 1:27:38 PM [INFO] GET /api/check-update
5/25/2025, 1:27:38 PM [INFO] GET /notifications
5/25/2025, 1:27:38 PM [INFO] POST /api/verify-session
5/25/2025, 1:27:38 PM [INFO] GET /api/check-update
5/25/2025, 1:27:38 PM [INFO] Checking notification plates
5/25/2025, 1:27:38 PM [ERROR] Error fetching notification plates: error: relation "tags" does not exist
5/25/2025, 1:27:38 PM [ERROR] Error in getNotificationPlates action: error: relation "tags" does not exist
Try running the following commands in the db container (per janhaus):

Code:
psql -d postgres -U postgres -f /docker-entrypoint-initdb.d/schema.sql

Code:
psql -d postgres -U postgres -f /docker-entrypoint-initdb.d/migrations.sql

If you get an error because there was no schema or migration file in the container, but you can see the file listed in the files tab for the container, see if there is a note with the word "mount." If so it means the container is accessing the file externally. If you copy the latest version of the file into your container and run the command again, it should work.
 
I'm working on this right now. I've fixed a bunch of other stuff but the db schema is such a pain in the ass. It has something to do with the setup running out of order. Normally I would just image the working db, but it's difficult for a self hosted app where you need to allow people to update and keep their existing external data. Kicking myself now for not using a proper tool from the start.
 
  • Like
Reactions: Gimmons and Skinny1
Try running the following commands in the db container (per janhaus):

Code:
psql -d postgres -U postgres -f /docker-entrypoint-initdb.d/schema.sql

Code:
psql -d postgres -U postgres -f /docker-entrypoint-initdb.d/migrations.sql

If you get an error because there was no schema or migration file in the container, but you can see the file listed in the files tab for the container, see if there is a note with the word "mount." If so it means the container is accessing the file externally. If you copy the latest version of the file into your container and run the command again, it should work.
I found these commands in the other ALPR thread earlier and it fixed everything..

Thank you.
 
I made a number of updates:

  • Fixed session kickout to login screen
  • Camera filter added to dashboard
  • Password will autofill and save in your browser now
  • Impossible to hit the login page if you have an active session
  • Deleting a record in live feed fixed to only delete that record
  • Correction/add to known forms styling fixed with bigger input boxes
  • Plate image viewer window data state updates properly now
  • Shows current release version in log page
  • Confusing notification page UI fixed
  • Time distribution clickable bars hitbox made height of entire column in case of wide range
  • Some other small improvements and preparations for future features


DB setup issue not yet fixed.....
 
Another quick general interest question. Does anyone experience a slow down in plate processing/ identification time after Blue Iris, CodeProject, and ALPR Database have been running for 4 to 5 days straight. It seems to me that my system will sit on a vehicle for maybe up to 10 seconds until the plate shows up in ALPR Database? All three programs (and Docker Desktop for Windows) reside on the same computer, and after I gracefully shut down everything, reboot, and then bring everything back up, processing/ identification is super quick once again. As in 1 second from car entering field of view to ALPR Database live view post. Any words of wisdom? Thanks
 
Another quick general interest question. Does anyone experience a slow down in plate processing/ identification time after Blue Iris, CodeProject, and ALPR Database have been running for 4 to 5 days straight. It seems to me that my system will sit on a vehicle for maybe up to 10 seconds until the plate shows up in ALPR Database? All three programs (and Docker Desktop for Windows) reside on the same computer, and after I gracefully shut down everything, reboot, and then bring everything back up, processing/ identification is super quick once again. As in 1 second from car entering field of view to ALPR Database live view post. Any words of wisdom? Thanks

I haven't had this happened, but for a while BI would randomly crash. Not the entire computer, just BI. Nothing in the logs.

You may want to monitor system resources and see if you are running out of mem or something. Some users have reported mem leak in CPAI, and they've resorted to restarting it from time to time. If you watch mem utilization for CPAI and see that mem usage is steadily increasing over time, then you might want to consider doing the same.

Anyway, this is probably not the best place to ask this question as this thread is focused on ALPR database issues.
 
I haven't had this happened, but for a while BI would randomly crash. Not the entire computer, just BI. Nothing in the logs.

You may want to monitor system resources and see if you are running out of mem or something. Some users have reported mem leak in CPAI, and they've resorted to restarting it from time to time. If you watch mem utilization for CPAI and see that mem usage is steadily increasing over time, then you might want to consider doing the same.

Anyway, this is probably not the best place to ask this question as this thread is focused on ALPR database issues.
Thanks, duly noted. I did also want to mention that besides my slow down issue (which I had a feeling it wasn't ALPR Database related but didn't know who or where to contact first), ALPR Database has been running flawlessly and I appreciate the effort that was spent on creating such a usefull app! I use it every day to monitor the safety and security of my property and street. Thanks again.
 
  • Like
Reactions: wpiman and algertc
Another quick general interest question. Does anyone experience a slow down in plate processing/ identification time after Blue Iris, CodeProject, and ALPR Database have been running for 4 to 5 days straight. It seems to me that my system will sit on a vehicle for maybe up to 10 seconds until the plate shows up in ALPR Database? All three programs (and Docker Desktop for Windows) reside on the same computer, and after I gracefully shut down everything, reboot, and then bring everything back up, processing/ identification is super quick once again. As in 1 second from car entering field of view to ALPR Database live view post. Any words of wisdom? Thanks
Have docker reboot each container once a day at like 3 AM or something? I know how to do that in Unraid, not sure on Windows.
 
Last edited:
  • Like
Reactions: wpiman and algertc