Get xLights talking to the box that drives your pixels, tell it which prop is plugged into which port, and light every prop to test it. No networking experience needed.
Part of the beginner series: 1. Build Your Display · 2. Connect Your Controller · 3. Load Your Sequence
Menu and button names come from xLights 2026 and can shift a little between versions. Every controller brand has its own web page for settings; this guide tells you what to look for, and your controller's manual shows exactly where. Pictures are simplified drawings.
Your layout says what lights you have. This guide tells xLights how to reach them: through which controller, and which socket on it.
Your props are drawn on the Layout tab with the right pixel counts. If not, start with Build Your Display in xLights.
An Ethernet (network) controller, such as a Falcon, Kulp, HinksPix or FPP-based board, with its manual handy.
The controller plugs into your home router (or a network switch) with a cable, the same network your computer is on.
The controller's power supply is wired correctly and fused as its manual describes. If you're unsure about mains wiring, ask a qualified person.
| Word | What it means, in plain English |
|---|---|
| Controller | The box that receives the show over your network and sends it down the wires to your pixels. |
| Port | One pixel socket on the controller. Each port drives one string of pixels, which can run through one prop or several props wired one after another. |
| IP address | The controller's "house number" on your network, like 192.168.1.50. xLights uses it to find the controller. |
| Protocol | The "language" xLights and the controller speak over the network. The common ones are DDP and E1.31 (also called sACN). |
| Channel | One brightness value. A colour pixel uses 3 channels: red, green and blue. |
| Universe | A bundle of channels (usually 510, so 170 pixels) used by E1.31. With Auto Size on, xLights works these out for you. |
| Smart receiver | A small add-on box that extends one port out to several more, out where your props are. Optional. |
| Upload | xLights writing the port setup (which props, how many pixels) straight into the controller, so you don't have to type it on the controller's web page. |
| FPP | Falcon Player: a small computer (often a Raspberry Pi) that plays your show on its own, so your PC doesn't have to stay on all season. |
Show data travels from xLights, over your home network, to the controller, and out of each port to the props wired to it.
Your router hands out addresses automatically, and they can change after a power cut. A show needs the controller at the same address every night.
| Name | Main Controller — any name you'll recognise |
| IP Address | The fixed address from Step 2, e.g. 192.168.1.50 |
| Vendor, Model, Variant | Your controller's make and model. This tells xLights how many ports it has and lets it upload the setup |
| Protocol | DDP or E1.31: use what your controller's manual recommends |
| Active | Active so xLights sends it the show |
| Auto Layout, Auto Size | Tick both. xLights then works out channels and universes for you |
Now tell xLights which props are wired to which port. The Controller Visualiser lets you do it by dragging.
| Wrong colours | Red shows as green? Change the prop's Color Order (e.g. RGB → GRB) in its Controller Connection |
| Too bright | Lower the prop's Brightness in its Controller Connection. Easier on the eyes and the power supply |
| What you see | Why, and what to do |
|---|---|
| Discover finds nothing | The controller and computer aren't on the same network, or the controller is off. Check the cable and the first three numbers of both addresses (Step 2), or add it by hand. |
| Nothing lights in the Test | Check Output to Lights is on, the controller is Active, its IP address is right, and you uploaded (Step 5). |
| Only part of a prop lights | The pixel count in xLights doesn't match the real string, or the prop is on the wrong port. Fix it and Upload Output again. |
| The second prop on a port lights wrongly | The props on that port are in the wrong order, or the first prop's pixel count is off by a few. Re-order them in Visualise. |
| Colours are mixed up | Set the right Color Order for that prop (Step 6). |
| Lights flicker or show random colours | Often a loose data connection or a very long cable run to the first pixel. Power off and check the plugs; the controller's manual lists maximum distances. |
| xLights says the controller is "unmanaged" | Two controllers in your list share the same IP address. Give each its own address. |
Load a sequence. Follow How to Load Your Sequence in xLights to put a purchased show on your layout, or browse the sequences.
Play it all season. An FPP player can run the show on its own. xLights' Tools → FPP Connect sends your sequences to it.
Questions? Contact us. xLights is a separate, free program made by its own volunteer team and is not affiliated with this site. Follow your controller maker's instructions for wiring and power.