A strip that is stable at 100% but flickers at 20% is not necessarily defective. Low brightness is where dimming method, controller resolution, power supply behavior, and wiring noise all meet.
This is the order I use before replacing anything.
1. Find out what is actually doing the dimming
A PWM controller, a phase-cut wall dimmer, and an addressable controller creating dimming in software are three different systems. A lamp-rated wall dimmer feeding an ordinary LED strip supply can produce exactly this symptom, and no change to the strip will solve it.
For a low-voltage DC strip, I want a compatible constant-voltage supply and a PWM controller on the DC side. If there is a phase-cut dimmer on the AC side, every component has to be designed for that chain.
2. Check whether the flicker follows the output level
Set the controller to a fixed low level and watch for a minute. Then raise it slowly.
Regular pulsing at one brightness often points to PWM frequency or limited dimming resolution. Random flashes while the level changes can be a control or signal issue. A brief drop when another load switches on points me toward the supply and wiring instead.
A phone camera can help reveal pulsing, but I do not use it as the only test. Cameras add their own sampling artifacts.
3. Measure the DC bus at the strip
Measure at the strip terminals, not only at the supply. Compare full brightness and the problematic setting.
A loose terminal or undersized lead can sit unnoticed at low current and become unstable when the load changes. I also check that the supply is not operating below a required minimum load. Some supplies need a small stable load to regulate cleanly.
4. Separate PWM flicker from data flicker
With analog white or RGB strip, the controller switches the power rails. With WS2812 or similar pixels, the power rail stays on and the controller sends data. Those failures look similar from across the room but need different fixes.
For addressable pixels, I check the ground shared by the controller and pixels, the data resistor, and the first pixel before touching the rest of the run. For PWM strip, I check the controller's output frequency and whether it supports the frequency I need.
This comparison of PWM and pixel control is a useful reference when choosing the control method: https://suntechlite.com/pwm-vs-spi-led-lighting/
5. Bypass one component at a time
My fastest useful test is a short known-good strip on the same controller. Then the original strip on a known-good controller. One variable at a time.
If the short strip flickers too, the original run is probably innocent. If the problem stays with the original run, I inspect connectors, damaged sections, and the first powered joint.
I replace the strip only after those tests point to it. Most low-brightness flicker complaints I see are compatibility or control problems, not dead LEDs.
Top comments (0)