node-red / node-red/node-red-nodes

Multiple "rpi-gpio in" doesn't work on Raspberry Pi 5

Open
#1,085 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.1k
Forks
612
Avg merge
13h 57m
Merged PRs (30d)
3

Description

Which node are you reporting an issue on?

rpi-gpio in

What are the steps to reproduce?

[ { "id": "78b4d995a81ab599", "type": "tab", "label": "Flow 1", "disabled": false, "info": "", "env": [] }, { "id": "a2c9b52862aa4d95", "type": "rpi-gpio in", "z": "78b4d995a81ab599", "name": "", "pin": "4", "intype": "tri", "debounce": "25", "read": false, "bcm": true, "x": 590, "y": 280, "wires": [ [ "cfbc42146f0c4c55" ] ] }, { "id": "cfbc42146f0c4c55", "type": "debug", "z": "78b4d995a81ab599", "name": "debug 1", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 780, "y": 280, "wires": [] }, { "id": "58d56a69c882d5f3", "type": "debug", "z": "78b4d995a81ab599", "name": "debug 2", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "false", "statusVal": "", "statusType": "auto", "x": 780, "y": 340, "wires": [] }, { "id": "8409d6f2d0c9f9bf", "type": "rpi-gpio in", "z": "78b4d995a81ab599", "name": "", "pin": "4", "intype": "tri", "debounce": "25", "read": false, "bcm": true, "x": 590, "y": 340, "wires": [ [ "58d56a69c882d5f3" ] ] } ]

What happens?

When there are multiple "rpi-gpio in" node acessing the same GPIO, only the first node works as expected. The remaining nodes are not working.

What do you expect to happen?

The same flow work on Raspberry Pi 4, so it should work on Pi 5 too.

Please tell us about your environment:
  • Node-RED version: v4.0.5
  • node.js version: v20.18.0
  • npm version: v10.8.2
  • Platform/OS: Raspberry Pi OS Bookworm Desktop 64-bit
  • Browser: Edge

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the rpi-gpio in node implementation and its Raspberry Pi 5 GPIO handling; compare how multiple nodes request the same pin using the provided flow. Reproduce on Raspberry Pi OS Bookworm with Node-RED v4.0.5, then verify that both debug nodes receive input events while preserving the Raspberry Pi 4 behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs, raspberry-pi
Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.