Yeah, that was the issue. It would just cancel before getting to the image with the plate. Before the change I made, it was very common to see this:
It would process the pre-trigger images and give up before getting to the post trigger.
@slabbel thank you for the suggestion, I played around with the setting and adding "*:30" to confirm seems to be helping a lot. It's been less than an hour with this setting, but so far, it seems to have fixed my issue, which was it was canceling the alert for no apparent reason. This seems to...
and I assume you have these in your docker-compose.yml
volumes:
- app-auth:/app/auth
- app-config:/app/config
- app-plate_images:/app/storage
app-plate_images:
driver: local
driver_opts:
type: none
o: bind
device: ./storage
do you have "storage" folder created under your install directory?
If you do, go to your http://ip.ip.ip.ip/update
and click the 3 buttons, you shouldnt have to... but I think that might fix it.
For whatever reason, the database wasn't build properly for you. I am not sure what causes this, but I ran into this when I was building the docker image from source and it wasn't working with similar errors as you each time it tries to write something to the database. I would get the images...
docker ps -a
find the container ID of your postgres
docker exec -it [container id] /bin/bash
psql -d postgres -U postgres -f /docker-entrypoint-initdb.d/schema.sql
@svalvasori Can you connecting to your sql container, and then issuing this command:
psql -d postgres -U postgres -f /docker-entrypoint-initdb.d/schema.sql
On my test system, I was seeing some errors that look sort of similar to yours:
app-1 | Database connection established
app-1 |...
Thanks for the suggestion, I'll give it a shot.
I moved back to .29 from .33 and it's no longer canceling the alerts. I added "confirm: *" to the config (it was blank before) and "fire only on confirmed" (was set to always). I am not sure if these were the needed changes, or if .29 is good.
I'm struggling with a number of issues, and they've changed over the last few months with each release. My main instance is .24 and aside from not processing about 2-4% of the plates, it's been super solid. This issue is said to be fixed in new versions, but each version after .24 has had...
I don't want to clutter up this thread, but if you can take a quick poll of the version of BI you are running, I'd appreciate it.
https://ipcamtalk.com/threads/which-version-of-bi-are-you-running-with-alpr-database-cpai.81001/
Pls reply in that thread, thanks
If BI and ALPR Database is working well for you, please share which version of BI you are running.
Well = BI behavior is consistent, it handles calls out to CPAI without failures and the motion triggers all work as expected, and you are running on the recommended HW.
For this poll, I am only...
...glad I found this post. In 5.9.9.33 it seems to cancel very aggressively, my ALPR catches are down 50% because it no longer waits for the vehicle to get into frame.
Can you post the md5sum of your migrations.sql and schema.sql files?
pdp11:/alprdash-lift# md5sum migrations.sql schema.sql
68299a0cc953f95cf27525b3c3023d41 migrations.sql
c11e379d5e7946a667b01a031086eb70 schema.sql
Have you tried just running the update script? This takes care of all of the details like using the latest migration.sql and schema.sql. I use to update manually, but the update in 0.18 has worked really well for me.
Check your settings on the dashboard under Home Assistant for the whitelisted IP, maybe you have that enabled.
How did you install this? Using the installation script, or manually?
Anyone getting any plate reads below confidence threshold? My threshold is around 70%, but once in a while, I am seeing these show up with v0.18, which I wasn't getting before:
And a little more weirdness:
The reading of 8XBZ466 has the image of the vehicle above (9MOA506).
Here is...
I have BI setup so for LPR. Generally, it works fine. However, I have noticed that there is a delay in when it starts sending images to LPR. What I mean is, if I watch the video clip of the event, I can clearly see the vehicle enter the frame, but the images sent to LPR are captures later...