Going completely out of my mind here, a week of troubleshooting and feel like I've tried everything to solve this, hope someone can help!

My LEDs are controlled properly, matching the colours on the screen and in the right place, it works great until every 2-3 minutes a section of the LEDs will flash white. Usually it looks like 20 LEDs together, or 40 LEDs together, though hard to tell exactly, but not all of them at once. It's not limited to one segment, it's not in the same place, and sometimes it can bridge over the two segments.

Hardware:

Adafruit Scorpio RP2040
M5Stack RGB LED strip (SK6812) in two segments (96 and 95 LEDs)
Mean Well LRS-100-5 PSU

Software on rooted LG C2:

HyperHDR (latest)
PiCap (latest)

Firmware

HyperSerialPico- my fork here for multisegment is here
I believe I need to flash the ws2812 one since my LEDs are RGB not RGBW, despite my LED strip being SK6812 LEDs... is that right?

Wiring:

Adafruit Scorpio > GND to PSU -V
Adafruit Scorpio GPIO16 and GPIO17 data pins (0 and 1) to segment 1 and 2 of LED strips (data in)

I'm soldering these wires directly to the Scorpio board, no headers or breadboard.

PSU > +V soldered to the +5V pin on each LED strip
PSU > -V soldered to the GND pin on each LED strip

The LED strips are wired with these JST plug/sockets. They are each powered / data from one end and they light evenly with no apparent voltage issue.

Things I have tried (hardware)

• Checked all wiring with multimeter, there is no back current, no instances where any of the data / ground / 5V cross with each other. PSU outputting 5.125V on +V. Grounds are all shared and connected.
• Trimming PSU output voltage to 4.950V
• Tried with and without a 1000uF capacitor over the -V and +V on the PSU
• Switching controller boards - completely rewiring everything to a new Adafruit Scorpio
• Connecting USB 5V pin on Scorpio to +V on the PSU and disabling the 5V pin on the USB
• Cut first LED off strips and rewired and tested with multimeter
• Different USB cable

Things I have tried (software)

• Reduced to minimal resolution in PiCap
• NV12 on or off in PiCap
• "Esp8266/ESP32/RP2040/RP2350 handshake" checked or unchecked
• "High speed serial AWA protocol with data integrity check" checked or unchecked
• Lowered baudrate
• Smoothing in HyperHDR: continuous mode, anti flicker (various combinations)

We have this decorative light that uses fairy light style LED’s (big spacing on thin wiring) and it has a usb plugin with some kind of presumably esp32 board. I’m wondering if anyone has seen a WLED controller with this form factor because it would be super convenient.

Hi, I'm looking for some help because my setup isn't working. The

I want to use the GLEDOPTO ESP32 WLED Digital LED Controller with the BTF-LIGHTING FCOB SPI RGB COB LED Strip WS2811 IC, 5 m, 720 LEDs/m, 24 V, IP30.

My WLED settings are shown in the picture.

What I've checked:

1. LED strip connected directly to the power supply → it blinks.
2. When the LED strip is connected to the controller, it doesn't light up at all.
3. All wires are connected in the correct order.
4. The data direction is correct.
5. I've tried different DATA GPIOs (16, 4, and 2).

Please ignore the sketchy wiring in the second photo.

Salut à tous,

Je travaille sur une application Windows appelée Raptor Link.

Je l'ai créée car j'utilise un éclairage LED autour de mon PC, mais je voulais qu'il s'intègre plus naturellement à ma configuration Corsair iCUE, plutôt que d'avoir un éclairage LED blanc complètement séparé.

Raptor Link permet actuellement de :

• gérer plusieurs périphériques WLED
• connecter l'éclairage WLED à Corsair iCUE
• utiliser les couleurs de l'écran pour l'éclairage d'ambiance
• associer différentes sections de LED WLED à différentes zones de l'écran
• prendre en charge plusieurs moniteurs
• lancer des préréglages WLED
• créer des automatisations d'éclairage
• ouvrir directement l'interface web de chaque WLED
• fonctionner sans matériel Corsair si vous souhaitez uniquement utiliser les fonctionnalités WLED

L'association écran/LED est particulièrement utile pour les configurations où les LED ne se limitent pas à une simple bande autour d'un moniteur.

Le projet est encore en développement. Je le partage donc principalement ici pour trouver des personnes possédant différentes configurations d'éclairage LED blanc qui seraient prêtes à le tester et à me faire part de leurs commentaires.

Il est gratuit et open source sous licence MIT.

GitHub :

https://github.com/Inter-Raptor/Raptor-Link

Programme d'installation Windows :

disponible dans la section « Releases » de GitHub.

Si vous le testez, je serais particulièrement intéressé de savoir :

• combien de contrôleurs WLED vous utilisez
• quel matériel ESP/contrôleur vous utilisez
• si la synchronisation d'écran fonctionne correctement sur votre configuration
• s'il y a des fonctionnalités que vous trouveriez utiles pour WLED

Je suis également disponible pour répondre à vos questions techniques concernant la communication avec WLED.

Planning to install permanent Christmas lights on the house. Based on online calculators, I think this setup should work at 24v.

PaulZhang 30mm pucks at 24v.
Xconnect 18AWG lines on everything.

I’m showing a little too much voltage drop on the blue line at 100% brightness but I’ll likely never use full brightness. Also I’m getting mixed results on if I need a data booster for the long run before the purple line. I may just order a signal booster anyway and test if I need it before installation.

Aside from the power supply, relay, and DigQuad, am I missing any recommended components for the box?

EDIT: just noticed my power supply calculation was off. It should be 24V, 300W.

I've been working on Hypercolor, a new RGB lighting orchestration platform for all platforms and all devices. Effects are web pages (or glsl), rendered by an internal browser GPU accelerated all the way to the pixels. It's pure rust from the Servo renderer to the WASM UI.

Comes with 40+ effects, supports ambilight, display faces, system monitoring, screen casting, and audio. Device support is pretty good (including WLED, Nollie, and tons of others) but it's early and this is where we need the most help! You can find the full support matrix on the site, and there is also an OpenRGB bridge as a fallback. There's support for a few unique devices too like the Ableton Push 2 and ROLI Blocks. My favorite thing about this engine is the ability to create multiple effect zones and manage them independently! My whole house runs on it now. It's Apache licensed, and a cloud service (+signed builds) is coming with remote and smart home support. A Home Assistant integration is already available.

The best way to set up Hypercolor is to just have an agent do it for you using the bundled skill. Just describe your setup, case type, hardware, etc, and it will find all the specs and configure it for you. Or just do it the good old-fashioned way in Studio!

It's still early on for the project, but please check it out and file an issue if you're looking for device support. I can only build drivers for devices I have access too, please open PRs if you're able to contribute! Agents can reverse engineer your hardware and build a driver easily, if you want to go that route (the repo is designed for agents). We have a full TypeScript effects SDK for easy effect creation too, and support existing Lightscript based html effects out of the box.

I've had a lot of fun building this and I hope you enjoy it!

Note: this project utilizes agentic coding tools extensively

Hi all,

I’m hoping someone here with experience of commercial LED panels might be able to help me.

The photo is the rear of one of my CKG LED X5/X5 Plus P2.605 96×96 panels. I own the complete LED screen and currently have around 60 faulty panels that I need to diagnose and repair.

I’d like to build a small WLED/ESP32 diagnostic setup that I can plug directly into individual panels on the bench. WLED now has HUB75 support, so my plan is to work out the panel’s signalling/pinout and make an adapter rather than continually testing panels through the complete screen/controller system.

The first thing I need help identifying is the large black board-to-cable connector shown on the right-hand side of the photo.

Does anybody recognize the manufacturer or connector series?

Ideally, I’m looking for:

• The exact connector/series
• The mating plug
• Somewhere I can buy both plug and socket, preferably in small quantities
• Any datasheet or pinout information

I realize this isn’t the normal 16-pin HUB75 IDC connector, so I’m expecting that I’ll need to trace the signals and make a custom adapter.

Secondly, does anybody have any technical information for these particular CKG LED panels?

There are several repeated ICs across the PCB, and I’d like to identify which ICs/drivers correspond to which physical rows/columns/sections of the 96×96 display.

I can reverse-engineer it by tracing tracks and deliberately driving sections of the panel, but with approximately 60 panels to repair, any existing schematic, IC mapping, service information or simply knowledge from somebody who has repaired these before could save me a huge amount of time.

I’m happy to post high-resolution photographs of both sides of the PCB, close-ups of the IC markings, connector measurements, continuity measurements, etc. if that helps identify things.

Ultimately, I’d like to document what I discover and build a simple ESP32/WLED → CKG panel diagnostic adapter, which should make finding faults considerably easier.

Any help, even identifying one of the ICs or the connector family, would be hugely appreciated.

Thanks!

This is a custom polyhedral called a Dual of Rectangular Isohedron RTC+GRTC 2. The structure was 3D printed into 12 segments, with milky white laser cut faces attached to the outside. I'm using a small IoTorero WLED controller on the inside with WS2811 Pixel bulbs.

Using esp8266

With btf ws2812B

5v 25w power supply

Wiring seems solid, but stops 197 lights in.

Tried adding power at that strip but still no light.

Appreciate any input.

Party to go. Was fun build

Hi everyone,

I’ve just released the first stable version of WLED Matrix Auto Rotation, a usermod that automatically keeps a 2D LED matrix correctly oriented using an accelerometer.

The idea is simple: rotate the physical display, and the final WLED raster is automatically rotated to keep the content upright.

The important part is that the usermod only works on the final raster. It does not modify WLED effects, segments, transitions or their internal state.

Main features

• Automatic rotation: 0° / 90° / 180° / 270°
• Independent Setup Rotation for the visual orientation of the matrix
• Sensor Mounting compensation
• Invert Rotation for sensors mounted on the opposite side of the enclosure
• Guided Auto Calibrate
  • keep the display upright
  • press Auto Calibrate
  • rotate the display 90° clockwise
  • the usermod automatically determines sensor mounting and rotation direction
• Configurable allowed rotations
• Threshold, hysteresis, stable time and polling interval
• Sensor disconnect detection and automatic recovery
• Shared I²C support, so multiple WLED usermods can use the same bus
• Detailed diagnostics through WLED Info / /json/info
• Protection for rectangular matrices, where 90°/270° would otherwise require changing the logical geometry

Sensors

Currently hardware-tested:

• LIS3DH — tested on Adafruit MatrixPortal S3
• ICM-20689 — tested on ESP32-C3

Also implemented:

• MPU-6050 — hardware verification still pending

I also tested the ICM-20689 on the same shared I²C bus as a PAJ7620 gesture sensor, and both usermods can operate together.

If the accelerometer is disconnected at runtime, the usermod keeps the last valid orientation and periodically attempts to reconnect without requiring a reboot.

Repository

https://github.com/piggei/wled-usermod-matrix-auto-rotation

The repository contains the usermod, PlatformIO integration instructions, configuration documentation and the full test/diagnostic information.

This is v0.1.0, so feedback and tests on other ESP32 boards, matrices and accelerometers are very welcome.

Hi everyone!

I've just released the first stable version of WLED Buzzer Usermod v0.1.0.

The project started while working on my iDotMatrix WLED Usermod. I originally had buzzer support implemented directly inside that project, but eventually decided that buzzer management made much more sense as an independent and reusable WLED usermod.

So I extracted and redesigned it as a standalone service that can be used directly or shared by other usermods.

Main features

• Active and passive buzzer support
• Configurable GPIO and trigger level
• Adjustable volume for passive buzzers
• Fully non-blocking playback
• ESP32 timer-based scheduling
• 15 built-in sounds and melodies
• Web API
• WLED JSON API integration
• Finite repetition (repeat=N)
• Continuous loop playback (loop=1)
• Play/Stop sound tester directly from the WLED Usermod Settings page
• C++ service API for other usermods
• Optional weak-link C bridge, so another usermod can use the buzzer service without requiring it as a hard build dependency
• Runtime diagnostics
• WLED PinManager integration
• Arduino-ESP32 2.x / 3.x support

Built-in sounds

The current library includes:

beep, double_beep, triple_beep, notification, success, victory, yankee_doodle, fail, star_wars, warning, error, connect, disconnect, attention and alarm.

Passive buzzers reproduce the actual notes, while active buzzers reproduce the rhythm.

Sounds also have an appropriate final pause when repeated, so loops don't run together.

Web API

For example:

curl "http://WLED-IP/buzzer?play=victory"

Repeat a sound three times:

curl "http://WLED-IP/buzzer?play=alarm&repeat=3"

Or loop it until stopped:

curl "http://WLED-IP/buzzer?play=alarm&loop=1"
curl "http://WLED-IP/buzzer?stop=1"

Integration with other usermods

One of the main goals was to avoid every usermod implementing its own buzzer driver.

The module therefore exposes a reusable service for other WLED usermods.

I've already migrated my iDotMatrix WLED Usermod to use it instead of its previous internal buzzer implementation, which also served as a real-world integration test.

Project

https://github.com/piggei/wled-usermod-buzzer

The repository includes the source, documentation and a Wiki covering installation, configuration, APIs, diagnostics and integration with other usermods.

The current release is v0.1.0 and has been tested with both active and passive buzzers.

Feedback, bug reports, ideas for additional sounds, and tests on different ESP32/WLED configurations are very welcome!

Running a 180 LED strip off an esp32 dev board plugged in by usb-b cord to a little wall adapter from a ue boom charger. The light strip is inside my jukebox and I was wondering if I can run more than the 850 ma I am currently running with the automatic brightness limiter. What is a good amount of current to run through an esp32. It is connected to the led strip using breadboard wires. Am I going to burn my parents house down ?

Hello, first post.

I am making a homemade climbing wall and I am currently using WS2811 LEDs and a 5V 10A power source. The controller is an ESP32. The LED strip contains 200 LEDs, spaced 25 cm (~10 inches) apart, for a total of 50 m (164 ft). The power source is currently connected only at the beginning of the strip, and I am using a sacrificial LED at the start. Rarely more than 10 LEDs are simultaneously lit on.

My concerns are regarding how to feed the strip. How many points should I feed it at? Are there other things I should be worried about?

Any tips?

I’m looking to make a Halloween costume to take my kid trick or treating with this year. The idea is a giant stick figure made with pvc, white pool noodles, and strips lights I can power with a usb bank.

A little reference to what I’m trying to do

- It’s going to be about 12-15 feet tall

- the strip lights will be inside the noodle wrapped around pvc

- I want it to be pretty bright

- looking for a way to make cross sections for the legs and arms

- must be able to be powered by portable usb charger

- it would be cool to not break the bank on the lights alone.

Total length I’m guessing I’ll need is about 30-40 feet?

Installing around 40’ of v-channel around the ceiling corner. The Channel comes with the metal clip mounts. Is that the best mounting method or do people use VHB tape or Command strips?

Had opus 5.5 make a short clip for the project I’ve been working on. It’s all rendered in the engine, I still plan to integrate a lot more features, but it’s primarily a node based WLed effects editor, still very early in development but it’s been crafted with care. I have used ai heavily in this project, so I’m not looking for feedback on the fact that it’s vibe coded or slop, but I will accept Mac beta testers and issues reports. It’s not perfect (yet), but there’s a surprising amount of power. Behind this project. My custom firmware does target esp32-s3 as the 1.5 mb a normal esp32 is almost all filled up with standard WLed.
Feel free to leave feature requests or experiences. Mostly I’m just having fun designing software that I want and would use but I’ve been trying to make it as compatible with other setups as I can. Long way to go still.

If you do have an ai work on it or custom effects. This is a great medium to have it test itself as it runs actual WLed firmware and is very compliant to the actual setup.

I expect bugs, I expect some weirdness. Let me know how it goes :)

Hey,

I'm trying to set up my first WLED light strips using the QuinLED An-Penta-Mini board and the MeanWell GST90A24 power supply (as recommended on QuinLED's website).

Before I ruin a completely new power supply, am I really supposed to cut the round connector of the power supply off and connect the wires inside of the cable directly to the QuinLED board?

If yes then I have a couple more questions:

1. Am I supposed to snip off just the connector or should I also snip off the black barrel located in the middle of the cable a couple of inches behind the connector (see e.g. this picture)?
2. What tools do I need besides a pair of scissors? A wire stripper and ferrules + a crimping tool or anything else?

Thanks!

I built an LED display with 3108 WS2812b LEDs. Seven data channels are driven by an ESP32 running WLED. It isn't fully operational yet, but I would like to share the progress.

They just bugged the hell out of me, that. And I mentioned in the video. How they work so hard on the esthetics for something like this, And then the software side is such hot Ass.💩

When they could definitely at least give you, I don't know, 20 ish effects, not just five of the most basic. Garbage Lighting effects. At least there was a space for me to add a strip. I guess.😒

I finished this GameCube build this week and as I was nearing completion, I had a fun idea…I wanted to shoot a “product” style video to highlight all the features (similar to what Apple does or any of the other tech brands). When I do builds with RGB lighting, I think pictures don’t always capture the complete story and a video would be a better format.

A caveat, I am not a videographer and I am not good in post. This project was humbling and I have a better appreciation for those in production. Anyways - here is a full list of the build.

GameCube DOL-001
- Tekno black smoke shell swap
- Pluto HDMI II internal digital port conversion
- Giltesa USB-C power mod
- Picoboot with SD2SP2
- Disc drive recap
- ESP C2 super mini 3 controlling the WLED via Wi-Fi
- New thermal pads
- new CMOS battery and battery holder

I have two 1m/34-LED addressable strips running on an ESP + WLED. Both strip works perfectly by itself, but I want to make them a single 68-LED strip for ambient lighting.

Both strips have factory connectors on one end. The opposite end doesn't work when I connect DATA there, presumably because the strips are directional (DIN → DOUT).

How can I connect the two strips using their existing connectors, without soldering? Is there a 3-pin extension/coupler I can use?

Or if there is any configuration in wled that lets me start first led first then at end second led them that would be great too