Most holiday light kits come with an app, a cloud account and a remote, and plenty of them reach Home Assistant only through the vendor’s cloud, if at all. A WLED controller talks to it directly. It is a small ESP32 board running open firmware that Home Assistant finds on your network by itself, and from then on every segment, preset and effect is an entity you can put in an automation. The best WLED controller for Home Assistant is the one that also survives a winter outside, which comes down to fusing, level shifting and how much current it can pass.
We picked four Amazon-sold WLED controllers, two outdoor-rated 12V light types and the power supply that feeds them, and wired the picks into one roofline plan with real current numbers. Nothing here was installed on our house, so every spec comes from the makers’ pages and datasheets, the WLED and Home Assistant docs, and live Amazon US listings. We confirmed all of it against WLED 16.0.1 and the current Home Assistant WLED integration in October 2026.
Match each part to its job
A WLED light show has three parts that you buy separately: the controller that runs the firmware, the addressable lights, and a power supply sized for the lights rather than for the controller. The table lists our pick for each job with the spec that decides it. Prices are Amazon bands from late October, and holiday pricing moves daily, so check the live price before you order.
| Job | Pick | Deciding spec | Price band |
|---|---|---|---|
| Whole roofline, best overall | GLEDOPTO GL-C-618WL | 4 outputs, Ethernet, level shifter, fuse | about $36 |
| One or two runs over Ethernet | GLEDOPTO GL-C-616WL | 2 outputs, Ethernet, 10A per output | about $28 |
| Cheapest start, indoors | GLEDOPTO GL-C-015WL-D | 2 outputs, Wi-Fi only, 800 pixels | about $25 |
| Pixels plus plain strips | BTF-LIGHTING SP805E | 2 pixel outputs, 5 PWM channels, ETL listed | about $27 |
| Roofline strip | BTF-LIGHTING WS2815 IP68 | 12V, backup data line, 300 LEDs per 5 m | about $56 |
| Windows, trees, fascia | ALITOVE WS2811 12V pixels | 50 IP68 bullets, xConnect plugs | about $31 |
| Power for all of it | Mean Well LRS-350-12 | 12V, 29A, 348W | about $27 |
Every controller in the table runs WLED on an ESP32, which matters more than it looks. The WLED project says ESP8266 support is coming to an end and points new builds at the ESP32, so we skipped every ESP8266 board, however cheap. The lights are all 12V for the same reason a roofline needs them: at the same wattage, 12V carries well under half the current that 5V does, and current is what drops voltage along a long run.
Wire power and data before you shop
Power and data reach the lights by different paths, and that split decides which controller you need. The controller sends data down each output and passes some current with it, but the supply feeds the far end of every long run directly through its own fuse, so most of the current never touches the controller. Home Assistant only ever talks to the controller, over your LAN.
We sized the picks against one plan: 20 m of roofline in four 5 m reels of WS2815, plus two strings of ALITOVE bullets around a window and a tree. BTF recommends a 12V 5A supply per 5 m reel of its IP68 WS2815, and ALITOVE rates its bullets at 0.5W each, so the numbers come out like this:
| Run | Pixels | Maker’s supply rating at 12V | Share of a 29A supply |
|---|---|---|---|
| 4 reels of WS2815 (20 m) | 1,200 | 20A, 240W | 69% |
| 2 ALITOVE strings | 100 | about 4.2A, 50W | 14% |
| Total | 1,300 | about 24.2A, 290W | 83% |
Full white is the worst case, and a holiday show rarely runs every pixel at full white, but the supply and the fuses must still survive it. The WS2815 figure is BTF’s supply recommendation rather than a measured draw, so meter one reel at full white before you trust it. We’d stop at this load on one LRS-350-12 and add a second supply for anything bigger. The table also shows why the controller choice matters: the GLEDOPTO boards pass 15A in total to their outputs, so 20A of roofline can’t all flow through them. Feed each reel from the supply at its far end, and fuse each feed.
WLED’s own wiring guide sets the rest of the rules, and they apply to every pick below:
- Fuse the positive lead close to the supply, rated just above the run’s expected draw.
- Once the supply is over 100W, give every injection line its own fuse as well.
- Inject power when a run passes about 150 LEDs or its far end looks dim or off-colour, with 22AWG wire or thicker.
- Join every ground: supply, controller and each light run.
- Level-shift the 3.3V data from the ESP32. The WLED docs call the shifter mandatory, especially on 12V and 24V lights.
Then set WLED’s brightness limiter to the current your supply can really deliver, so a stray full-white preset can’t overload it. Change the mA per LED too, because the default assumes 5V pixels. WLED has a built-in 12mA (WS2815) option, but we’d set a custom 17 mA, which matches BTF’s 5A per 300 LEDs and leaves the limiter on the cautious side. The full rules, with photos, are in the WLED wiring guide. Missing grounds and unshifted data cause most of the flicker people blame on bad strips.
Run a roofline from the GL-C-618WL
The GL-C-618WL (GLEDOPTO calls it the Elite 4D-EXMU) is the controller we’d mount in the weatherproof box for a full roofline. It has four data outputs, so our plan puts two 5 m reels on each of two pins (600 pixels each, inside the 800 per pin that the WLED multi-strip docs call very good) and leaves the other two pins for the bullet strings.
Protection is what earns it the top spot. It carries a TI level shifter, a pluggable 20A fuse with a spare 5A in the box, reverse polarity protection and a relay that cuts power to the lights when WLED turns them off. The relay means the lights are not left powered all night while the show is off. There’s one catch: power you inject from the supply at the far end of a reel bypasses the relay. Switch those feeds too, or accept the idle draw.
On the network side, the board has an Ethernet port as well as Wi-Fi, and it adds a PDM microphone for sound effects and Wago lever terminals for the wiring.
Watch two numbers on the label. It takes 5, 12 or 24V in, but the output limits are 10A per channel and 15A in total, so the 20A fuse protects the board, not your load budget. Two reels at full white reach the channel limit on their own, which is why the far-end injection matters. Keep the current that passes through the controller under 15A and inject the rest from the supply. It is also rated IP20, so it belongs in a sealed box under the eaves, never loose on the gutter.
Buy it if you light a whole house from one box, or plan to run xLights shows over Ethernet later. Skip it if you have one run, where the GL-C-616WL below does the same job for less. It sells for about $36 from GLEDOPTO’s own Amazon store, where it had 129 ratings averaging 4.3 when we checked, so check the GL-C-618WL’s live price.
Use the GL-C-616WL for one or two runs over Ethernet
GLEDOPTO’s GL-C-616WL is the same Elite family with two outputs instead of four. You get the same Ethernet port, level shifter, relay and 20A pluggable fuse, the same 15A total, and up to 10A on either output.
Two outputs cover more houses than you’d think: one for the front roofline and one for the bullets around the door is a common first season. Ethernet is the reason we’d pick it over a cheaper Wi-Fi board. A controller in a metal box on an outside wall often sits at the edge of the house Wi-Fi, and the WLED FAQ recommends wired Ethernet for large realtime shows anyway. Home Assistant does not care which link the controller uses, as long as it is on the same network.
According to the Amazon listing, the board ships with GLEDOPTO’s pre-configured custom firmware, which is WLED set up for its pins. Stock WLED has a Gledopto Ethernet profile in its settings, so you can flash the official ESP32_Ethernet build later if you prefer, since the plain ESP32 build has no Ethernet support. It is about $28, but it had only 49 ratings at 4.0 when we looked, fewer than the four-output board, so see the GL-C-616WL’s current price and reviews before you order. A house that will need a third run from the same box is better served by the GL-C-618WL.
Start cheap with the GL-C-015WL-D indoors
For learning WLED, the GL-C-015WL-D is the board we’d start with: an ESP32 with two outputs, a microphone, a UART port for flashing and a MOSFET relay. It takes 5 to 24V in, its label allows 10A per channel and 15A in total, and it is rated for 800 pixels.
What it leaves out is the reason it is not our roofline pick. Neither GLEDOPTO’s page nor the Amazon listing claims a fuse or a level shifter, and it has no Ethernet. On a short indoor run beside the controller that’s fine: a mantel garland, a stair rail or a tree a metre from the outlet. On a 12V roofline with a long data lead, you’d be adding the fuse and fighting the flicker yourself.
GLEDOPTO’s budget board is the most-reviewed one in this guide, with 168 ratings at 4.4 when we checked, sold by GLEDOPTO’s store under the Sogledwow brand name. At about $25 it is a cheap way to see whether you like WLED in Home Assistant before you wire the house, so look up the GL-C-015WL-D’s price. Skip it for anything mounted outside.
Mix pixels and plain strips on the SP805E
The SP805E is the pick when the holiday setup includes ordinary single-colour or white strips as well as pixels. Next to its two pixel outputs, which the Amazon listing rates at up to 2,048 pixels each, it has five PWM channels at 6A each for plain RGB, RGBW or tunable-white strips, so the warm-white under-cabinet strip and the chasing pixels share one controller and one Home Assistant device.
It’s the only controller here with an ETL safety listing (the Mean Well supply carries UL 62368-1). The limits are low for an outdoor build, though. The total is 12A, the DC barrel jack is labelled 4A, BTF rates it for indoor use from -10 to 40°C, it is Wi-Fi only, and neither BTF nor the listing claims a level shifter or a fuse. Feed it through the screw terminals rather than the jack once a strip draws more than 4A.
We’d use it indoors: a window display, a lit shelf, the tree. It had 36 ratings at 4.8 when we checked and sells for about $27, the same as on BTF’s own store, so confirm the SP805E’s price before you order. Skip it if every light you own is a pixel strip, since you’d be paying for PWM channels you never use.
Line the roof with WS2815 IP68 strip
For a continuous roofline we’d hang BTF’s IP68 WS2815: 12V, 300 individually addressable LEDs per 5 m reel, sealed in silicone. The WS2815 carries a backup data line, so one dead LED does not black out everything after it, which on a roofline is the difference between a ladder trip in December and a ladder trip in January.
Three details from BTF’s page change how you install it. The IP68 version has no adhesive tape, so it mounts with the screws and clips in the bag, which suits gutters and fascia board better than tape in the cold anyway. The colour order is GRB rather than RGB, so set it in WLED’s LED preferences or red and green swap. And BTF rates it from -20 to 40°C, which covers most winters but not the coldest ones.
A waterproof strip still needs waterproof joints. The Amazon listing says the connection points must be protected from direct water exposure, so seal every cut end and keep the 4-pin connectors out of standing water.
BTF’s page recommends a 12V 5A supply per reel while the listing says 3A, and we used the page’s figure for sizing. At about $56 a reel with 514 ratings averaging 4.7, shared across its variants, check the IP68 WS2815’s price. For visible points of light rather than a smooth line, pick the bullets below instead.
Outline windows with ALITOVE bullet pixels
Bullet pixels are the classic holiday look: separate points of light spaced along a cable, each with its own WS2811 chip and sized to fit a 12 mm hole. The ALITOVE string has 50 IP68 pixels at 8 in (20 cm) spacing over 10 m, which wraps a tree trunk or traces a window frame with gaps you can see from the street.
The xConnect plugs are why we chose this string. They’re the 3-pin waterproof connector most holiday-pixel gear uses, the string ships with a female pigtail to wire into the controller, and strings plug end to end without soldering. ALITOVE rates each pixel at 0.5W, which works out to 25W a string, although the same page also says 50W a string. Our power table uses 25W a string. At the page’s 50W figure, two strings would add about 8.3A and push one LRS-350-12 near its limit, so meter a string before you add a second batch.
Review history is the honest catch with this pick. On Amazon this exact listing had only 10 ratings averaging 2.9 when we checked, against 28 at 4.8 on ALITOVE’s own store, so treat it as the least proven pick in this guide and test each string on the bench before it goes up the ladder. It costs about $31, so check the ALITOVE string’s current price. Skip bullets for a roofline, where 50 points over 10 m reads as sparse next to a strip.
Power it from a Mean Well LRS-350-12
Cheap kits usually fail at the power supply first, and the Mean Well LRS-350-12 is the one we’d trust with a whole roofline. Mean Well’s datasheet rates it at 12V and 29A for 348W, with output adjustable from 10.2 to 13.8V, and protection against short circuits, overload, over voltage and over temperature.
Two things on the datasheet catch first-time buyers. The AC input range is set by a switch, 90 to 132V or 180 to 264V, so check it matches your mains before you plug it in. And it is an enclosed, fan-cooled unit with screw terminals and no IP rating, so outside it lives in a ventilated weatherproof box with the controller, never on the ground or in the rain.
Our 20 m roofline plan puts it at about 83% of its rating at full white, which is as far as we’d push one unit. For more lights, add a second supply rather than a bigger one, so each feeds its own runs and fuses. It is about $27 with 252 ratings averaging 4.7, so see the LRS-350-12’s live price. It’s the wrong unit for 5V lights, and a 5V roofline is the wrong plan anyway. This listing ships from a third-party seller, so check the serial number on Mean Well’s S/N lookup when it arrives.
Connect WLED to Home Assistant
The WLED integration is built into Home Assistant, uses local push, and finds controllers on its own through zeroconf. It needs WLED 0.14.0 or newer, and it gets state changes over a WebSocket, falling back to polling every 10 seconds on firmware that has no WebSocket. If you haven’t installed Home Assistant yet, our guides cover Home Assistant on Ubuntu 26.04 and Home Assistant in Docker.
Order matters here, because Home Assistant creates its entities from whatever the controller has when you add it:
- Join the controller to your network, over Wi-Fi or by plugging in Ethernet.
- Set the LED count, colour order (GRB for the BTF strip) and power limit in WLED’s LED preferences.
- Create the segments you want as separate lights, such as one per side of the roof.
- Accept the discovered WLED device in Home Assistant, or add it by IP.
Once the controller is added, each segment becomes a light entity, with a master light added when there are two or more. Presets, playlists and palettes become select entities, speed and intensity become numbers, and an update entity can install new stable WLED releases from Home Assistant. On a GLEDOPTO board, back up the WLED configuration first, because the update can swap the vendor’s pre-configured build for a different one. With the brightness limiter configured, you also get estimated current and max current sensors, and estimated current is the one we’d chart on a dashboard during the first cold night to check the supply’s headroom.
A few limits shape your automations. It sets only the primary colour, so two-colour and three-colour looks belong in WLED presets that Home Assistant calls by name. It ignores custom segment names and can’t control usermods such as the audio-reactive microphone.
In practice, you build the looks in WLED and use Home Assistant to choose which preset runs and when: on at sunset, a playlist on weekends, off at midnight. A small mini PC running Home Assistant handles that schedule easily, since the controller does all the pixel work.
Check these specs on any WLED controller
Amazon lists dozens of boards with WLED in the title, and the listings rarely say what’s missing. These are the checks we ran on every candidate, in the order that ruled most of them out:
- ESP32, not ESP8266, since WLED is winding down ESP8266 support.
- A level shifter on the data outputs, named on the maker’s page.
- A fuse on board, or room in your box for an inline one.
- A total output current above the share of your lights it will carry.
- Ethernet if the box sits at the edge of your Wi-Fi.
One more check is the official list. GLEDOPTO is not on WLED’s compatible controllers page, which names QuinLED, Athom and a handful of others. QuinLED’s Dig-Quad, which is on that list, has four outputs, five onboard fuses and optional Ethernet, but it sells through resellers listed on QuinLED’s shop page rather than on Amazon, and is worth the wait if you can order ahead of the season. Our QuinLED vs Gledopto vs Athom comparison puts the Dig-Quad next to those two brands board by board.
For the lights, the IP rating tells you where they can go. IP65 survives jets of water, IP67 survives brief immersion to 1 m, and IP68 survives longer immersion on terms the maker sets. A roofline needs IP65 at minimum, and IP67 or better wherever snowmelt pools. If your ESP32 projects go beyond lights, our ESP32 boards for ESPHome guide covers the sensor side of the same chip.
Connect WLED to more than Home Assistant
Home Assistant is the scheduler, but WLED speaks other protocols too, and a holiday show usually ends up using one of them. The controller does not care how many sources talk to it, though only one can drive the pixels at a time:
| Talks to | Protocol | Use it for | Watch out for |
|---|---|---|---|
| Home Assistant | WLED JSON API and WebSocket | Schedules, presets, dashboards | Primary colour only |
| xLights | DDP on UDP 4048 | Music-synced sequences | Ethernet for large shows |
| Other show software | E1.31 or Art-Net | Show software without DDP | 170 pixels per universe |
| Any MQTT broker | MQTT on 1883 | Node-RED and other tools | Unencrypted |
The E1.31 row is where people get stuck. Our 1,200-pixel roofline needs 1,200 ÷ 170 = 7.06, so eight universes, which fits under WLED’s limit of nine universes (1,530 pixels), but WLED recommends three or fewer for a smooth frame rate. That’s why the WLED FAQ recommends DDP with xLights. Finally, WLED has no HTTPS and no login, so keep every controller on your LAN and reach it from outside through a VPN to your Home Assistant, never through a port forward.
