Known Plates tab says "No known plates found" even though they are in the table.Nice update available:
Known Plates tab says "No known plates found" even though they are in the table.Nice update available:
Did you add the Known Plate by clicking on the plus signKnown Plates tab says "No known plates found" even though they are in the table.
View attachment 211250
@algertc out of the blue the API Key changed, I did the update this morning and everything was working fine then at about 1:00pm the ALPR-Dashboard stop logging plates. What I found is the API Key changed.Nice update available:
- Time format fix
- Dashboard Redux: adjustable period, new visuals, top plates improvements, better responsiveness, clickable bars on chart, hover for quick look.
- Ignore flag for known plates (Eyeball in known plates page)
- Live feed can now actually be live updated. Switchable with toggle. Your page and scroll position are maintained on receipt of a new plate.
- Ability to edit tag name and color
- Sensible default sorting of database
- Speed and loading improvements
I would definitely like to do more advanced notification rules. Sorting on live feed page will come next. I will add the untagged filter also @VideoDad
Pics below. I thought the hover for quick look thing was pretty cool.
View attachment 211217
View attachment 211218
Yes, I have about 20 known plates in the database which I confirmed directly. I can also see the details throughout the other screens. But the Known Plates tab doesn't bring anything up, after the update.Did you add the Known Plate by clicking on the plus sign
View attachment 211253
View attachment 211252
It works for me after the update, did you update the docker-compose.yml and migrations.sql files before update the Docker container.Yes, I have about 20 known plates in the database which I confirmed directly. I can also see the details throughout the other screens. But the Known Plates tab doesn't bring anything up, after the update.
You can click on the top to view all platesINSIGHTS:
- Could the button for View All be closer to the top? Or perhaps make the plate name at the top clickable?
But the Known Plates tab doesn't bring anything up, after the update.
It's working for me too.It works for me after the update,
This would likely be whyIt works for me after the update, did you update the docker-compose.yml and migrations.sql files before update the Docker container.
Did anyone else experience this? Mine did not change@algertc out of the blue the API Key changed, I did the update this morning and everything was working fine then at about 1:00pm the ALPR-Dashboard stop logging plates. What I found is the API Key changed.
Mine hasn't changed. The update was applied about 12 hours agao.Did anyone else experience this? Mine did not change
So far I have not had anymore issues with the API Key.Did anyone else experience this? Mine did not change
Yes, I did. But apparently the migrations.sql failed to run and add the 'ignore' flag to Known Plates. I did a full refresh and ran the update again and this time it took. Thanks, as usual, @MikeLud1It works for me after the update, did you update the docker-compose.yml and migrations.sql files before update the Docker container.
I did notice that… The way the live update works is kind of sloppy and is a fix for my previous bad code. If you disable it the filter should work. I will redo the whole page correctly at some point.@algertc I do not think it is a bug but when you have Live Update enabled the Hour Range filter is useless, you can not set the range.
Line 16878: 1 1/4/2025 9:45:20.267 AM Cam3a Web: No stream: 500
Line 17087: 1 1/4/2025 10:26:51.445 AM Cam3b Web: No stream: 500
Line 17303: 0 1/4/2025 1:08:02.653 PM Cam3a Web: 201 Created
Line 17316: 0 1/4/2025 1:08:12.798 PM Cam3b Web: 201 Created
Line 17427: 0 1/4/2025 1:34:49.643 PM Cam3a Web: 201 Created
Line 17439: 0 1/4/2025 1:34:59.583 PM Cam3b Web: 201 Created
Line 17486: 0 1/4/2025 1:41:35.935 PM Cam3b Web: 201 Created
Line 17733: 0 1/4/2025 2:05:22.366 PM Cam3a Web: 201 Created
Line 17753: 1 1/4/2025 2:06:23.693 PM Cam3b Web: No stream: 409
Line 17812: 0 1/4/2025 2:12:12.658 PM Cam3b Web: 201 Created
Line 17961: 1 1/4/2025 2:34:38.655 PM Cam3a Web: No stream: 409
Line 18003: 0 1/4/2025 2:40:58.018 PM Cam3b Web: 201 Created
Line 18156: 1 1/4/2025 3:22:59.600 PM Cam3b Web: No stream: 409
Line 18288: 0 1/4/2025 3:59:12.794 PM Cam3b Web: 201 Created
Line 18324: 0 1/4/2025 4:15:41.671 PM Cam3b Web: 201 Created
Line 18359: 1 1/4/2025 4:31:57.388 PM Cam3a Web: No stream: 409
Line 18393: 0 1/4/2025 4:37:11.364 PM Cam3a Web: 201 Created
Line 18405: 0 1/4/2025 4:37:22.452 PM Cam3b Web: 201 Created
Line 18489: 1 1/4/2025 5:03:08.954 PM Cam3b Web: No stream: 400
I will be adding a page to view the logs from inside the app soon. You can check by attaching to the container. Try reducing your JPEG size/quality in blue Iris and checking the rest of the settings. I encountered that error a few times too when setting up a new cam. That’s fully a BI thing.I'm seeing occasional failures when making API calls to the database:
Code:Line 16878: 1 1/4/2025 9:45:20.267 AM Cam3a Web: No stream: 500 Line 17087: 1 1/4/2025 10:26:51.445 AM Cam3b Web: No stream: 500 Line 17303: 0 1/4/2025 1:08:02.653 PM Cam3a Web: 201 Created Line 17316: 0 1/4/2025 1:08:12.798 PM Cam3b Web: 201 Created Line 17427: 0 1/4/2025 1:34:49.643 PM Cam3a Web: 201 Created Line 17439: 0 1/4/2025 1:34:59.583 PM Cam3b Web: 201 Created Line 17486: 0 1/4/2025 1:41:35.935 PM Cam3b Web: 201 Created Line 17733: 0 1/4/2025 2:05:22.366 PM Cam3a Web: 201 Created Line 17753: 1 1/4/2025 2:06:23.693 PM Cam3b Web: No stream: 409 Line 17812: 0 1/4/2025 2:12:12.658 PM Cam3b Web: 201 Created Line 17961: 1 1/4/2025 2:34:38.655 PM Cam3a Web: No stream: 409 Line 18003: 0 1/4/2025 2:40:58.018 PM Cam3b Web: 201 Created Line 18156: 1 1/4/2025 3:22:59.600 PM Cam3b Web: No stream: 409 Line 18288: 0 1/4/2025 3:59:12.794 PM Cam3b Web: 201 Created Line 18324: 0 1/4/2025 4:15:41.671 PM Cam3b Web: 201 Created Line 18359: 1 1/4/2025 4:31:57.388 PM Cam3a Web: No stream: 409 Line 18393: 0 1/4/2025 4:37:11.364 PM Cam3a Web: 201 Created Line 18405: 0 1/4/2025 4:37:22.452 PM Cam3b Web: 201 Created Line 18489: 1 1/4/2025 5:03:08.954 PM Cam3b Web: No stream: 400
Are there logs somewhere that I can view to get a better idea why these occasionally fail?