# RBPi GPIO issues

**URL:** <https://discourse.nodered.org/t/rbpi-gpio-issues/84519>\
**Category:** General\
**Tags:** gpio\
**Created:** [13 January 2024 15:55 UTC](https://discourse.nodered.org/t/rbpi-gpio-issues/84519 "2024-01-13T15:55:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![edje11](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/edje11/32/572_2.png) [@edje11](https://discourse.nodered.org/u/edje11)\
**Post date:** [13 January 2024 19:16 UTC](https://discourse.nodered.org/t/rbpi-gpio-issues/84519/2 "2024-01-13T19:16:18Z")

</div>

Have a look at this topic;

> [@Raspi Zero 2W GPIO](https://discourse.nodered.org/t/raspi-zero-2w-gpio/84484):
>
> Raspi GPIOs unusable in up to date installation (Nodes say "not available") node red v3.1.3 running on bullseye Linux 6.1.21-v7+ #1642 SMP Mon Apr 3 17:20:52 BST 2023 armv7l GNU/Linux) on Raspi Zero 2W, Syslog level trace says: [warn] rpi-gpio : Raspberry Pi specific node set inactive fixed after reading this: [Rpi-gpio : Raspberry Pi specific node set inactive](https://discourse.nodered.org/t/rpi-gpio-raspberry-pi-specific-node-set-inactive/53569) by manually installing the python3 libs: sudo apt install python3-rpi.gpio I have several node reds running on different ol…

---

_[View the full topic](https://discourse.nodered.org/t/rbpi-gpio-issues/84519)._