-
-
Notifications
You must be signed in to change notification settings - Fork 28
Home
This system uses Docker containers to run DeepStack AI and process images from a watch folder, then fires a set of registered triggers to make web request calls, send MQTT events, and send Telegram messages when specified objects are detected in the images.
This project was heavily inspired by GentlePumpkin's post on ipcamtalk.com that triggers BlueIris video survelliance using DeepStack as the motion sensing system.
The following five steps are all that's required to start using AI to analyze images and then call a web URL, such as one that triggers a BlueIris camera to record.
- Install Docker
- Copy the
docker-compose.yml
andtriggers.json
files from the[sampleConfiguration](https://github.com/danecreekphotography/node-deepstackai-trigger/tree/master/sampleConfiguration)
directory locally. - Edit the
docker-compose.yml
file to modify the mount point for source images and set the timezone - Edit
triggers.json
to define the triggers you want to use. - Run
docker-compose up
to start the system running
Setting the timezone via the TZ
environment variable in docker-compose.yml
is important for
every thing to work smoothly. By default Docker containers are in UTC and that messes up
logic to skip existing images on restart. A list of valid timezones is available on
Wikipedia. Use any value
from the TZ database name
column.
Editing the .json files in Visual Studio Code or some other editor that understands JSON Schemas is recommended: you'll get full auto-complete and documentation as you type.
- Copy
mqtt.json
andtelegram.json
from the[sampleConfiguration](https://github.com/danecreekphotography/node-deepstackai-trigger/tree/master/sampleConfiguration)
directory locally. - Edit
mqtt.json
to specify the connection information for your MQTT server (if using MQTT). - Edit
telegram.json
to specify the connection information for your Telegram bot server (if using Telegram). - Edit
triggers.json
to add mqtt and Telegram handlers. - Stop the existing running containers
- Run
docker-compse up
to start the system with the new configuration
Having trouble? Check the logs output from Docker for any errors the system may throw. The troubleshooting page has tips for resolving common deployment problems.
Interested in building this locally? Check out the contributing guide for quick steps on how to clone and run in under five minutes.