neilenns / node-deepstackai-trigger

Detects motion using Deepstack AI and calls registered triggers based on trigger rules.
MIT License
167 stars 28 forks source link

Document how to get node-deepstackai-trigger working on Unraid #349

Closed MattW2 closed 3 years ago

MattW2 commented 4 years ago

This tutorial assumes that you will be running deepstack and node-deepstackai-trigger as docker containers on an Unraid server.

Hope this helps people trying to get this running on Docker. I have had it working for the last week and it has been working smoothly while using far less system resources than trying to run deepstack on a Windows VM. I would be happy to turn this into a Wiki page with screen shots on the node-deepstackai-trigger git repository.

Setup deepstack as a docker container

Since deepstack isn't in the Unraid app store we will need to manually setup the container. Create a new container with the following parameters

Click done, wait for deepstack to download and run, it can take 20 minutes or more. Check that it is running by going to http://fixedIPYouAssigned:5000

Setup node-deepstackai-trigger as a docker container

Since node-deepstackai-trigger isn't in the Unraid app store we will need to manually setup the container. Create a new container with the following parameters

deepstack Unraid Docker node-deepstackai-trigger Unraid Docker

neilenns commented 4 years ago

Very nice! Yes, I'd love to have this as proper documentation for the wiki. If you stick it in a markdown file and make sure it passes markdownlint I'd be happy to include it. I think you can attach it all as a zip file here?

One thing I've also wanted to do is actually get this listed in the UnRaid app store but have never had any luck finding documentation on how to do that. Do you by any chance know the submission process?

the-speedmax commented 4 years ago

Tks for this nice "Howto". The only think that I modify was the Network Type. I was not able to figure how to change the Subnet of a Docker Network. So I used the Bridge. I forwarded port 4242 to 4241 and the 5000 to 83. It work!

image

image

Tks again!

MattW2 commented 4 years ago

Very nice! Yes, I'd love to have this as proper documentation for the wiki. If you stick it in a markdown file and make sure it passes markdownlint I'd be happy to include it. I think you can attach it all as a zip file here?

One thing I've also wanted to do is actually get this listed in the UnRaid app store but have never had any luck finding documentation on how to do that. Do you by any chance know the submission process?

I haven't tried to submit an application myself to the UnRaid app store but this is the best post I've found so far that points to how to do it https://forums.unraid.net/topic/55503-how-to-submit-new-docker-containers-to-community-apps/ and for specific directions on how to publish https://forums.unraid.net/topic/57181-docker-faq/#comment-566084

mattiapsu commented 4 years ago

Great documentation, and I believe I've followed exactly. I've used the bridge version and forwarded ports, which I prefer. I've even tried using the custom Network type. Unfortunately, it doesn't look like the trigger is pulling the images. The watch pattern is correct, and I've moved my aiinput folder to a number of places including the config folder.

This is all the log ever says. I assume 'unable to read' the secrets is a check before just picking up the setting.json in config, but maybe I am actually missing something. Not using secrets right now.

2020-11-05T23:30:17-05:00 [Main] **** 2020-11-05T23:30:17-05:00 [Main] Starting up version 5.4.0

2020-11-05T23:30:17-05:00 [Main] Timezone offset is 300 2020-11-05T23:30:17-05:00 [Main] Current time is Thu Nov 05 2020 23:30:17 GMT-0500 (Eastern Standard Time) 2020-11-05T23:30:17-05:00 [Settings] Unable to read the configuration file: ENOENT: no such file or directory, open '/run/secrets/settings'. 2020-11-05T23:30:17-05:00 [Settings] Loaded settings from /config/settings.json

neilenns commented 4 years ago

@mattiapsu please open a new github issue for your specific troubleshooting request. Make sure to include the entire output log as well as your settings.json and triggers.json file.

neilenns commented 3 years ago

Closing old issues.