Running Node-RED update for user pi at /home/pi on raspbian
This can take 20-30 minutes on the slower Pi versions - please wait.
Stop Node-RED ✔
Remove old version of Node-RED ✔
Remove old version of Node.js ✔
Install Node.js LTS ✔ Node v12.19.0 Npm 6.14.8
Clean npm cache ✔
Install Node-RED core ✔ 1.2.3
Move global nodes to local -
Install extra Pi nodes -
Npm rebuild existing nodes -
Add shortcut commands ✔
Update systemd script ✔
Any errors will be logged to /var/log/nodered-install.log
All done.
You can now start Node-RED with the command node-red-start
or using the icon under Menu / Programming / Node-RED
Then point your browser to localhost:1880 or http://{your_pi_ip-address}:1880
Started Tue 10 Nov 08:38:22 GMT 2020 - Finished Tue 10 Nov 08:45:47 GMT 2020
pi@raspberrypi:~ $
pi@raspberrypi:~ $ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://172.16.10.234: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.
10 Nov 08:54:26 - [info]
Welcome to Node-RED
===================
10 Nov 08:54:26 - [info] Node-RED version: v1.2.3
10 Nov 08:54:26 - [info] Node.js version: v12.19.0
10 Nov 08:54:26 - [info] Linux 5.4.51-v7+ arm LE
10 Nov 08:54:28 - [info] Loading palette nodes
10 Nov 08:54:32 - [info] Settings file : /home/pi/.node-red/settings.js
10 Nov 08:54:32 - [info] Context store : 'default' [module=memory]
10 Nov 08:54:32 - [info] User directory : /home/pi/.node-red
10 Nov 08:54:32 - [warn] Projects disabled : editorTheme.projects.enabled=false
10 Nov 08:54:32 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
10 Nov 08:54:32 - [info] Creating new flow file
10 Nov 08:54:32 - [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.
---------------------------------------------------------------------
10 Nov 08:54:32 - [info] Server now running at http://127.0.0.1:1880/
10 Nov 08:54:32 - [info] Starting flows
10 Nov 08:54:32 - [info] Started flows
pi@raspberrypi:~ $ node-red-stop
Stop Node-RED
Use node-red-start to start Node-RED again
pi@raspberrypi:~ $ npm install node-red-dashboard
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.
+ [email protected]
added 83 packages from 60 contributors and audited 83 packages in 19.949s
found 0 vulnerabilities
pi@raspberrypi:~ $ sudo systemctl enable nodered.service
Created symlink /etc/systemd/system/multi-user.target.wants/nodered.service → /lib/systemd/system/nodered.service.
Even though I enabled run on boot, I couldn't find the web page activated until I manually ran it using node-red-start Also, the dashboard nodes do not appear in the list of nodes after the attempted installation. Next, open up nodeRed in browser, go to menu, manage pallete --> install tab --> search for node-red-dashboard, then select install.
Installation takes about 1 minute, then the nodes can immediately be found under "dashboard" in the nodes list. The color of these nodes is a light ocean blue.