# Rpi-gpio : Raspberry Pi specific node set inactive
**URL:** https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569
**Category:** General
**Created:** [11 November 2021 10:59 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569 "2021-11-11T10:59:41Z")
**Posts on this page:** 19
**Page:** 4
### Author:  [@alanmasu](https://discourse.nodered.org/u/alanmasu)
#### Post date: [11 November 2021 20:02 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/61 "2021-11-11T20:02:16Z")
Yes, I'm sure that I've done an injection, before nodes were connected to an MQTT-out node, so they got at least one message
---
### Author:  [@alanmasu](https://discourse.nodered.org/u/alanmasu)
#### Post date: [11 November 2021 20:04 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/62 "2021-11-11T20:04:19Z")
ok, but the "N/A" is not normal as we have now!
Alan
[edit]
and I've got 4 LEDs physically connected to GPIOs and they were not working!
---
### Author:  [@ScheepersJohan](https://discourse.nodered.org/u/ScheepersJohan)
#### Post date: [11 November 2021 20:06 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/63 "2021-11-11T20:06:20Z")
> [@alanmasu](#):
>
> "N/A" is not normal
Not normal as my node-red is running on a AWS EC2 and not a PI
---
### Author:  [@alanmasu](https://discourse.nodered.org/u/alanmasu)
#### Post date: [11 November 2021 20:08 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/64 "2021-11-11T20:08:40Z")
> [@ScheepersJohan](#):
>
> Not normal as my node-red is running on a AWS EC2 and not a PI
Yes, but I'm not working in AWS but in a Pi! And, as I just saw, the GPIOs were broken!!
---
### Author:  [@ScheepersJohan](https://discourse.nodered.org/u/ScheepersJohan)
#### Post date: [11 November 2021 20:08 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/65 "2021-11-11T20:08:50Z")
> [@alanmasu](#):
>
> and I've got 4 LEDs physically connected to GPIOs and they were not working!
Inject a 1 into the GPIO
The bottom should show 1 for the pin to go high
---
### Author:  [@alanmasu](https://discourse.nodered.org/u/alanmasu)
#### Post date: [11 November 2021 20:11 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/66 "2021-11-11T20:11:53Z")
At the moment that I've did the screen, GPIOs are already connected to MQTT nodes and they receive data from network
Alan
[edit]
so at the moment are receiving `0` from MQTT
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [11 November 2021 20:17 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/67 "2021-11-11T20:17:19Z")
> [@dceejay](#):
>
> I have a beta version that may help
Out of interest, what was the issue?
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [11 November 2021 21:13 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/68 "2021-11-11T21:13:01Z")
The base OS has now finally dropped python2 and also finally which python points to python3 - so we have to ensure we use that (and yet drop back if not available)
I have now pushed 2.0.0 to be the default install.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [11 November 2021 21:40 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/69 "2021-11-11T21:40:56Z")
Ah yes, thanks.
---
### Author:  [@cymplecy](https://discourse.nodered.org/u/cymplecy)
#### Post date: [12 November 2021 05:31 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/70 "2021-11-12T05:31:04Z")
Just confirming that re-running the install script got my new install up and running and controlling pins 🙂
Interestingly though - if I type python2 in a command prompt I get
---
### Author:  [@cymplecy](https://discourse.nodered.org/u/cymplecy)
#### Post date: [12 November 2021 05:58 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/71 "2021-11-12T05:58:43Z")
Aah - it's that it doesn't have an RPi.GPIO python2 library
---
### Author:  [@ApronCricket](https://discourse.nodered.org/u/ApronCricket)
#### Post date: [16 November 2021 16:06 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/72 "2021-11-16T16:06:11Z")
Just in case anyone else is struggling with this as I have been for a few days.
I have one particular Pi running OMV backups and use GPIO for cooling and LED status.
Having tried the install script and everything else I could think of, it was installing the python3-rpi.gpio package that fixed it for me.
'sudo apt-get install python3-rpi.gpio' and everything worked after a reboot.
Thanks @Colin
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [16 November 2021 16:35 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/73 "2021-11-16T16:35:18Z")
Welcome to the forum @ApronCricket.
What version of node-red-node-pi-gpio are you using? You can check in Manage Palette.
---
### Author:  [@serimi](https://discourse.nodered.org/u/serimi)
#### Post date: [16 November 2021 18:29 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/74 "2021-11-16T18:29:55Z")
I was running into the same issue as the thread opener and this ultimately fixed my issue.
> [@Colin](#):
>
> I am not very hopeful but worth trying.
> `sudo apt install python3-rpi.gpio`
> then restart node-red. In fact maybe a good idea to reboot.
All the other later-mentioned solutions did solve the issue for me.
Thanks for all your effort guys, highly appreciate it!
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [16 November 2021 19:04 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/75 "2021-11-16T19:04:15Z")
The same question for you, what version of the node are you running?
---
### Author:  [@ApronCricket](https://discourse.nodered.org/u/ApronCricket)
#### Post date: [16 November 2021 19:10 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/76 "2021-11-16T19:10:19Z")
I'm on 2.0.0 now. It was the upgrade to this that started the issue.
I'm not sure which version I was on before the update though.
I have a standard Pi OS install, with OMV and Node Red only.
I updated everything on the OS and OMV, then ran through the available updates in the Node Red pallet manager - bringing me up to node-red-node-pi-gpio 2.0.0.
I noticed the GPIO issues, so ran the update script for Node Red. This didn't work, so I did the update script with --update-nodes which didn't help, then with --node16 just in case.
After fumbling for a day I checked the startup logs in node red and found the 'Raspberry Pi specific node set inactive' warning, which led me here. I tried the 2.0.0-beta4, then back to 2.0.0, then finally tried phython3-rpi.gpio.
I have a few more Pi's to update this week with various NR versions, so hopefully they go smoothly.
Let me know if I can provide anything further to help. I'm by no means an expert, but can follow instructions.
---
### Author:  [@serimi](https://discourse.nodered.org/u/serimi)
#### Post date: [16 November 2021 19:38 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/77 "2021-11-16T19:38:57Z")
> [@Colin](#):
>
> The same question for you, what version of the node are you running?
Sorry I should have supplied that information 🙂 While going through my logs I realised that for me it was NOT upgrading to Bullseye. It rather started like this: I was going through an update run on multiple devices and installed Node-RED version: v2.1.3 using the node-red script:
```auto
bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)
```
As a consequence I had an issue with the GPIOs appearing as "N/A" in Node-RED. I then went through Linux update / upgrade commands hoping it would solve it and ran into the system update to Bullseye. The update didn't change anything.
Then I consulted this thread and using the command below It was fixed:
> [@Colin](#):
>
> sudo apt install python3-rpi.gpio
Hope this somehow helps.
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [17 November 2021 09:03 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/78 "2021-11-17T09:03:45Z")
I meant the version of the GPIO node. There is now a further new version of that node available.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [1 December 2021 09:04 UTC](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569/79 "2021-12-01T09:04:35Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
[Previous page](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569.md?page=3)