Vettester
Getting comfortable
- Feb 5, 2017
- 828
- 828
The lovelace iFrame card is not going to work for a simple dashboard url because it has to be tied to an entity.
Full ALPR Database System for Blue Iris!
- Thread starter algertc
- Start date
I use hass_ingress which is a custom component for home assistant that takes care of the auth within HA. Works for blue iris along with other services. On the ALPR Dashboard side, it would need to support basic auth or api key in the header for example. No improvements in intrinsic security but I don't think it's necessary to have the ALPR Dashboard exposed externally regardless..?
This is the component for HA: GitHub - lovelylain/hass_ingress: Home Assistant ingress feature, add additional ingress panels to your Home Assistant frontend.
Worth taking a look!
This is the component for HA: GitHub - lovelylain/hass_ingress: Home Assistant ingress feature, add additional ingress panels to your Home Assistant frontend.
Worth taking a look!
Vettester
Getting comfortable
- Feb 5, 2017
- 828
- 828
There’s a docker compose plugin for unraid. You could also deploy the two containers on their own without compose, but there are quite a few manual steps to do that.
Pls post a reply if u have success w the plugin.
See previous replies in this thread if it complains that port 5432 is already in use. That has been the case for Synology users.
Last edited:
Vettester
Getting comfortable
- Feb 5, 2017
- 828
- 828
Sorry that was a mistake. Didn’t mean to quote both. Any luck w the HA link hikky_b sent?
Vettester
Getting comfortable
- Feb 5, 2017
- 828
- 828
MikeLud1
IPCT Contributor
Alright I’ll do some research and get some better built in support for home assistant going.
I definitely understand the appeal of having it the dashboard - it’s a cool use case.
I would like it to work without needing a bunch of tinkering. I’m just not super familiar with HA so it’s a bit harder for me to figure out. Will get there tho.
Nothing at the moment. Was thinking it could be nice to be able to export your database, just not sure exactly how that should look yet or what people would end up using it for.
Would love to hear any thoughts
MikeLud1
IPCT Contributor
@algertc
Thanks for this awesome program.
If you are considering feature requests, I would like to add one.
My usage case is I have three LPR cameras, two for the main road in front of my house covering each direction, and a third LPR camera for the driveway coming up to the house. It would be very useful to add camera name to each alert. I have been doing this previously sending info by MQTT to Home Assistant using "Camera":"&NAME". This would likely require a redo of the database.
Thanks for this awesome program.
If you are considering feature requests, I would like to add one.
My usage case is I have three LPR cameras, two for the main road in front of my house covering each direction, and a third LPR camera for the driveway coming up to the house. It would be very useful to add camera name to each alert. I have been doing this previously sending info by MQTT to Home Assistant using "Camera":"&NAME". This would likely require a redo of the database.
Hmm very strange. I definitely didn't add anything that would turn it into ... so guessing that's BI chopping the memo length. Of course it happens to be the irrelevant OCRs first... Looks like I'll have to switch over to the other option. I'm going to prioritize some other improvements first since this is a bit of an edge case for vehicles with a lot of writing on them, but I'll change it eventually.
Absolutely. This is in progress. I actually had a column in the plate reads table for this originally but removed it for simplicity to reduce bugs since a bunch of people started using it. It won't require a full redo of the database, I should be able to just add a line to the schema file that will add it and keep all your other data when updating. I'm also adding the ability to edit plate reads to correct anything that was recognized incorrectly so people don't have 5 different plates in their db that are actually the same.
All ears for feature requests of any kind.
In case it's helpful, the maximum length of the memo parameter is 35 characters.
This is from the Help PDF, Administration chapter, JSON interface section.
Had a bit of a snag on getting data to the ALPR database. "api/plate-reads" was not connecting.... when I looked in my Unraid logs, it said "plate_reads" was not found.
When I changed to "api/plate_reads" it seemed to connect.
Is this something particular to Unraid maybe?
When I changed to "api/plate_reads" it seemed to connect.
Is this something particular to Unraid maybe?
Vettester
Getting comfortable
- Feb 5, 2017
- 828
- 828
It appears the database tab is sorting the data by the first seen column. It would be a nice feature to be able to sort the data by the other columns as well.