Anyway you can have it delete the images after they are processed by deepstack?
I've had the request before and resisted adding it. I don't believe the system should be responsible for managing files it didn't create.
Anyway you can have it delete the images after they are processed by deepstack?
If my folder gets to 100 images, the CPU for the trigger docker goes up to 80% constant. Does yours do that?
I'm only experimenting with 1 camera, but I have 20 altogether....
statusTopic
can no longer be set on the mqtt configuration in settings.json
. Overall status messages are always sent to the node-deepstackai-trigger/status
topic. This change aligns the status topic messages with the new MQTT messages that the system listens to for resetting statistics.node-deepstackai-trigger/statistics
topic. The trigger name, triggered count and analyzed file count are included, as well as a formatted string version suitable for presentation to a user. The per-trigger statistics are also available as variables for mustache templates.node-deepstackai-trigger/statistics
topics and sub-topics./statistics
and per-trigger statistics are available at /statistics/triggerName
. Statistics for all triggers can be retrieved from /statistics/all
.node-deepstackai-trigger/motion
MQTT messages with the name of the trigger in the message. This is similar to activating a trigger via the REST API and results in the trigger attempting to download a snapshot from the snapshotUri
specified in the trigger's configuration. node:slim
.docker-compose pull
then docker-compose up
to run with the new build. Unless you were using the statusTopic
feature (and I'm guessing nobody was) there are no config changes necessary to upgrade.Version 5.0.0 is out!
Breaking changes
statusTopic
can no longer be set on the mqtt configuration insettings.json
. Overall status messages are always sent to thenode-deepstackai-trigger/status
topic. This change aligns the status topic messages with the new MQTT messages that the system listens to for resetting statistics.
Non-breaking changes
To upgrade do
- Per-trigger statistics are now sent in new MQTT messages published to the
node-deepstackai-trigger/statistics
topic. The trigger name, triggered count and analyzed file count are included, as well as a formatted string version suitable for presentation to a user. The per-trigger statistics are also available as variables for mustache templates.- Statistics can be reset by publishing specific MQTT messages to the
node-deepstackai-trigger/statistics
topics and sub-topics.- Statistics can be read and reset via new REST APIs. Overall statistics are available at
/statistics
and per-trigger statistics are available at/statistics/triggerName
. Statistics for all triggers can be retrieved from/statistics/all
.- Triggers can be activated by sending
node-deepstackai-trigger/motion
MQTT messages with the name of the trigger in the message. This is similar to activating a trigger via the REST API and results in the trigger attempting to download a snapshot from thesnapshotUri
specified in the trigger's configuration.- Shutting down the system after a failed launch no longer throws an error.
- The underlying Linux variant used for the Docker image is now
node:slim
.- Pushbullet is now included in the settings JSON schema.
docker-compose pull
thendocker-compose up
to run with the new build. Unless you were using thestatusTopic
feature (and I'm guessing nobody was) there are no config changes necessary to upgrade.
2020-06-26T07:37:40-04:00 [Main] [MQTT] Unable to connect: connect ECONNREFUSED <ip>:1883
2020-06-26T07:37:40-04:00 [Main] ****************************************
2020-06-26T07:37:40-04:00 [Main] Startup cancelled due to errors. For troubleshooting assistance see https://github.com/danecreekphotography/node-deepstackai-trigger/wiki/Troubleshooting.
2020-06-26T07:37:40-04:00 [Main] Watching for changes to /run/secrets/settings
Thanks for the update. Do you have samples code on how you setup your dashboard in HA? Also, if i reboot my mqtt server i get "[Main] Startup cancelled due to errors." Is it possible to keep retrying instead of having to restart container again?
2020-06-26T07:37:40-04:00 [Main] [MQTT] Unable to connect: connect ECONNREFUSED <ip>:1883 2020-06-26T07:37:40-04:00 [Main] **************************************** 2020-06-26T07:37:40-04:00 [Main] Startup cancelled due to errors. For troubleshooting assistance see https://github.com/danecreekphotography/node-deepstackai-trigger/wiki/Troubleshooting. 2020-06-26T07:37:40-04:00 [Main] Watching for changes to /run/secrets/settings
annotateImage
is true
for a trigger handler but enableAnnotations
wasn't set to true
in the settings.json
file.docker-compose pull
then docker-compose up
.p
---------------------------------------
v1/restore
/v1/vision/detection
---------------------------------------
v1/vision/addmodel
--------------------------------------
v1/vision/listmodels
---------------------------------------
v1/vision/deletemodel
---------------------------------------
---------------------------------------
p
---------------------------------------
v1/restore
2020-07-02T09:20:14+01:00 [Main] Watching for changes to /run/secrets/settings
2020-07-02T09:20:14+01:00 [Main] Watching for changes to /run/secrets/triggers
2020-07-02T09:20:14+01:00 [Main] ****************************************
2020-07-02T09:20:14+01:00 [Main] Up and running!
2020-07-02T09:20:26+01:00 [Trigger Cat detector] /aiinput/Cat_20200523-075000 - Copy - Copy (2) - Copy - Copy.jpg: Analyzing
2020-07-02T09:20:26+01:00 [Trigger Cat detector] /aiinput/Cat_20200523-075100 - Copy - Copy (2) - Copy - Copy.jpg: Analyzing
2020-07-02T09:20:26+01:00 [Trigger Cat detector] /aiinput/Cat_20200523-074700 - Copy - Copy (2) - Copy - Copy.jpg: Analyzing
2020-07-02T09:20:26+01:00 [Trigger Dog detector] /aiinput/Dog_20200523-075000 - Copy - Copy (2) - Copy - Copy.jpg: Analyzing
For reference - the time now is 9:44
It never times out.. it never finishes analysis
In MQTT I can see the server is ONLINE
Thank youSee danecreekphotography/node-deepstackai-trigger for how to resolve this.
Version 5.0.0 is out!
Breaking changes
statusTopic
can no longer be set on the mqtt configuration insettings.json
. Overall status messages are always sent to thenode-deepstackai-trigger/status
topic. This change aligns the status topic messages with the new MQTT messages that the system listens to for resetting statistics.
Non-breaking changes
To upgrade do
- Per-trigger statistics are now sent in new MQTT messages published to the
node-deepstackai-trigger/statistics
topic. The trigger name, triggered count and analyzed file count are included, as well as a formatted string version suitable for presentation to a user. The per-trigger statistics are also available as variables for mustache templates.- Statistics can be reset by publishing specific MQTT messages to the
node-deepstackai-trigger/statistics
topics and sub-topics.- Statistics can be read and reset via new REST APIs. Overall statistics are available at
/statistics
and per-trigger statistics are available at/statistics/triggerName
. Statistics for all triggers can be retrieved from/statistics/all
.- Triggers can be activated by sending
node-deepstackai-trigger/motion
MQTT messages with the name of the trigger in the message. This is similar to activating a trigger via the REST API and results in the trigger attempting to download a snapshot from thesnapshotUri
specified in the trigger's configuration.- Shutting down the system after a failed launch no longer throws an error.
- The underlying Linux variant used for the Docker image is now
node:slim
.- Pushbullet is now included in the settings JSON schema.
docker-compose pull
thendocker-compose up
to run with the new build. Unless you were using thestatusTopic
feature (and I'm guessing nobody was) there are no config changes necessary to upgrade.
When the container starts, it doesn't seem to do anything, i have setup triggers and settings, images folder via samba mount but container logs shows no activity.
I'd like to try "snapshotUri" instead watchPattern , can you say what "snapshotUri " i should use.