Version 6

[Tinman]

So just for curiosity's sake, after doing a uninstall and reinstall of BI6 using the latest FULL installer file that I just downloaded. Here is what it now shows under installed apps.
Notice it shows the correct current version number. Not sure if this updates but I will check it out.

 

[Bruce_H]

If you adopted early in the prerelease beta's you were on like 5.9.9.7 or.9 before the official 6.0 came out...dont freak out on the version number. says 5.9.9.9 in Program uninstall. Don't worry .
View attachment 235545

I had three systems running BI 5.x, One of them I did the upgrade to V6x via the full download from the BI site, the other two the upgrade to V6x was done by the normal update inside BI, both of these systems have the messed up version in the list of installed application, the full install is correct. On one of my systems with the messed up version numbers I did a registry backup of V6x and then uninstalled V5 and V6, then reinstalled V6 from the full download, upon reinstall everything was still there and did not require the import of the reg file and all the version numbers are now correct in the list of installed applications. My conclusion is that the versioning got mixed up do to doing the upgrade using the internal update procedure, anyone else who is contemplating doing an upgrade from V5x to V6x, should download the full install package. Now I just need to fix up my one remaining installation

 

[TheDogee]

Since updating to version 6, I keep getting what appears to be false triggers on multiple cameras at the same time, the log looks like this. What does it mean?
level time object message
1 1/2/2026 10:26:40.225 AM FrontLeft Events: request 00002efe
1 1/2/2026 10:26:40.225 AM Right Events: request 00002efe
1 1/2/2026 10:26:40.234 AM Drive Events: request 00002efe
1 1/2/2026 10:26:40.234 AM FrontRight Events: request 00002efe
1 1/2/2026 10:26:40.234 AM Backyard1 Events: request 00002efe
1 1/2/2026 10:26:40.238 AM Deck Events: request 00002efe
0 1/2/2026 10:26:43.316 AM FrontRight ONVIF Event: RuleEngine/CellMotionDetector/Motion
3 1/2/2026 10:26:43.334 AM FrontRight Trigger: ONVIF (RuleEngine/CellMotionDetector/Motion)
0 1/2/2026 10:26:43.335 AM Drive ONVIF Event: RuleEngine/CellMotionDetector/Motion
3 1/2/2026 10:26:43.333 AM Drive Trigger: ONVIF (RuleEngine/CellMotionDetector/Motion)
8 1/2/2026 10:26:43.783 AM Drive Trigger: Alerted
8 1/2/2026 10:26:43.948 AM FrontRight Trigger: Alerted
0 1/2/2026 10:26:44.123 AM Deck ONVIF Event: RuleEngine/CellMotionDetector/Motion
0 1/2/2026 10:26:44.134 AM FrontLeft ONVIF Event: RuleEngine/CellMotionDetector/Motion
0 1/2/2026 10:26:44.138 AM Backyard1 ONVIF Event: RuleEngine/CellMotionDetector/Motion
3 1/2/2026 10:26:44.132 AM Deck Trigger: ONVIF (RuleEngine/CellMotionDetector/Motion)
0 1/2/2026 10:26:44.160 AM Right ONVIF Event: RuleEngine/CellMotionDetector/Motion
3 1/2/2026 10:26:44.162 AM Right Trigger: ONVIF (RuleEngine/CellMotionDetector/Motion)
3 1/2/2026 10:26:44.170 AM Backyard1 Trigger: ONVIF (RuleEngine/CellMotionDetector/Motion)
3 1/2/2026 10:26:44.188 AM FrontLeft Trigger: ONVIF (RuleEngine/CellMotionDetector/Motion)
8 1/2/2026 10:26:44.286 AM Right Trigger: Alerted
8 1/2/2026 10:26:44.308 AM Backyard1 Trigger: Alerted
8 1/2/2026 10:26:44.311 AM FrontLeft Trigger: Alerted
8 1/2/2026 10:26:44.366 AM Deck Trigger: Alerted

 

[Flintstone61]

I had three systems running BI 5.x, One of them I did the upgrade to V6x via the full download from the BI site, the other two the upgrade to V6x was done by the normal update inside BI, both of these systems have the messed up version in the list of installed application, the full install is correct. On one of my systems with the messed up version numbers I did a registry backup of V6x and then uninstalled V5 and V6, then reinstalled V6 from the full download, upon reinstall everything was still there and did not require the import of the reg file and all the version numbers are now correct in the list of installed applications. My conclusion is that the versioning got mixed up do to doing the upgrade using the internal update procedure, anyone else who is contemplating doing an upgrade from V5x to V6x, should download the full install package. Now I just need to fix up my one remaining installation

good to know. thanks.
I'm going to probably try that on a day when I have free time to mess around.
I used the link somebody provided to get the full version of 6 as i recall. I cant remember if the link was internal to IPcamtalk or out at BI's site.
But they were saying it would still show as 5.9.9.9 until the official release.
I did all the Backups like you did, end surprisingly enough it somehow automagically replaced my working .reg file(s)

I should probably leave well enough alone. but yes, the 6 version seems smart enough to fin the .reg files of the last running version and incorporate them into the new installation.

 

[Bruce_H]

good to know. thanks.
I'm going to probably try that on a day when I have free time to mess around.
I used the link somebody provided to get the full version of 6 as i recall. I cant remember if the link was internal to IPcamtalk or out at BI's site.
But they were saying it would still show as 5.9.9.9 until the official release.
I did all the Backups like you did, end surprisingly enough it somehow automagically replaced my working .reg file(s)

I should probably leave well enough alone. but yes, the 6 version seems smart enough to fin the .reg files of the last running version and incorporate them into the new installation.

Just get the full install from the BlueIris download page, that is the only one that I would trust!

 

[105437]

Try using "wildlife" label in the "To confirm:" field.

So "wildlife" isn't a lable listed when I check Yolov8 labels list. I'm going to try this and see how it works.

 

[Vettester]

So "wildlife" isn't a lable listed when I check Yolov8 labels list. I'm going to try this and see how it works.

I made this suggestion before I knew about the coco.names file. You should stick with whatever you have not commented out in that file.

 

[Keizer]

I made this suggestion before I knew about the coco.names file. You should stick with whatever you have not commented out in that file.

How exactly does the coco.names file come into play? I found the list. Can you only use the names listed in the coco.names file?

 

[Bruce_H]

How exactly does the coco.names file come into play? I found the list. Can you only use the names listed in the coco.names file?

That is my understanding that what is in the file is all that there is at the moment, you can not add to it, just tell it to ignore ones that you are not interested in by putting a "-" in front of the item, make sure that you use a plain text edititor ant that you do not mess up the ".names" extension on the file

 

[Keizer]

That is my understanding that what is in the file is all that there is at the moment, you can not add to it, just tell it to ignore ones that you are not interested in by putting a "-" in front of the item, make sure that you use a plain text edititor ant that you do not mess up the ".names" extension on the file

90% of my list already has a "-" in front of the items. Why would you need to even put a "-" in front when you tell each camera what to detect in the "To confirm:" field in AI settings? If you only put bird,cat,zebra in the "To confirm:" field, isn't that what the camera will detect and the rest of the list is ignored?

 

[Bruce_H]

I would think that it would save the AI process from even considering the items, but that is only a guess on my part, when I commented out many of the items it appeared to reduce the time it took, but I did not do a scientific study to confirm it! If you do the testing let us know the results!

 

[rocky500]

Followed what some have written for the change over from v5 to v6. Did backup first, so could always go back quickly to how things were.

Stopped current v5 from running on boot up by disabling the top 2 options in the startup tab for Operating System. Rebooted, then installed full v6.
Set that up and rebooted and checked it worked. Then uninstalled v5.
One thing I noticed after is I could not access the webserver from my other PC's on the same lan as before.
I have Eset on my BlueIris server and even disabled that and no go. Eset I thought also totally disables MS antivirus/firewall etc, so thought that was not the problem also.
Could access it from the same PC through a browser with the HTTP server info/port but not from other PC's.

I had to go to the options in BlueIris and select WebServer Tab then run the Remote Access Wizard at the bottom.
Once completed I could then access the webserver from other PC's.

Took a little while to work this out as I also have Tailscale on the BlueIris PC and did some online reading to rule that one out too. Setup Tailscale a little while back as kept getting so many attempts to log on to it from outside my lan.

So not sure if anyone else had to run the Remote Access Wizard also or this may already have been mentioned before?

 

[The Automation Guy]

Speaking of hard drive failures... Do you guys feel like over the past 10+ years you see less failures? I used to see it all the time.

I wonder if that is because we (the general public) are just more aware/educated to the different types of hard drives and we are better about purchasing a drive that is designed for the specific use case, or if hard drives are getting better? I suspect it is the former......

 

[Keizer]

I wonder if that is because we (the general public) are just more aware/educated to the different types of hard drives and we are better about purchasing a drive that is designed for the specific use case, or if hard drives are getting better? I suspect it is the former......

I just had my first ever hard drive failure. It was a Seagate that I was using as a storage drive in a non Blue Iris PC.