Vettester
Getting comfortable
- Feb 5, 2017
- 841
- 831
The lovelace iFrame card is not going to work for a simple dashboard url because it has to be tied to an entity.Take a look at this thread: Lovelace iFrame card: dynamic url
The lovelace iFrame card is not going to work for a simple dashboard url because it has to be tied to an entity.Take a look at this thread: Lovelace iFrame card: dynamic url
Anyone have setup guidelines for Unraid?
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.
I'm not using Unraid.Pls post a reply if u have success w the plugin.
Sorry that was a mistake. Didn’t mean to quote both. Any luck w the HA link hikky_b sent?I'm not using Unraid.
No, I couldn't get it to work.Sorry that was a mistake. Didn’t mean to quote both. Any luck w the HA link hikky_b sent?
Alright I’ll do some research and get some better built in support for home assistant going.No, I couldn't get it to work.
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.
See below, the plate shows up as ...This is good to know, and yes, probably more proper. I will keep it in mind, but using it would require refactoring a whole bunch of code, especially the timestamp stuff, which was a pain in the ass the first time around. The label list solution should work just fine. If you find any bugs, I'll look at converting it.
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.@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.
so guessing that's BI chopping the memo length
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.All ears for feature requests of any kind.
I agree with prsmith777, I have three LPR cameras as well and it'd be nice to have the camera name noted.@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.