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

**URL:** <https://discourse.nodered.org/t/issue-with-node-red-node-pi-neopixel-on-cm4-rpi4-with-debian-bookworm-64-bit/97607>\
**Category:** Hardware\
**Tags:** raspberry-pi\
**Created:** [13 June 2025 13:18 UTC](https://discourse.nodered.org/t/issue-with-node-red-node-pi-neopixel-on-cm4-rpi4-with-debian-bookworm-64-bit/97607 "2025-06-13T13:18:01Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Flo](https://avatars.discourse-cdn.com/v4/letter/f/b38774/32.png) [@Flo](https://discourse.nodered.org/u/Flo)\
**Post date:** [13 June 2025 13:18 UTC](https://discourse.nodered.org/t/issue-with-node-red-node-pi-neopixel-on-cm4-rpi4-with-debian-bookworm-64-bit/97607/1 "2025-06-13T13:18:01Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Flo](https://avatars.discourse-cdn.com/v4/letter/f/b38774/32.png) [@Flo](https://discourse.nodered.org/u/Flo)\
**Post date:** [16 June 2025 12:23 UTC](https://discourse.nodered.org/t/issue-with-node-red-node-pi-neopixel-on-cm4-rpi4-with-debian-bookworm-64-bit/97607/2 "2025-06-16T12:23:29Z")

</div>

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:

> <https://github.com/node-red/node-red-nodes/pull/1098>
>
> \## Types of changes
> 
> \- \[x\] Bugfix (non-breaking change which fixes an issue)
> …
> \- \[\] New feature (non-breaking change which adds functionality)
> 
> \## Proposed changes
> 
> My CM4 Module has in /proc/cpuinfo no " : BCM" text string
> Wich leads to a false, failing Hardware check, and the NeoPixel nodes are ignored.
> 
> Instead of the "BCM" chip, /proc/cpuinfo shows "Hardware : Raspberry Pi Compute Module 4 Rev 1.1".  
> 
> The Check was updated to use ": BCM" or ": Raspberry Pi" to check for Raspberry Pi Hardware.
> 
> 
> \## Checklist
> 
> \- \[x\] I have read the \[contribution guidelines\](https://github.com/node-red/node-red-nodes/blob/master/CONTRIBUTING.md)
> \- \[\] For non-bugfix PRs, I have discussed this change on the forum/slack team.
> \- \[\] I have run \`grunt\` to verify the unit tests pass
> \- \[\] I have added suitable unit tests to cover the new/changed functionality

---

<div class="post-metadata">

**Author:** ![dudleyjosh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dudleyjosh/32/105799_2.png) [@dudleyjosh](https://discourse.nodered.org/u/dudleyjosh)\
**Post date:** [27 June 2025 15:32 UTC](https://discourse.nodered.org/t/issue-with-node-red-node-pi-neopixel-on-cm4-rpi4-with-debian-bookworm-64-bit/97607/3 "2025-06-27T15:32:52Z")

</div>

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](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/3/83897b833aae2c9a1d059b3e44fe91fd6826db8b.png)

Any ideas?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [27 June 2025 16:11 UTC](https://discourse.nodered.org/t/issue-with-node-red-node-pi-neopixel-on-cm4-rpi4-with-debian-bookworm-64-bit/97607/4 "2025-06-27T16:11:04Z")

</div>

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

```auto
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.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [27 June 2025 16:24 UTC](https://discourse.nodered.org/t/issue-with-node-red-node-pi-neopixel-on-cm4-rpi4-with-debian-bookworm-64-bit/97607/5 "2025-06-27T16:24:25Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [27 June 2025 16:47 UTC](https://discourse.nodered.org/t/issue-with-node-red-node-pi-neopixel-on-cm4-rpi4-with-debian-bookworm-64-bit/97607/6 "2025-06-27T16:47:37Z")

</div>

Apologies - extraneous ) now removed . v2.0.3

---

<div class="post-metadata">

**Author:** ![dudleyjosh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dudleyjosh/32/105799_2.png) [@dudleyjosh](https://discourse.nodered.org/u/dudleyjosh)\
**Post date:** [27 June 2025 17:25 UTC](https://discourse.nodered.org/t/issue-with-node-red-node-pi-neopixel-on-cm4-rpi4-with-debian-bookworm-64-bit/97607/7 "2025-06-27T17:25:38Z")

</div>

Thanks @dceejay.

---

<div class="post-metadata">

**Author:** ![dudleyjosh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dudleyjosh/32/105799_2.png) [@dudleyjosh](https://discourse.nodered.org/u/dudleyjosh)\
**Post date:** [27 June 2025 17:27 UTC](https://discourse.nodered.org/t/issue-with-node-red-node-pi-neopixel-on-cm4-rpi4-with-debian-bookworm-64-bit/97607/8 "2025-06-27T17:27:58Z")

</div>

@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 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [11 July 2025 17:28 UTC](https://discourse.nodered.org/t/issue-with-node-red-node-pi-neopixel-on-cm4-rpi4-with-debian-bookworm-64-bit/97607/9 "2025-07-11T17:28:14Z")

</div>

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