That isn't the issue (the nodjs version). The node installed ok this time. I think the issue linked to is actually that the build tools were not installed 2021-08-12T09:23:52.982Z [err] npm ERR! gyp ERR! stack Error: not found: make
In a terminal run node-red-stop node-red-start
and post the output here.
[Edit] did you remember to refresh the browser window?
The minimum node version currently required by node-RED is v12.
(I would use v12 instead of v13 as even numbers have LTS - Supported Node versions : Node-RED)
But take the advise of more senior advisers, I'm a minnow in the forum
It looks like it only needed some time Now it is working
Didn't do anything.
demokedes@NodeRed:~/.node-red$ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://10.0.0.4:1880
On Pi Node-RED works better with the Firefox or Chrome browser
Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot
To find more nodes and example flows - go to http://flows.nodered.org
Starting as a systemd service.
14 Feb 18:20:58 - [info]
Welcome to Node-RED
===================
14 Feb 18:20:58 - [info] Node-RED version: v2.2.0
14 Feb 18:20:58 - [info] Node.js version: v16.14.0
14 Feb 18:20:58 - [info] Linux 5.4.0-1069-azure x64 LE
14 Feb 18:20:58 - [info] Loading palette nodes
Mon, 14 Feb 2022 18:21:01 GMT node-telegram-bot-api deprecated Automatic enablin g of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. at node:internal/ modules/cjs/loader:1103:14
14 Feb 18:21:02 - [info] RedBot version: 0.19.11 (node-red-contrib-chatbot)
14 Feb 18:21:04 - [info] Dashboard version 3.1.5 started at /ui
14 Feb 18:21:05 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
(node:6816) [DEP0128] DeprecationWarning: Invalid 'main' field in '/home/demoked es/.node-red/node_modules/azure-iothub/node_modules/azure-iot-amqp-base/package. json' of 'main.js'. Please either fix that or report it to the module author
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:6816) [DEP0128] DeprecationWarning: Invalid 'main' field in '/home/demoked es/.node-red/node_modules/node-red-contrib-azure-iot-hub/node_modules/azure-iot- amqp-base/package.json' of 'main.js'. Please either fix that or report it to the module author
(node:6816) [DEP0128] DeprecationWarning: Invalid 'main' field in '/home/demoked es/.node-red/node_modules/azure-iot-device-amqp-ws/node_modules/azure-iot-amqp-b ase/package.json' of 'main.js'. Please either fix that or report it to the modul e author
(node:6816) [DEP0128] DeprecationWarning: Invalid 'main' field in '/home/demoked es/.node-red/node_modules/azure-iot-device-amqp-ws/node_modules/azure-iot-amqp-b ase/package.json' of 'main.js'. Please either fix that or report it to the modul e author
14 Feb 18:21:05 - [info] Settings file : /home/demokedes/.node-red/settings.js
14 Feb 18:21:05 - [info] Context store : 'default' [module=memory]
14 Feb 18:21:05 - [info] User directory : /home/demokedes/.node-red
14 Feb 18:21:05 - [warn] Flows file name not set. Generating name using hostname .
14 Feb 18:21:05 - [info] Flows file : /home/demokedes/.node-red/flows_NodeRe d.json
14 Feb 18:21:05 - [info] Server now running at http://127.0.0.1:1880/
14 Feb 18:21:05 - [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.
---------------------------------------------------------------------
14 Feb 18:21:05 - [info] Starting flows
14 Feb 18:21:05 - [info] Started flows