# Unable to open/dev/gpiomem no such file or directory (version 4.1.0)

**URL:** https://discourse.nodered.org/t/unable-to-open-dev-gpiomem-no-such-file-or-directory-version-4-1-0/99033
**Category:** General
**Created:** [13 September 2025 07:09 UTC](https://discourse.nodered.org/t/unable-to-open-dev-gpiomem-no-such-file-or-directory-version-4-1-0/99033 "2025-09-13T07:09:55Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [13 September 2025 17:29 UTC](https://discourse.nodered.org/t/unable-to-open-dev-gpiomem-no-such-file-or-directory-version-4-1-0/99033/5 "2025-09-13T17:29:33Z")

</div>

It’s always wise to do a search to see if someone else has run into the same issue you are having. For instance this thread might be informative:

> [@Rpi-dht22 node RasPi 5 Bookworm "TypeError: failed to initialize"](https://discourse.nodered.org/t/rpi-dht22-node-raspi-5-bookworm-typeerror-failed-to-initialize/96825/6):
>
> Pretty sure they don't. I believe the basic issue is that the IO hardware on the Pi5 was changed, but Node-red on any Pi running Bookworm is likely to have problems with GPIOs. I do have BME280 and BME680 sensors. I do not have a Pi 5 and I am very reluctant to connect wires to my Pi 4 GPIO pins. It's too easy to kill the Pi. They are connected instead to ESP boards running Tasmota and (once Tasmota is configured) send the readings automatically over MQTT. There are suggested fixes online. …

---

_[View the full topic](https://discourse.nodered.org/t/unable-to-open-dev-gpiomem-no-such-file-or-directory-version-4-1-0/99033)._