Full ALPR Database System for Blue Iris!

You fixed the missing x-api-key issue, but did you fix the missing "/api/plate-reads" in your ip address?
Good spot. @Vettester is right. I would use localhost instead of your hostname too if it’s the same machine just to prevent any issues.

Did you use the install script or did you create the directories and copy the files manually? Please check the logs tab at the bottom left of the app also and see if there are any other errors there. @sunny0101786
 
You fixed the missing x-api-key issue, but did you fix the missing "/api/plate-reads" in your ip address? It should be MY-PC:3000/api/plate-reads
i get this error

This page isn’t working​

If the problem continues, contact the site owner.


HTTP ERROR 405
 
Were you actually capturing plates in BI before jumping down this rabbit hole or did you think this was the magic solution?

You need to have been capturing plates reliably day and night before going down this path.
 
  • Like
Reactions: aesterling
You may have a slightly better chance than USA plates with those being larger, but I think that field of view is too wide to reliably get plates, especially at night.

But if you haven't got that part worked out, then hold on this database until the first part is resolved.
 
what configuration you are referring to?
Screen Shot 2025-02-21 at 7.51.22 PM.png
 
what configuration you are referring to? i'm trying this for more info please check my previous post Full ALPR Database System for Blue Iris!

Where did /dashboard/ come from? It should look exactly as it does in the example.



Let me just clarify the flow of how things work for this in case anything doesn't make sense

1) Your existing Blue Iris system uses either CodeProject or DeepStack and has an ALPR module installed. In this setup, the AI server (completely separate from this application) sends back the results from its detection to Blue Iris and BI saves it.

2) We use a Blue Iris alert action to then send that AI prediction to this application so that you can store and use them instead of just having it in the memo in Blue Iris. The &PLATE, &ALERT_JPEG, etc are Blue Iris "macros" which will replace that text with what the AI server sent.

3) This application is a combination of a web app and database that uses an API route to receive the data from Blue Iris and store it for you so you can actually use it.

4) Everything here is completely separate and is just a way to manage your ALPR recognitions.



So it goes ALPR camera stream -> Blue Iris sees motion and triggers -> AI server with ALPR module detects license plate -> Blue Iris gets the plate back from the AI -> Alert Action uses the & macros to get that data from the alert -> Web request sends data to the /api/plate-reads route of this app -> this app receives that data, processes it, then stores it in its database -> you can then access and manage the recognitions in your browser.


Did you use the install script or did you create the directories and copy the files manually? Please check the logs tab at the bottom left of the app also and see if there are any other errors there. @sunny0101786
 
  • Like
Reactions: Vettester
I’m running version 5.6.2.10. Do you think it has something to do with this? I’m still in the process of upgrading, but I’m having a bit of an issue I haven’t received any new keys from the BI team yet.
 

Attachments

  • 13.11.16_5ce3510d.jpg
    13.11.16_5ce3510d.jpg
    63.6 KB · Views: 0
Do I need to change any settings in the AI menu?
 

Attachments

  • Image 2025-02-22 at 13.16.06_c5f099f4.jpg
    Image 2025-02-22 at 13.16.06_c5f099f4.jpg
    152.7 KB · Views: 0
Where did /dashboard/ come from? It should look exactly as it does in the example.



Let me just clarify the flow of how things work for this in case anything doesn't make sense

1) Your existing Blue Iris system uses either CodeProject or DeepStack and has an ALPR module installed. In this setup, the AI server (completely separate from this application) sends back the results from its detection to Blue Iris and BI saves it.

2) We use a Blue Iris alert action to then send that AI prediction to this application so that you can store and use them instead of just having it in the memo in Blue Iris. The &PLATE, &ALERT_JPEG, etc are Blue Iris "macros" which will replace that text with what the AI server sent.

3) This application is a combination of a web app and database that uses an API route to receive the data from Blue Iris and store it for you so you can actually use it.

4) Everything here is completely separate and is just a way to manage your ALPR recognitions.



So it goes ALPR camera stream -> Blue Iris sees motion and triggers -> AI server with ALPR module detects license plate -> Blue Iris gets the plate back from the AI -> Alert Action uses the & macros to get that data from the alert -> Web request sends data to the /api/plate-reads route of this app -> this app receives that data, processes it, then stores it in its database -> you can then access and manage the recognitions in your browser.
logs
 

Attachments

  • ge 2025-02-22 at 13.23.18_bfd3e540.jpg
    ge 2025-02-22 at 13.23.18_bfd3e540.jpg
    117.4 KB · Views: 0
Do I need to change any settings in the AI menu?
It looks like your AI is disabled? Unless you have the server override set in the camera you should have the top box ticked.

Can you clarify if you ever had ALPR working? That has been asked a couple times, but I couldn't find your response.

I believe you need custom models enabled for ALPR in the older releases.


If you aren't already getting plates in the memo of your blue iris alerts, I would encourage you to please consult the ALPR threads or a youtube video and get that working first then come back here. As I said, this does not do any ALPR. Your issue is well before anything here in the pipeline.