It's because it's watching for new files in that directory and that's a lot of files to watch for. I suggest making the following changes on the BlueIris side:
1. Change the retention policy on your aiinput folder to delete above 1GB and 1 hours.
2. Change the motion sensitivity settings on the...
Great! I really think the function node can be omitted. A simple switch node that looks at the msg.payload.state for "on" would replace it entirely.
Just to confirm, you're running with enableAnnotations set to true, correct?
Happens to the best of us :) This is why I recommend using Visual Studio Code to edit the settings files. It'll detect those errors for you as you type.
You don't need a change node for it. On the MQTT in node set the output dropdown to "a parsed JSON object". Then basename will be in msg.payload.basename.
Looking at the code it appears I never bothered to check in the changes to store the original image locally. Oops :D The only image...
There's two different kinds of integrations worth doing. The first is setting up MQTT Binary Sensors to get motion history. I use this to show a history chart on my Lovelace page:
The second is getting detailed info for use in the sequence in NodeRed. For that just directly register for the...
Open a support request on github and make sure to include your complete triggers.json file and all the log from startup through to first detection that fails.
I have Home Assistant and NodeRed on an RPI4. BlueIris, Deepstack, and this trigger system are on a dedicated PC. It is a normal PC I built for this but nothing fancy. Entry level AMD CPU, 16GB RAM. I would not run DeepStack on an RPI.
Version 4.0.0 is out with Pushbullet support!
Breaking changes
settings.json and triggers.json can no longer have unrecognized properties in them. While this is technically a breaking change it shouldn't impact anyone in practice. The addition of this requirement is to ensure new users get...
Are you running Docker on the same Windows machine as BlueIris? If not, do. It's by far the simplest and easiest way to get this up and running. Once you have it on the same machine BlueIris see this comment in GitHub for an example of setting it up.
I have Home Assistant + NodeRed managing all...
The system uses an off-the-shelf AI solution that doesn't have a way to train it with different things. For your situation you can set up two triggers with the same camera. The first trigger should mask where the cars are parked and should trigger on cars. The second trigger shouldn't have a...
See this comment on a support issue in GitHub: Correctly Write Mount Point for Source Images · Issue #286 · danecreekphotography/node-deepstackai-trigger.
If that doesn't help feel free to open a support issue there for more assistance and be sure to include a copy of your docker compose and...
You don't but since you're doing install/upgrades anyway I would. Make sure you're on Windows 10 version 2004, then install WSL2 and enable it. You may want it down the line and it is amazing :)
Oof :( I feel some of your pain, I had the same problem with the PC I built for BlueIris. I didn't have to drag a ladder out and go in the attic, but I did have to disconnect it all and drag it over to my office with a monitor and keyboard. Then I spent 30 minutes online trying to find out how...
This is very likely a BlueIris configuration issue, not an AI Tool issue @CommittotheIndian. Before I wrote my own system from scratch that supported MQTT natively I had MQTT events firing from BlueIris when AI Tool kicked it to say motion happened.
FWIW, MQTT support at the AI end, without...
Any Pushbullet fans out there? I've got everything written to add Pushbullet as one of the notification methods but wouldn't mind having someone take it for a spin before I promote the code to the dev image. If so let me know.
This means there's an error in your docker-compose.yaml file. I just tested with the sample config that's available on GitHub and it worked fine. The path and line count in that error is highly suspicious and makes me think you are not running docker-compose in the same directory as your...
Yes. See the trigger documentation for how to configure it. Note that I just realized I have a bug with it but I'll push an update out to fix that later today.
Edit: I was mistaken, no bug. Woot!
In terms of performance they should be essentially equivalent. The performance is largely driven by the time it takes to analyze each image and both approaches use the same DeepstackAI solution for that piece.
In terms of features this approach has a lot more options and capabilities in terms...
Version 3.1.0 is now available:
Triggers can now be manually activated via a REST API, and can be configured to retrieve a camera snapshot from a REST API instead of watching for image files that appear in a folder. This is useful for NVR systems other than BlueIris that don't support writing...
Ok you're in great shape then. Make sure you are running the latest version of Windows 10 (version 2004). Stop running the non-Docker Deepstack. Follow the instructions at danecreekphotography/node-deepstackai-trigger.
You won't have to edit anything in settings.json. Edit docker-compose.yaml...