Yes I could ignore it, but I just wated to make sure it wasn't an issue. I did not find anything using Google Fu so I thought I would ask here.
[tool] [tutorial] Free AI Person Detection for Blue Iris
- Thread starter GentlePumpkin
- Start date
Yes I could ignore it, but I just wated to make sure it wasn't an issue. I did not find anything using Google Fu so I thought I would ask here.
Village Guy
Pulling my weight
I have reported a couple of issues related to the Default Camera that arose on a recent build. Apparently although the Default does not appear to do anything it is required and should not be deleted. You might want to confirm that it is not selected as being active in your configuration!
It might also be worth compiling and testing the latest version at it has changes associated with the Default Camera.
Thanks @Village Guy I looked at the AITool setting but do not understand where the Default Camera setting is. Can you explain more about how to confirm that a default camera is not selected?
Village Guy
Pulling my weight
Choose Camera's and the Default Camera should be listed at the top. You can select "Enable AI detection for this camera" on the right, choose if it is to be active or not.
Last edited:
Scotty_4869
n3wb
Latest version BI and AI Tool 1.65 both installed on a Win10 machine. TBH I'm still getting my head around it all but I think I'm doing the ddns thing so I can run a VPN for remote access, both to BI and to my Home Assistant.
Everything I read tells me a VPN is the preferred way to remote access because you don't have to forward / open any ports? Saying that I do currently have port 81 forwarded and if I just use my current public IP I can access BI remotely too.
I just tried your suggestion, if I understand it correctly, and put [admin] in front of my [ddns url] followed by [:81] and my trigger command. Still getting an error in AI Tool and no trigger sent.
Village Guy
Pulling my weight
OK I think you are way ahead of yourself. First of all Aitool V1.65 is very very old and I highly recommend that you install the vorlonCD version which I believe most people are using.
Before you do that it might be a good idea to get everything working and become familiar with its operation.
Putting aside remote access which is really a whole new ball game, have you got everything working using local ip addresses? Once you get that working we can deal with remote access.
Scotty_4869
n3wb
Yep, if I just use my current public IP in the AI Tool trigger command and in BI's web server WAN setting it all works.
I installed BI, AI Tool and Deepstack following a youtube vid from The Hook Up, who does a lot of Home Assistant stuff. His video was from early 2020 and he installed AI Tool 1.65. When I first downloaded it I went with 1.67 but I couldn't see how to make it access my Deepstack which is installed in a docker container on the same VM as my Home Assistant. So I installed 1.65 instead and got everything working.
So like I said, I've got everything working including remote access via my VPN, but every time I reboot my router or whenever my ISP decides, I get a new public IP and then I've got to update that IP in each camera in AI Tool and the BI web server, and anything else I'm using with remote access, hence the ddns.
Village Guy
Pulling my weight
You keep referring to your public address! If you are running everything from one platform I recommend you get everything working using your local IP addresses. Public addresses come later
Seems that I deleted the default camer and that is what is causing the error messages. I tried to create a new one named Default but that did not work, so I may just go ahead and re-install the AITool from scratch.
Village Guy
Pulling my weight
If you have the VPN working just use the local IP address and port of BI. You will access it remotely by connecting to your VPN and then to your local IP and port. This simplifies everything. If you have port forwarding or are using Stunnel you can shut them off because your VPN gives you access to your network. When I am out of my network I start a VPN connection. Then I open UI3 or RDP into BI with the same LAN address that I use on my network.
It will pick up any file in the default folder and analyze it if it isn't named (input file begins with) for any other camera. (It's always been there in all versions).
I was not able to get the UI to show when I installed the VorlonCD version so I went back and installed AITool 1.67 and it is working fine with no errors. As the VorlonCD version is the newest, I would like to use it. I installed it by unzipping it over my current config but still no UI when trying to start aitool.exe. What am I doing wrong here?
You can try another. Maybe a bad zip. I posted the newest version .760 in both a RAR and ZIP format. Just need to go back one page.
Check the properties of AITool.exe and make sure the box below is ticked. You should have unblocked the zip file befor unziping it.
Hmm...I do not have that Unblock option and looking it up it says that means the file is not blocked.
Attachments
Yes. For now I am just going to use the 1.67 version as it seems to work well. I will try installing the VorlonCD version later.
Village Guy
Pulling my weight
Sorry my fault. I forgot that you were not already running a vorlonCD version.
I have attached the latest build that should work for you.
Last edited: