Issue with node-red-node-pi-neopixel on CM4 / RPi4 with Debian Bookworm 64 Bit

Hardware
1

Hello, im new to NodeRed.
have trouble to get the node-red-node-pi-neopixel node working.
It was working fine with Debian Bullseye, but there I got issues with my Serial HAT, so I had to upgrade to a more recent kernel/os.

Im running:
Debian Bookworm Lite 64Bit on an CM4 on a Tofu Board.
Node-Red V4.0.9 installed as root (---break-system-packages)

The I can control the Neopixel LEDs from python without issues, just from Node-Red it dosen´t work.
The node shows: "node-red:rpi-gpio.status.not-available" and does nothing else.

Can someone hint me to the right path how to solve it?
Thanks

2

I found the Issue:
The code checks for the ": BCM" string in /proc/cpuinfo
But the the CM4 Module with Debian Bookworm 64 Bit, does not show that information.
As Hardware it shows a "Raspberry Pi Compute Module 4 Rev 1.1" string.

I created a merge request for the fix:

1 Like
3

Any chance anyone has looked at the CM5/RPi5 w/ Bookwork 64bit?

I just updated node-red-node-pi-neopixel from v2.0.0 to v2.0.2 and while it wasn't yet working with v.2.0.0 now it is broke altogether and won't even allow the flow to run with v2.0.2?

Screenshot 2025-06-27 at 11.27.56 AM
Screenshot 2025-06-27 at 11.27.56 AM560×144 8.85 KB

Any ideas?

4

I don't know about that particular node, but to investigate the problem go into your .node-red folder (assuming a conventional install) and run

npm remove node-red-node-pi-neopixel
npm install node-red-node-pi-neopixel

If that shows errors then post the log here (text copy/paste please, not screenshot). If it doesn't show errors then restart node-red.

5

On second thoughts don't bother. If you look in the node-red startup log you may see
[warn] [node-red-node-pi-neopixel/rpi-neopixels] SyntaxError: Unexpected token ')' (line:13)
which indicates a problem with the node.

One of the developers may see this, if not then submit an issue on the node's github page.

For the moment you can revert to the previous version by running
npm install node-red-node-pi-neopixel@2.0.0
or 2.0.1 to try the intermediate release

6

Apologies - extraneous ) now removed . v2.0.3

1 Like
7

Thanks @dceejay.

8

@Colin Thanks, I had already reverted to v2.0.1 after running into the issue but it's already been fixed with a v2.0.3 release :slight_smile:

1 Like
9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.