As I found, that doesn't seem to work until a user is manually logged in. So I have to RDP to the BI machine which logs in as a user, and then starts the docker engine.
Again if anyone knows of a way to do this automatically in Windows (short of disabling user credentials) several of us would...
I asked about running docker as a service in Windows awhile ago, but wasn't able to find a solution. If you figure something out, let me know.
https://ipcamtalk.com/threads/full-alpr-database-system-for-blue-iris.79082/post-899295
So @algertc, what's in the next update? Are you working on the AI integration? Or auto correction of plates? I'd also like to put in a reminder request for a method of creating rules for notifications, etc.
If anyone else agrees, please add an upvote to this roadmap entry...
For direction of travel, in my case I have two zones (left and right) with motion triggered from A>B. Then I cloned the camera and changed it to B>A. So I end up with two virtual cameras with cars traveling one way detected on the first and in the other on the second.
A camera that only can zoom is always centered on the middle of the view. In your case you want that to be the bus stop which is up and to the left.
If you zoomed the view pictured, you'd be looking at your immediate neighbor's mailbox and driveway.
If you moved the camera so it was centered...
Don't forget the awesome ALPR DB system that @algertc has created. If people are recognizing plates but not yet logging them into a database, this is definitely something to consider.
https://ipcamtalk.com/threads/full-alpr-database-system-for-blue-iris.79082/
The problem I see is that area is not in the center of your current view. If all the camera can do is zoom, then you'd need the zoomed in and zoomed out views to have the same center.
So a PTZ instead?
From Nextdoor:
"Last night someone robbed a home on [redacted] around 9:03pm. There are plenty of good quality cameras on this court, the low life loser pieces of S, WILL get caught, that’s for certain.
They had to scale a fence and knew what they were going after in the home. It was more than...
I'm using Plate Recognizer for my detections and it is not infallible either. There are times with changing lighting conditions, physical obstructions, etc. where it gets a "close" but slightly wrong plate. Whether it be a database of corrections that have been made previously that it can auto...
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...