WS2805 RGBCCT flickering at specific brightness/color combinations on ESP32 / WLED 16.0.1
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 52/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- cpp
- Área
- embedded-iot
Línea de trabajo
Start by reproducing the saved JSON state on the QuinLED Dig-Quad/ESP32 with WS2805 RGBCCT, GPIO 16, WLED 0.16.0.1, and the Solid effect. Compare the flickering state with the stable state after the Kelvin adjustment, then trace the WS2805 RGBCCT output path for brightness values 126–130. Done means the supplied state no longer causes unintended white-emitter flashes and nearby brightness/color combinations remain stable.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What happened?
I'm using 168 WS2805 RGB+CCT pixels with a QuinLED Dig-Quad running WLED 0.16.0.1.
I occasionally noticed very brief flashes from white LEDs that should not be illuminated. I was able to narrow this down to particular combinations of master brightness and color/CCT state.
The issue is especially reproducible with master brightness values 126–130 / 255. At brightness 128, a saved preset can reliably reproduce the flickering.
Known flickering state:
{
"bri":128,
"seg":[{
"id":0,
"bri":255,
"cct":127,
"col":[
[255,206,166,0],
[8,255,0,0],
[0,0,0,0]
],
"fx":0
}]
}
Making a very small adjustment to the Kelvin/temperature slider stops the visible flickering without changing master brightness.
Stable state after that adjustment:
{
"bri":128,
"seg":[{
"id":0,
"bri":255,
"cct":127,
"col":[
[255,214,177,0],
[8,255,0,0],
[0,0,0,0]
],
"fx":0
}]
}
Reloading the original saved preset causes the flickering to return.
Additional observations:
- Brightness 126–130 produces the issue most noticeably.
- Values immediately outside that range appeared stable during short tests.
- A very small Kelvin/temperature adjustment can eliminate the flicker.
- Sometimes the expected bad state doesn't immediately flicker, but changing to blue and then back to white causes it to return.
- The visible flashes appear to come from white emitters that should otherwise be off.
- This occurs directly from the WLED web interface, independent of Home Assistant/MQTT.
- Solid effect (fx:0) reproduces it.
- 168 WS2805 RGB+CCT pixels.
- GPIO 16.
- The problem appears related to the combination of brightness and color/CCT rather than brightness alone.
Possibly related to #5198, although that report is using ESP32-C3 while this setup uses a Dig-Quad/ESP32.
To Reproduce Bug
Hardware:
- QuinLED Dig-Quad / ESP32
- 168 WS2805 RGB+CCT pixels
- WLED 0.16.0.1
- WS2805 RGBCCT configured as the LED type
- Data GPIO 16
I can reproduce the flickering using the following steps:
- Set the effect to Solid.
- Set the master brightness to 128/255.
- Set the LEDs to a warm white color.
- With the following state, some of the white emitters that should not be illuminated will intermittently flash:
{
"bri": 128,
"seg": [{
"id": 0,
"bri": 255,
"cct": 127,
"col": [
[255, 206, 166, 0],
[8, 255, 0, 0],
[0, 0, 0, 0]
],
"fx": 0
}]
}
Expected Behavior
No flicker
Install Method
Binary from WLED.me
What version of WLED?
0.16.0.1
Which microcontroller/board are you seeing the problem on?
ESP32
Relevant log/trace output
Anything else?
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
- Lenguaje dominante
- C++
- Estrellas
- 18.8k
- Forks
- 4.4k
- Merge medio
- 2 d 1 h
- PR fusionados (30 d)
- 11
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de wled/WLED
-
Gravimeter: bars turn black at full volume (uint8_t(segmentSampleAvg*8) overflows)Posiblemente ocupada @DedeHai la tomó hace 15 días. Abiertobug confirmed
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
wled/WLED#5891 · 12 comentarios ·
Los mantenedores suelen responder en 1 día
-
bug cannot reproduce
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
wled/WLED#5840 · 12 comentarios ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
wled/WLED#5836 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
backburner enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
wled/WLED#4132 · 5 comentarios · 2 reacciones ·
Los mantenedores suelen responder en 1 día
-
discussion enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
wled/WLED#3478 · 13 comentarios ·
Los mantenedores suelen responder en 1 día
Issues similares
-
[mimalloc] update to 3.6.0Abiertocategory:port-update
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 2 días
-
MinGW build faillureAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
facebookresearch/faiss#5775 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
Eval bug: minimax-m3: build_moe_ffn() drops the per-expert NVFP4 scale → garbled output (M3.1 Flash)Abiertobug-unconfirmed
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
bug triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
secondlife/viewer#6507 ·
Los mantenedores suelen responder en 1 día
-
clang:frontend code-cleanup HLSL
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
llvm/llvm-project#235100 · 1 comentario ·
Los mantenedores suelen responder en 1 día