Living dangerously… upgrading Node-RED to version 2.2.2 brought me a few surprises. But, all is well and smooth now.
Starting point – I was running on an OrangePiPC2 Node-RED 1.6 with node version 8. As the UI started to become sluggish, I thought an upgrade to version 2 would be a good idea.
I stopped node-red with the usual
node-red-stop command and issued my usual
npm install -g --unsafe-perm node-red node-red-admin and after execution, opened the browser at the usual URL for node-red and …. nothing. Reviewing the log, it was full of ERROR and WARNING messages.
Google is your friend – and the friend told me to update node. So it gave me a number of solution for each problem in turn. The final working ones are in the following list:
Node-RED not running after update – update Node
- Node-RED not running after update – update Node
- rbe node errors – go to .node-red/node_modules and
npm remove node-red-node-rbe
- Tasmota node not working – reconfigure the MQTT server details
- serialport didn’t compile properly – upgrade to node 16 using the script from https://nodered.org/docs/getting-started/raspberrypi which is
bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered) --node16
RTFM from Node-RED.org, in particular this page https://nodered.org/docs/getting-started/raspberrypi and when using the parameter –node16 on a OrangePi, you should be at the desired point fairly quickly.