Run the install in a terminal. Go to your .node-red folder and run npm install node-red-dashboard
and post the output here. I suspect the problem you are seeing is not actually related to the dashboard.
No reason not to. As Colin says, give it time. If you get stuck with the serial port upgrade as many people seem to, the last resort is to simply delete your node_modules folder and do npm install - all in your userDir folder of course (normally ~/.node-red). That will take time on an old Pi but it will properly rebuild everything. Just make sure that Node.js and apt installs are all up-to-date first.
Yeah, but I would prefer to leave well enough alone.
Alas it (that machine) is my DNS server so my internet access is not very good just now.
And as I ssh'ed into it from this machine, I can't turn off the ethernet and change the DNS and re-activate it.
I think that would not do the ssh link to the RasPi any good and therefore not help the dashboard being updated.
Well you should be able to SSH into it using its IP address (assuming you and it are both on the same network anyway. If not, maybe you have another device you can use as a jump-box? SSH into the other device and set up port forwarding over SSH). That won't be affected by any DNS changes other than maybe temporarily losing the ability to look up addresses on the Internet.
As the Pi is Linux based, you can easily change the network settings on the fly and then just reboot. Of course, there is always the danger you won't then be able to access it at all Probably not a problem if you are local to it but a pain otherwise.
Yes, so now: This machine is ssh to the RasPi, updating the dashboard.
That machine - raspi - is also the DNS for all my local network.
The pi (3B) is kinda busy.
The DNS was down for a while. It seems to be happier now.
If I wanted to change the DNS on this machine:
We've agreed (I believe) that for the change of the DNS to happen I have to shut down the ethernet port (on this machine) and bring it back up.
So what would happen to the SSH session to the RasPi?
When I get some more $$$ I may have to get another RasPi as a second DNS to avert this problem in the future.
And you want to change the DNS settings on DEVICE? But don't want to drop the SSH session?
Not what I thought you were trying to do.
In that case, you will want to install TMUX (or at least SCREEN) on the Pi. This will let you be disconnected from the remote ssh connection but without losing your BASH session. So when your local device loses network connection for any reason, you can pick up the remote session where you left off.
But this is the tail of what was spat to the console:
make: *** [serialport.target.mk:112: Release/obj.target/serialport/src/serialport.o] Error 1
make: Leaving directory '/home/pi/.node-red/node_modules/serialport/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (events.js:314:20)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
gyp ERR! System Linux 5.10.17-v7+
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/pi/.node-red/node_modules/serialport
gyp ERR! node -v v12.22.0
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm WARN node-red-contrib-ui-led@0.3.3 requires a peer of node-red-dashboard@2.23.x but none is installed. You must install peer dependencies yourself.
npm WARN ts-lib-utils@2.2.0 requires a peer of typescript@2 || 3 but none is installed. You must install peer dependencies yourself.
npm WARN tsutils@3.17.1 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
npm WARN type-coverage-core@2.4.1 requires a peer of typescript@2 || 3 but none is installed. You must install peer dependencies yourself.
npm WARN node-red-project@0.0.1 No repository field.
npm WARN node-red-project@0.0.1 No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! serialport@6.2.2 install: `prebuild-install || node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the serialport@6.2.2 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2021-04-07T12_25_28_847Z-debug.log
pi@BedPi:~/.node-red $
It is the bit before that we need, I did say to post it all, I hope you haven't lost it. Are you using the serial port node? If not then uninstall it. It is that which is causing the problem, not the dashboard.
Probably not a problem if you are local to it but a pain otherwise.
