Announcement: Big bug and PR cleanup as well as helping out the project

For those who don’t know me, I’m not the developer, Henner is a friend and former coworker of mine, so I’m just a user and helping out.
I went through all the Pull Requests and tried to approve the ones that looked safe and still relevant. I asked for updates on some, and closed the rest. Apologies if yours got closed, but you can update and re-open if your need is still relevant today (some were over 5 years old:).

For bugs, there were over 600 bugs open, many should never have been bugs to start with but then again many were open before discourse existed. I have looked at all the titles, rescued a few from bug bankruptcy and closed the rest. Apologies if you had a real bug in there, you can update and re-open it, it’s not that I hated you :wink: it was just a mass cleanup.

Since all this took over 10h across 2 days, I have modified the new bug template to strongly encourage reading and doing homework before you post.

Most of the text is also relevant for asking for help here. Everyone who posts ‘it doesn’t work, help me”, is not being mindful that this is useless for getting help. I’ll paste the text here, hope it’s useful. This also means that we have very little help for working on the actual code. If you have expertise and time, please help us, thank you :wink:

Note that if you are not a developer who can work on the library code but you can help new users here, this is also useful and appreciated, thank you.


Before filing an issue, please keep in mind that developer time is extremely limited.
We are happy that you are excited to use this project :slight_smile: but we do not have the time or
resources to help users with their programming or debugging questions.
Please read all of this before you delete it and type your bug if it is still appropriate.
For reference over 90% of the issues that were mass closed in 2025/11 did not qualify as bugs,
please help us help you by leaving more time for development.

If you have a problem, make sure that

  1. you read the entire top level README
  2. look at all the sub-pages: GitHub - hzeller/rpi-rgb-led-matrix: Controlling up to three chains of 64x64, 32x32, 16x32 or similar RGB LED displays using Raspberry Pi GPIO
  3. if you are using example code, you should be able to read and understand that code

If you need further help, you can ask on discourse:
https://rpi-rgb-led-matrix.discourse.group/
Please understand again that no one is getting paid to help you. Help us help you:

  • say what you have
  • say what you tried
  • if your panel isn’t working, you need to read the markings on the chips
  • search discourse and the bug tracker for your chip type if it’s a chip issue or your issue type
    (“half my lines are black”).
  • generally please treat people’s time as more valuable than yours, do as much as you can. There are
    many of you and only one of them :slight_smile:

For panel support issues, you want to refer to rpi-rgb-led-matrix/README.md at master · hzeller/rpi-rgb-led-matrix · GitHub .
The bugs working on chip support are for development, not “I bought this panel and I want you to make it work”
(it is on you to research which panels are supported before you buy).
If you have a commercial application where you need support for a new panel and are
willing to pay consulting rates for that work, then it is ok to state so in the panel
support bug and someone may be able to work something out with you, but again be mindful
this is not a commercial or paid project.

It is of course always ok to suggest a new feature that is different from supporting new
panels.

A few master bugs that may help:

For language bindings, note that the main developers are not using them, so they will lag.
Your patience is appreciated, and help is welcome :slight_smile:


1 Like

Great job. Thanks for keeping the project going.

Marc, I will be happy to help with issues that I understand.

You are our recent superstar. Your help across this project and other RGBPanel support code (like the ESP32DMA one) is very much appreciated.
Thank you!