When pixels flicker or go dark, start with one simple test and change one thing at a time. Swapping the controller, extension, and strand together might make the lights work, but it will not tell you which part caused the trouble.
Here is the process we want you to use before buying replacements. Keep the exact pixel and controller instructions nearby, disconnect power before moving connections, and stop using equipment that is damaged, unusually hot, or repeatedly tripping protection.
Show us the pattern of the problem
Does it affect every output, one port, one prop, or everything after a certain node? Did it start after rain, a cable move, a settings change, or an increase in brightness? Write that down before changing anything.
Record a short video with a simple solid color. Include the controller model, port, configured count, cable length, and pixel product. A useful support message might say, “Standard EVO pixels on port 3 work on a short lead but flicker with the installed extension.” That gives us a repeatable condition to investigate.
Run one test source at a time
Stop other show players and test patterns. Use the controller's documented local test at an appropriate brightness. If the prop works there but fails from the sequencer, the next checks are the upstream data path and mapping.
A local pass is a helpful clue; it does not prove every load or cable arrangement works. FPP users should follow the Display Testing guide and turn testing off afterward so it does not interfere with normal playback.
Compare the settings with what is plugged in
Check pixel protocol, node count, physical output, receiver assignment, and the incoming channel range. A perfectly healthy prop can be dark because its data is going to another output. Our xLights addressing guide explains those settings.
If the controller supports output status or current monitoring, check it. FPP's Port Status page depends on supporting hardware; do not expect that information from every device.
Make a like-for-like comparison
With power off, inspect the connectors for loose fit, bent contacts, moisture, corrosion, damaged seals, or cable strain. Confirm input and output direction and the pinout. A connector that fits can still be wrong for that connection.
Use a known-good compatible short cable or strand, keeping the same output settings. If you are checking an EZ Label extension, compare it with the same required connector arrangement. If you are checking standard EVO pixels, keep the correct voltage and protocol for that product.
| What the test does | Where to look next |
|---|---|
| A short cable works; the original extension fails. | The extension, its connections, or the longer power/data path. |
| A known-good strand works on the same output. | The original strand or its immediate connections. |
| Both strands fail on one output. | That output's settings, protection, connection, or hardware. |
| The symptom follows the original strand. | The strand or its attached cable. |
These results narrow the search. They do not prove a particular component has failed.
Check power while the fault is happening
If the problem grows with brightness or appears toward the end of a run, check power delivery. Use the product's allowed voltage range and load requirements. There is no universal “below 10 volts” cutoff for all RGB pixels.
If you can safely access the low-voltage measurement points, follow the manufacturer's meter procedure and record the reading, location, and test pattern. Keep away from exposed mains terminals and get qualified help when the required access is unsafe for you.
The Adafruit power guide explains voltage drop. Use your own pixel specifications for limits; do not raise supply voltage beyond them or install a larger fuse to hide a problem.
Follow the data path to the first affected section
Inspect the last working and first nonworking areas. The first dark node is not automatically the failed component: a connection or upstream data problem can affect what follows, and pixel designs handle interruption differently.
For a long run or receiver system, check the supported wiring and modes. Choose a repeater, receiver, or power change only after identifying what it needs to fix. One accessory cannot solve every kind of flicker.
Contact us before cutting
Send Mattos support your order information, product and controller details, connector and jacket photos, and the test video. Tell us exactly which comparison changed the symptom. Get guidance before cutting or splicing a strand, then repeat the original test after the fix and save the working setup.
Keep learning
- Pixel Power Planning: Voltage Drop, Injection and Brightness
- xConnect vs M-Connect: Match Pixel Cables and Adapters
- Light Show Preflight Checklist: Test, Label and Back Up
Browse all Mattos education and support guides.
Reviewed October 29, 2026. Use the instructions for your exact hardware and installed software version.
