Suddenly 2 of my rasberry stopped working the same problem. The node rpi-gpio out is grey and disappered from the node collection. In the flow is says "Unknown: rpi-gpio out".
I've upgraded Raspian to latest. Removed from palette the node-red-node-pi-gpio. Restarted and reinstalled it. But no luck. My Rasperrys is one pi4 and one pi zero W. I believe it happend on the 6/12 if it's any lead.
The only thing I've done is working on a bash script on another machine totaly irrelevant. The pi4 is after i detected the problem upgraded to latest Raspian and reinstalled the node. Nothing else have I done. And about cache in browser is also tested. Still problem.
For it to happen on two pis at the same time without you doing anything to the pis means that is something external to the pis, or it is a most remarkable co-incidence.
Open the browser console and see if you see any errors when you refresh the page
Also stop node red and start it again in a terminal and post the output here. node-red-stop node-red-start
Starting as a systemd service.
8 Dec 21:56:49 - [info]
Welcome to Node-RED
===================
8 Dec 21:56:49 - [info] Node-RED version: v1.3.4
8 Dec 21:56:49 - [info] Node.js version: v10.24.0
8 Dec 21:56:49 - [info] Linux 5.10.63-v7l+ arm LE
8 Dec 21:56:51 - [info] Loading palette nodes
8 Dec 21:56:53 - [info] Settings file : /home/pi/.node-red/settings.js
8 Dec 21:56:53 - [info] Context store : 'default' [module=memory]
8 Dec 21:56:53 - [info] User directory : /home/pi/.node-red
8 Dec 21:56:53 - [warn] Projects disabled : editorTheme.projects.enabled=false
8 Dec 21:56:53 - [info] Flows file : /home/pi/.node-red/flows_honshus.json
(node:2245) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, scandir '/usr/lib/node_modules/node-red/node_modules/@node-red/nodes/examples'
(node:2245) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2245) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
8 Dec 21:56:53 - [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.
---------------------------------------------------------------------
8 Dec 21:56:53 - [info] Server now running at http://127.0.0.1:1880/
8 Dec 21:56:53 - [info] Starting flows
8 Dec 21:56:54 - [info] [Bme280:BME280] Initializing on bus1 addr:119
8 Dec 21:56:54 - [info] Started flows
8 Dec 21:56:55 - [info] [mqtt-broker:server] Connected to broker: mqtt://192.168.200.1:1883
Found BMx280 chip ID 0x60 on bus i2c-1, address 0x77
8 Dec 21:56:55 - [info] [BME280:BME280] Sensor BME280 initialized.
Hi!
I do think you are on something here. I tried the install script earlier today. It detected that I ran node10 and let me choose what to do. I don't remember what the script said but I thought i've done correct. The script downloaded I believe 1,4Gb and needed a reboot. Therefore I thought thats done. What to do next?
When I try the script now it says:
Running Node-RED install for user pi at /home/pi on raspbian
Nodejs 10 is no longer supported.
You can update to the latest Node-RED 1.x version by adding --nodered-version="1.3.5"
to that install command. If in doubt this is the safer option.
Or you can force an install of node 12 or 14 by using the --node12, --node14 or --node16 parameter
However doing so may break some nodes that may need re-installing manually.
Generally it is recommended to upgrade all nodes to their latest versions before upgrading.
Please backup your installation and flows before upgrading.
I ran the install script again with --node14 option and it worked fine. After that I had to edit the settings.js to set the uiHost: "192.168.200.232"
Now it's up and running using chrome browser but for some reason it won't work with my old safari, but thats ok.