Start with the word, because nobody explains it. A pixel is one small LED node that you can control completely on its own. Each pixel has a tiny chip in it, so one node can be red while the node three inches away is white and the next one is off. A data wire runs down the line telling every node what to do. That is the whole idea, and it is what makes permanent lighting able to do anything more interesting than one flat color.
Pixels compared to a standard LED strand. A normal strand of LED lights is what people call dumb. The whole run is one color at a time, because every bulb is wired to do the same thing. You can have all warm white, or all red, and that is it. With pixels every node is independent, so the same run can do a pattern, a chase, two colors at once, or a slow fade. Standard strands are cheaper and completely fine if you only ever want one steady color.
Pixels compared to globe or C9 bulbs. Globe lights and C9 bulbs are a look. They are big decorative bulbs, usually a fixed warm white or a fixed color, and they hang in a visible strand because being seen is the point. Pixels are a system. They mount in a slim channel meant to disappear in daylight, and their value is that you can reprogram them. If you want the classic bulb look hanging over a patio, globes are the right answer. If you want the roofline to change with the season and vanish the rest of the time, that is pixels.
What a build actually needs. Outdoor rated addressable pixels, a controller, a power supply sized with headroom, mounting channel, and sealed connectors. For DIY the usual controller is an ESP32 running WLED, which is free software you run from your phone. Bigger sequenced displays sometimes step up to a dedicated pixel controller and xLights.
What DIY builds get wrong most. Power. A long run fed from one end goes dim at the far end and the colors shift, because voltage drops as it travels. The fix is power injection, which just means feeding power in at more than one point along the run. The other two are undersizing the power supply and skipping proper waterproofing, which on this coast is what kills a build in a season.
How you actually control a DIY build. This surprises people: WLED does not need an app. The ESP32 serves its own web page, so you open a browser on your phone while you are on your home WiFi and control it there, the same as visiting any website. The trade off is that it only answers on your home network. If you want to change the lights from the road you have to add a VPN back to your house or run it through a home automation setup. Do not just open the controller to the open internet, it has no password on it by default.
Why DIY wins if you run a home hub. If you already have Home Assistant or something like it, a WLED build is the easier thing to automate, not the harder one. Home Assistant discovers WLED on the network by itself, and WLED also speaks MQTT and has a simple web API. So you can drive the lights from anything the hub knows about, a gate sensor, a camera, sunset, and those automations run on the hub at the house whether you are home or not. Closed brand systems often only hand you Alexa or Google, which caps you at roughly on, off, and a color.
- A pixel is one individually controllable LED node, so each point can be its own color
- A standard strand is one color at a time for the whole run, and costs less
- Globe and C9 bulbs are a visible decorative look, not a programmable system
- An ESP32 running free WLED software is the common DIY controller
- Long runs need power injected at more than one point or the far end goes dim
- Waterproofing and connectors matter more on the coast than the brand of LED
- WLED needs no app, you control it from a browser on your home WiFi
- Local only by default, so remote control from away takes extra setup
- Home Assistant discovers WLED automatically, and MQTT plus a web API are built in
