My development pi3b sd card got bad so I reinstalled my system. I had a backup of all the flows but then the nodes were not installed. So I managed to get almost all things to get working except for ui_base, ui_link, ui_spacer and so on till ui_dropdown and ui_colour_picker. So I installed noder-red-dashboard, although deprecated, and then the error did not go away. In the manage palette screen there is a strange error: in the node-red-dashboard palette it saia 19x [object Object] where the last one had a yellow triangle in front with a ! in it. And then it says 21 nodes.
Assuming that you used the recommended pi install script, go into your .node-red folder and run npm remove node-red-dashboard npm install node-red-dashboard
And post the full output from that.
Then restart node red using node-red-stop node-red-start
If you still have the problem then post the full output from the stop/start.
up to date in 3s
pi@rbpi3b1:~ $ npm install node-red-dashboard
npm error code EINTEGRITY
npm error errno EINTEGRITY
npm error Invalid response body while trying to fetch https://registry.npmjs.org/node-red-dashboard: sha512-mcDq4bqhTVh7hn6kBmB6v8TfFfUQq+dhRxYsUtws0ZLidtVVxpAkH2hWI0Rgd13rLx//P7DxPRwZc64PS/O6oA== integrity checksum failed when using sha512: wanted sha512-mcDq4bqhTVh7hn6kBmB6v8TfFfUQq+dhRxYsUtws0ZLidtVVxpAkH2hWI0Rgd13rLx//P7DxPRwZc64PS/O6oA== but got sha512-2+Vr+gtlIxcjKlJq6+uIb54xIRLRWzLI7cUTUVGCG7k4ks3MOpqIaIoGf7yrSRX4qFzpdOpvaXoj+ggUOkH2JQ==. (549868 bytes)
npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-09-11T07_53_25_126Z-debug-0.log
pi@rbpi3b1:~ $
Once Node-RED has started, point a browser at http://192.168.17.71: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
These messages mean that the Node-RED dashboard nodes are still present in your flow, but the node is not installed.
pi@rbpi3b1:~ $ npm install node-red-dashboard
npm error code EINTEGRITY
npm error errno EINTEGRITY
npm error Invalid response body while trying to fetch https://registry.npmjs.org/node-red-dashboard: sha512-mcDq4bqhTVh7hn6kBmB6v8TfFfUQq+dhRxYsUtws0ZLidtVVxpAkH2hWI0Rgd13rLx//P7DxPRwZc64PS/O6oA== integrity checksum failed when using sha512: wanted sha512-mcDq4bqhTVh7hn6kBmB6v8TfFfUQq+dhRxYsUtws0ZLidtVVxpAkH2hWI0Rgd13rLx//P7DxPRwZc64PS/O6oA== but got
...
Implies that there was a problem when you tried to reinstall it. The error implies the tgz file that npm downloaded didn't match the hash it was given (it was changed or corrupted in transfer).
Best suggestion is to use the Node-RED palette manager to try and reinstall node-red-dashboard again, if the errors persist after reinstall, then you have a much bigger problem, something is messing with your traffic from the internet.
I prefer to use the command line in cases like this as it is easier to see what the problem is. @warnert did not notice the error when he initially installed using the palette manager, whereas it is clear to see when installing via the command line.
But yes, @warnert appears to have a major issue of some sort with his internet access.
I installed a lot of other nodes and that all went well. Only this one fails.
But (later) I will fire-up another PI3 and do, as I did with this one on a new sd-card, a clean install.
Note that if you are moving an node red system from one machine another, after installing node red, restore the full .node-red folder from the old machine except for the node_modules folder and the file package-lock.json. The go into the .node-red folder and run npm install
That will automatically install all the extra nodes that you had previously installed.
I have done a fresh install on an other sd-card and there it worked.
So I copied the .node-red directory from the new system to the old one (after a rename from the original one) without the node_modules map and did the npm install.
After that the problem was solved, I could install all the modules I needed.
