I am running latest version of node-red 1.3.5 and node JS v14.17.
startup log looks like this
5 Jun 09:55:30 - [warn] ------------------------------------------------------
25 Jun 09:55:30 - [info] Settings file : /home/niclas/.node-red/settings.js
25 Jun 09:55:30 - [info] Context store : 'default' [module=memory]
25 Jun 09:55:30 - [info] User directory : /home/niclas/.node-red
25 Jun 09:55:30 - [warn] Projects disabled : editorTheme.projects.enabled=false
25 Jun 09:55:30 - [info] Flows file : /home/niclas/.node-red/stop
25 Jun 09:55:30 - [info] Creating new flow file
25 Jun 09:55:30 - [debug] loaded flow revision: d751713988987e9331980363e24189ce
25 Jun 09:55:30 - [debug] red/runtime/nodes/credentials.load : no user key present
25 Jun 09:55:30 - [debug] red/runtime/nodes/credentials.load : using default key
25 Jun 09:55:30 - [debug] red/runtime/nodes/credentials.load : keyType=system
25 Jun 09:55:30 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
25 Jun 09:55:30 - [trace] runtime event: {"id":"runtime-state","retain":true}
25 Jun 09:55:30 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"d751713988987e9331980363e24189ce"},"retain":true}
25 Jun 09:55:30 - [info] Starting flows
25 Jun 09:55:30 - [debug] red/nodes/flows.start : starting flow : global
25 Jun 09:55:30 - [trace] [flow:global] start flow [global]
25 Jun 09:55:30 - [trace] runtime event: {"id":"runtime-state","retain":true}
25 Jun 09:55:30 - [info] Started flows
25 Jun 09:55:30 - [info] Server now running at http://127.0.0.1:1880/
**niclas@niclas-desktop** : **~** $ node-red
25 Jun 10:30:06 - [info]
Welcome to Node-RED
===================
25 Jun 10:30:06 - [info] Node-RED version: v1.3.5
25 Jun 10:30:06 - [info] Node.js version: v14.17.1
25 Jun 10:30:06 - [info] Linux 4.9.201-tegra arm64 LE
25 Jun 10:30:07 - [info] Loading palette nodes
25 Jun 10:30:07 - [debug] Module: node-red-contrib-deepstack 0.1.2 /home/niclas/.node-red/node_modules/node-red-contrib-deepstack
25 Jun 10:30:07 - [debug] Module: node-red-dashboard 2.29.3 /home/niclas/.node-red/node_modules/node-red-dashboard
25 Jun 10:30:07 - [debug] Module: node-red-node-rbe 0.5.0 /usr/local/lib/node_modules/node-red/node_modules/node-red-node-rbe
25 Jun 10:30:07 - [debug] Module: node-red-node-tail 0.3.1 /usr/local/lib/node_modules/node-red/node_modules/node-red-node-tail
25 Jun 10:30:08 - [info] Dashboard version 2.29.3 started at /ui
25 Jun 10:30:08 - [warn] ------------------------------------------------------
25 Jun 10:30:08 - [warn] [node-red-contrib-deepstack/deepstack-object-detection] Error:
Something went wrong installing the "sharp" module
libvips-cpp.so.42: cannot open shared object file: No such file or directory
- Remove the "node_modules/sharp" directory then run
"npm install --ignore-scripts=false --verbose sharp" and look for errors
- Consult the installation documentation at https://sharp.pixelplumbing.com/install
- Search for this error at https://github.com/lovell/sharp/issues
25 Jun 10:30:08 - [warn] [node-red-contrib-deepstack/deepstack-face-recognition] Error:
Something went wrong installing the "sharp" module
libvips-cpp.so.42: cannot open shared object file: No such file or directory
- Remove the "node_modules/sharp" directory then run
"npm install --ignore-scripts=false --verbose sharp" and look for errors
- Consult the installation documentation at https://sharp.pixelplumbing.com/install
- Search for this error at https://github.com/lovell/sharp/issues
25 Jun 10:30:08 - [warn] ------------------------------------------------------
25 Jun 10:30:08 - [info] Settings file : /home/niclas/.node-red/settings.js
25 Jun 10:30:08 - [info] Context store : 'default' [module=memory]
25 Jun 10:30:08 - [info] User directory : /home/niclas/.node-red
25 Jun 10:30:08 - [warn] Projects disabled : editorTheme.projects.enabled=false
25 Jun 10:30:08 - [info] Flows file : /home/niclas/.node-red/flows_niclas-desktop.json
25 Jun 10:30:08 - [info] Server now running at http://127.0.0.1:1880/
25 Jun 10:30:08 - [debug] loaded flow revision: 36bd8b18a6bd616995421873f5f84039
25 Jun 10:30:08 - [debug] red/runtime/nodes/credentials.load : no user key present
25 Jun 10:30:08 - [debug] red/runtime/nodes/credentials.load : using default key
25 Jun 10:30:08 - [debug] red/runtime/nodes/credentials.load : keyType=system
25 Jun 10:30:08 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
25 Jun 10:30:08 - [trace] runtime event: {"id":"runtime-state","retain":true}
25 Jun 10:30:08 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"36bd8b18a6bd616995421873f5f84039"},"retain":true}
25 Jun 10:30:08 - [info] Waiting for missing types to be registered:
25 Jun 10:30:08 - [info] - server
25 Jun 10:30:08 - [info] - deepstack-object-detection
25 Jun 10:30:08 - [trace] runtime event: {"id":"runtime-state","payload":{"error":"missing-types","type":"warning","text":"notification.warnings.missing-types","types":["server","deepstack-object-detection"]},"retain":true}
25 Jun 10:30:38 - [trace] comms.open kxLBOHKvf3wUdBPUMYSPzJ67rYNWcglTrdiMzIZ5ewE=
How do you rate the performance of Deepstack when running on the Jetson? Is it utilizing the GPU?
I run YOLO v4 on my Jetson's and used the guides in here:
Also interesting with Deepstack is of course that you can register faces with it