...because Blue Iris is a network dependent application. Consequently the best practice is to handle network dependency handling in its startup routine and only start activities on the network, once the network stack is up and running.
I found a workaround however: if I change the startup type...
Ahh, it’s not about necessity—it’s because I can! :)
BI runs on a Windows 11 VM within an unRAID server, and I had an unused SFP+ port there what I could pass through to the VM. Plus, my core switch in the same rack cabinet had free SFP+ ports, so it was a no-brainer to connect them. :)
...but...
Would be nice if you could try unchecking and rebooting to see if it starts.
It’s not working on my end, but I might have a different issue. My BI machine uses a 10G SFP+ Ethernet interface, and the network initialization is slower than usual (taking 30–60 seconds after boot). This might be...
Wow, yes, enabling auto-start (while not having local CPAI installed, so there is no CPAI to actually auto-start) fixes the issue for me. 5.9.9.27 is up and running with remote CPAI in unRAID docker what was not possible before.
Thank you for following up on this!
I'm experiencing this as well. This is what I meant when I said I noticed that in versions 5.9.9.25 and 5.9.9.27, BI no longer detects the CPAI update status in the 'Blue Iris News and Updates' tab, whereas it did in versions prior to 5.9.9.25.
I firmly believe that the "Start now" button is...
That's odd...
On v5.9.8.5, where the config panel has a different layout, I see the following options for custom selection when clicking the three dots while using an external Docker for CPAI:
So, there's no option to select the models, which makes sense since the models are managed within...
@hopalong, based on your AI config tab in the main configuration, it looks like it's working for you because you're running some kind of hybrid setup between external and local CPAI. If you were using only external CPAI, you wouldn’t be able to select custom models in that menu: it would simply...
@wpiman @PeteJ
I'm joining the queue as I'm experiencing the exact same issue. While reinstalling Windows under BI, I ran into this problem after getting everything set up again. I spent hours troubleshooting before coming here and realizing that I was likely running a version earlier than...
@sunny0101786 I mean no disrespect, but could you please continue troubleshooting your ALPR issue in the CodeProject.AI forum threads? As has been politely mentioned multiple times, what you're asking for is entirely off-topic for this discussion, which is focused on the ALPR database. Once you...
Interesting how many iterations are possible based on different BI settings... :)
I manually rerun the migration.sql command (since I’m the unRAID guy and have to do this manually), but it doesn’t work for me. I always have to go back to the /update page and run a database backfill cycle to...
I have only continuous, so there might be some differences. My continuous also splice every hour and when I was using &ALERT_CLIP I landed (probably) at the beginning of the splice, but surely far away from the actual alert.
As you said, it's definitely not something to handle on the app side...
I had to change &ALERT_CLIP to &ALERT_DB to ensure the URL points to the exact moment in the clip where the alert begins.
I believe this is because my LPR CAM is set to continuous recording, so the URL needs to reference both the clip and the exact timestamp within it. Since Blue Iris splits...
@algertc it appears that - at least for me - the occurrence counter is still not working correctly in case of corrected plates.
See the below example. Are you aware of this (I seem to remember you were at something similar)?
You're probably just not noticing it because it depends on the motion detection setup, lighting conditions, and the camera's field of view.
At first glance, it seems to work correctly in 90-95% of cases for me as well. However, I mostly encounter issues at night when car headlights are...
I’m noticing the same thing, and I believe it's because BI saves the trigger image rather than the AI-confirmed image in the database. As a result, the motion trigger image is what BI sends to the app when using "&ALERT_JPEG."
I’ll reach out to Ken @BI to clarify whether this is intentional, a...
Hmm... I just double-checked, and I don't have the main stream enabled. However, I am using 720p as the sub-stream for my ALPR camera. Maybe that's why it works well for me then?
I genuinely disagree with some of the settings being flagged as required:
The To Cancel field can be left empty because, given how the custom model is configured (objects:0, alpr), this setting becomes redundant.
Is using the main stream truly beneficial for you? In my experience, it only slows...
Thank you so much for this approach and way of thinking! I believe everyone here truly appreciates it.
For updates where things might go wrong, would it be possible to tag Docker releases for easier rollbacks, or would that be too much effort?
Indeed working without issues now. I saw on GitHub that the temporary fix was already quite complex, and you're planning to enhance it even further. Huge thanks, Charlie, for your hard work!
I'm experiencing the same issue now. I keep getting disconnected almost every few seconds, and the API key changes randomly and frequently. Actually API key changes are so frequent, that it is unusable now.
Hmm, the upgrade and database migration went smoothly—everything's running fast, and all my previous records are intact. However, I haven’t had any new plate detections recorded since then.
I even tried a fresh installation to see if the issue was related to the migration, but the problem...
Upgraded and migrated the images. Everything works perfectly now on my end. The database is indeed incredibly fast! I expected the image handling rewrite to take much longer. Fantastic work, Charlie! Thank you very much!
I know that both files have been updated, but what I'm saying is that the update to schema.sql doesn't matter since that file is only used during fresh installations when the database is initially created. After that, it’s no longer used—not even for database updates.
It's the migrations.sql...