I ran into the same thing on a Pi 5. As far as I understand it, the cause is the Pi 5 itself rather than OpenPlotter: the GPIO pins now go through the new RP1 chip, and the old RPi.GPIO library (which the classic rpi-gpio nodes rely on) does not support it. pigpiod does not support the Pi 5 either, so the "remote GPIO" nodes are no help there.
What worked for me without waiting for a fixed node:
1. Check that the pins respond at OS level first:
Code:
pinctrl get 17
pinctrl set 17 op dh # output, drive high
pinctrl set 17 op dl # output, drive low
gpioinfo | head -40 # from the gpiod package
2. In Node-RED, use an exec node with the command "pinctrl set 17 op" and append msg.payload ("dh" or "dl"). For inputs, an exec node running "pinctrl lev 17" triggered by an inject node every second is crude, but reliable.
3. If you have Python scripts that import RPi.GPIO, the "rpi-lgpio" package is a drop-in replacement that runs on top of lgpio (uninstall RPi.GPIO first, they clash).
Also check that the node-red user is in the "gpio" group (groups node-red or groups pi), otherwise everything fails silently.
If someone has a native Node-RED GPIO node that works on Pi 5 + Bookworm, I would also like to know, it would be cleaner than exec nodes.