I just started to use Raspberry OS Full with applications. First when I installed it, noticed, that it has built in Node-RED (so cool). I tried it without any modification and I manage to control GPIO pin 2 without any issue through Node-RED. Then I did an upgrade according to this article:
Also I setup Node-RED to start as a service. I added a few nodes to it, like the node-red-contrib-s7 and node-red-dashboard. I setup PIGPIOD to start automatically after reboot with this command:
sudo systemctl enable pigpiod
Additionally I setup to run my .py program, which controls the MeArm Robot with Crontab with the help of this article (you can find the autostart description in the middle):
I wanted to do the same, as before, control the same GPIO 2 with node-red-node-pi-gpio, but now it says not available.
- I am using Rasberry Pi 4 with 8 gb RAM.
- The newest Rasberry OS is installed on it.
- GPIO-s are working, if I run a python program on it.
- Doesn't matter if I set it up as output or input, it won't work. Always show not available.
- node-red startup log
"pi@zeus:~ $ node-red startup log
10 Nov 19:14:50 - [info]
Welcome to Node-RED
10 Nov 19:14:50 - [info] Node-RED version: v2.1.3
10 Nov 19:14:50 - [info] Node.js version: v12.22.5
10 Nov 19:14:50 - [info] Linux 5.10.63-v7l+ arm LE
10 Nov 19:14:51 - [info] Loading palette nodes
10 Nov 19:14:53 - [info] Dashboard version 3.1.1 started at /ui
10 Nov 19:14:53 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
10 Nov 19:14:53 - [info] Settings file : /home/pi/.node-red/settings.js
10 Nov 19:14:53 - [info] Context store : 'default' [module=memory]
10 Nov 19:14:53 - [info] User directory : /home/pi/.node-red
10 Nov 19:14:53 - [warn] Projects disabled : editorTheme.projects.enabled=false
10 Nov 19:14:53 - [info] Flows file : /home/pi/.node-red/startup
10 Nov 19:14:53 - [info] Creating new flow file
10 Nov 19:14: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
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."
- Export of the flow with all the nodes, what I have now online. Only using the S7 and GPIO nodes.
- I'm not using any extra hardware.
- Start and Stop the Node-RED did not help.
- I even disabled the script Autostart function, but it did not help either.
This is the last step what I want to achieve on Raspberry to my Master Thesis, besides that the missing part is setting up the Node-RED communicating with the Siemens S7 300 PLC and Raspberry correctly and make a nice dashboard for it.
If you have any idea how to get GPIO alive again, please let me know. I don't want to start from the beginning again. The strange thing, that the first time with brand new Raspberry OS without any Node-RED upgrade it worked