Full ALPR Database System for Blue Iris!

rfoust said:
Nevermind, finally realized the database container wasn't running. Not sure why. I have a lot to learn about docker :)
Click to expand...
Alright one last post so people don't think I'm a complete idiot, I figured out why the database container was stopped. There is a missing comma in the schema.sql file that seemed to be breaking the whole thing. I added the comma and restarted the container and everything seems happy so far. I've submitted a pull request, assuming I did that right.
 
rfoust said:
Alright one last post so people don't think I'm a complete idiot, I figured out why the database container was stopped. There is a missing comma in the schema.sql file that seemed to be breaking the whole thing. I added the comma and restarted the container and everything seems happy so far. I've submitted a pull request, assuming I did that right.
Click to expand...
Yes did it right haha - thanks for the PR. Not dumb at all, my silly mistake.
 
  • Like
Reactions: prsmith777 and MikeLud1
I encountered the no stream error and was able to get it to go away by reducing the image size down very low to like 740 at 70% or something like that. As someone else said, it is kind of unfortunate that there isn't a way to store the full res JPEGS in BI but send a different size for alerts.

I think I can increase the max payload size and get the problem to go away for most people in the short term, but I really need to completely rework the way the images are stored. That will be coming soon, along with fixes for the other bugs people found.

I might create some sort of roadmap page to keep track of what to do. Would be nice for me as a to-do list and also would be cool to let people vote on which things they want most to bump them up.
 
  • Like
Reactions: prsmith777, MikeLud1 and Vettester
Here’s another over the top sneaky idea for the ultra enthusiastic:

Perhaps in the same box as a TMPS reader, broadcast generic unprotected WIFI SSIDs like verizonwifi, gogoinflight, unitedwifi, eduroam, starbuckswifi, iPhone, etc.

The point here is that many phones will auto join the network because they think they have connected before, and that is the default behavior. Most people aren’t connected to WiFi while driving, so I bet you could get a decent amount of connections.

POE+ would give enough power to broadcast far enough that most phones driving by would pick it up within your zone. Would have to be a lower traffic street though, not likely to work very well for the 30k plates per month users.

Your neighbors might hate you, and there’s probably some FCC regulation against it, but it could be done…

I actually knew someone many years ago who ended up getting a visit from the police after being caught exactly this way, phone auto connecting to WiFi.
 
  • Like
Reactions: MikeLud1
algertc said:
Here’s another over the top sneaky idea for the ultra enthusiastic:

Perhaps in the same box as a TMPS reader, broadcast generic unprotected WIFI SSIDs like verizonwifi, gogoinflight, unitedwifi, eduroam, starbuckswifi, iPhone, etc.

The point here is that many phones will auto join the network because they think they have connected before, and that is the default behavior. Most people aren’t connected to WiFi while driving, so I bet you could get a decent amount of connections.

POE+ would give enough power to broadcast far enough that most phones driving by would pick it up within your zone. Would have to be a lower traffic street though, not likely to work very well for the 30k plates per month users.

Your neighbors might hate you, and there’s probably some FCC regulation against it, but it could be done…

I actually knew someone many years ago who ended up getting a visit from the police after being caught exactly this way, phone auto connecting to WiFi.
Click to expand...

I like it!
 
  • Like
Reactions: MikeLud1
algertc said:
decided to make a half-wave 3' dipole antenna
Click to expand...
I think 3' is to big for 315MHz, it should be 17.9"

1736807060491.png
 
  • Like
Reactions: algertc
MikeLud1 said:
I think 3' is to big for 315MHz, it should be 17.9"

View attachment 212025
Click to expand...
You’re completely right. I forgot to half it the second time‍ :facepalm:

I’m horrendously inept when it comes to arithmetic and practical math. Calculator comes out for literally anything and often still ends up wrong as we see here. Online antenna calculator would have been a good call.

I’ll chop em down. Great catch and thank you for noticing. Looking at it now, and actually using my brain, I don’t know how I didn’t stop to question that. Just does not compute on its own…
 
algertc said:
You’re completely right. I forgot to half it the second time‍ :facepalm:

I’m horrendously inept when it comes to arithmetic and practical math. Calculator comes out for literally anything and often still ends up wrong as we see here. Online antenna calculator would have been a good call.

I’ll chop em down. Great catch and thank you for noticing. Looking at it now, and actually using my brain, I don’t know how I didn’t stop to question that. Just does not compute on its own…
Click to expand...
Also some car manufactures use 433MHz.


 
  • Like
Reactions: algertc
olympia said:
I had that issue the first time I was trying to update, but then then known plates page didn't even appear. When I ran migration.sql again, I've got back the known plates table, so I don't think this is the issue, but I will try running it again.

Edit: when I run migrations.sql again I get this:
Code: 
# psql -U postgres -d postgres -f migrations.sql   
psql:migrations.sql:1: NOTICE:  extension "pg_trgm" already exists, skipping
CREATE EXTENSION
psql:migrations.sql:2: NOTICE:  extension "fuzzystrmatch" already exists, skipping
CREATE EXTENSION
psql:migrations.sql:6: NOTICE:  column "priority" of relation "plate_notifications" already exists, skipping
ALTER TABLE
psql:migrations.sql:9: NOTICE:  column "camera_name" of relation "plate_reads" already exists, skipping
ALTER TABLE
psql:migrations.sql:11: ERROR:  column "ignore" of relation "known_plates" already exists
Click to expand...

So it turns out that this was actually a code mistake. I checked my live feed, and the same thing is happening to me. I think it was just that nobody else noticed. I revised the query, and it should work now if you pull the latest image.

I also increased the payload size for now, so please pull and test anyone who was having issues with BI sending plates. I think it should be able to accept much larger JPEGs now.

I created a public roadmap page:
@Vettester are you still getting 5x notifications?
 
algertc said:
  • Manually add known plates
  • "Untagged" as a filter option
Click to expand...
I can now filter the Live Feed by "untagged" but I'm not seeing the option for the Database tab. Will it be in both places, or was that an oversight?
It would also be nice to be able to add Flagged Plates to the database without having to see them.
Also, can the log timestamps be changed to local time rather than UTC?

Oh, and most importantly, thanks for all the updates! I should have said that FIRST.
 
VideoDad said:
I can now filter the Live Feed by "untagged" but I'm not seeing the option for the Database tab. Will it be in both places, or was that an oversight?
It would also be nice to be able to add Flagged Plates to the database without having to see them.
Also, can the log timestamps be changed to local time rather than UTC?

Oh, and most importantly, thanks for all the updates! I should have said that FIRST.
Click to expand...
My pleasure.

Responded on the roadmap board. Yes and will, but wondering why it's useful in the db page for you.

The log time is in the server's time format. Docker uses UTC by default because it is the standard for applications. If you need to change it, you can add something like:

YAML: 
 environment:
          TZ:"America/Los_Angeles"

to your compose for the app section. Might screw up other stuff though, not sure.

EDIT:
wondering why it's useful in the db page for you.
Click to expand...
He said when filtering by recognition count in the db page, avoid scrolling past all the plates you already know. Coming soon...
 
Last edited:
You must log in or register to reply here.
Top Bottom