The place where I see the ALPR database having an advantage over just BI (whether it be an MQTT message or a notification) is that ALPR can do some lookup of the plate and add enriched data (such as fixing poor recognition with a fuzzy lookup), adding tags, checking for flagged vehicles, adding...
I ran the update.ps1 script on Friday and it looked like everything was working. However, I'm getting errors about 'mqttnotifications' doesn't exist and I haven't been getting plate reads for a couple days. I'll try manually updating migrations.sql to see if that fixes it. I'd recommend that...
Before even considering the ALPR Database you need:
1) A camera capable of getting close-up photos of license plates, with the right settings for day and night, high shutter speed, gain, etc.
2) A working Blue Iris setup where the camera is configured and sending data into BI.
3) The camera...
@algertc, I went ahead and did an update using the ps1 script and it does appear that this list of updates is there. Do you have any further info on the next big release and when it might be arriving?
Let's go back a step. Are you calling the ALPR module (CodeProject.AI) correctly? Are you getting plates detected and returning the plate value in Blue Iris?
You shouldn't be getting an error about JSON. Are you sure you changed it to the following?
{ "plate_number":"&PLATE", "Image":"&ALERT_JPEG", "camera":"&CAM", "ALERT_PATH": "&ALERT_PATH", "ALERT_CLIP": "&ALERT_CLIP", "timestamp":"&ALERT_TIME" }
Check the Blue Iris log files to confirm what happens when a plate is detected. You should see a successful call to the ALPR database, or an error.
If you see an error there, then the problem is with the call. I'd start by verifying the IP of the ALPR DB server hasn't accidently been changed...
Have you tried creating two zones (left third and right two-thirds) and using a crossing from right to left as the trigger to search for a plate?
I agree that more zoom would help give the license plate model a better chance to see a plate.
It might be easier to set up an LPR camera and detect the desired plates rather than trying to just detect the make/model of car. First, you'd need a good amount of training data so that it could discern each specific car without a lot of false negatives for the wrong make/model, but even then...
The problem, I think, is the database schema is different than what the code is expecting.
From that prior post I linked, I'd try those separate db container calls.
Try them one by one and report back if you can get through them without an error.
1. The JSON should not be in quotes.
2. The path and file names for the images are long; probably not an issue.
3. The timezone shouldn't affect the reading of plates. They are actually sent and stored in UTC.
Can you check your DB logs again? If you're still getting the ON CONFLICT error...
I'm using Windows App to connect to my home PCs (see my earlier screenshot). You still need a way to VPN to your home network if you want remote access.
And yes, local RDC access also works and won't go away.
For PC to PC, the Remote Desktop Connection is still functioning fine for me.
For Android (and I think iOS), the former RD App has been replaced by the "Windows App". Apart from having a name that is completely generic and hard to search for, it does still provide the same remote access...
I would go back to having the ALPR database on the same machine. Verify you have correctly set the API key in the settings.
From another PC on the LAN, confirm you can reach the login screen. You want to use the internal IP of the BI/DB machine (leave the VPN out of the equation).
Then ensure...
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...
Blue Iris has a limit of 64 cameras.
But the ALPR database doesn't technically care about the camera that read the plate. The database just stores images, plate details, the name of the camera, etc. As long as you have enough disk space you could technically be sending plate reads from hundreds...
This was previously added to the roadmap. You can follow progress on this or add comments:
https://alprdatabase.featurebase.app/p/manually-add-new-flagged-plate-without-prior-detection
The &JSON that is sent when the ALPR module has found a plate is different than when other objects are found.
If you want to use the same camera for both plates and objects, you should do exactly what you did and separate the ALPR processing to its own instance so that it isn't trying to treat...
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.