Addressable LEDs work with WLED controllers by combining two separate systems: electrical power makes the lights operate, while a digital data signal tells each logical pixel what color, brightness, or effect to display. WLED runs on an ESP-based controller, calculates the appearance of every pixel, and repeatedly sends updated lighting data along the configured output line.
This is fundamentally different from a conventional non-addressable RGB light strip. In a traditional analog RGB strip, all LEDs connected to the same channel normally display the same color because the controller adjusts the shared red, green, and blue electrical channels. An addressable system adds control electronics within each LED or pixel module, allowing different positions on the same run to display different colors simultaneously.
That individual or group-level control makes effects such as these possible:
-
A color chase moving from one end of a roofline to the other
-
Red, white, and blue repeating across individual eave lights
-
A gradient moving from warm amber to cool blue
-
Different colors on the porch, garage, and gables
-
Symmetrical effects beginning at the center of a house
-
Music-responsive movement across selected zones
-
One static warm-white section beside an animated holiday section
The Lumary Permanent Outdoor Lights 3 uses an addressable lighting design with manufacturer-documented ESP32 WLED integration. Lumary also publishes 32-zone control, 16 million colors, adjustable 2200K–6500K white light, more than 150 preset scenes, 28 music-responsive modes, and support for Home Assistant.
To understand how the system works, separate it into five technical layers:
-
The power adapter converts household power to the voltage required by the lighting system.
-
Power wiring supplies electrical energy to the lights.
-
The ESP32 controller runs WLED and generates lighting instructions.
-
The data connection carries those instructions to the addressable lights.
-
Each pixel interprets its assigned data and produces the requested light output.
WLED’s official documentation distinguishes digital addressable LEDs from analog non-addressable LEDs. Addressable products can control individual pixels separately, while analog products require separate color channels and generally change all connected LEDs together. WLED supports numerous digital protocols, voltages, channel arrangements, and pixel types, but compatibility must be verified for the exact lighting hardware.
“WLED compatible” does not mean that any WLED controller can be connected to any LED string. The following characteristics must agree:
-
Operating voltage
-
Data protocol
-
Number of color and white channels
-
Color-channel order
-
Pixel grouping
-
Signal voltage and direction
-
Connector pinout
-
Maximum current
-
Power-supply capacity
-
Controller firmware configuration
-
Cable and extension architecture
The Lumary system’s published light-string input is 36V DC. That does not make it electrically interchangeable with the many 5V, 12V, or 24V WLED strips used in custom DIY projects. Use the Lumary controller, power supply, extensions, connectors, and instructions specified for Permanent Outdoor Lights 3 unless Lumary explicitly documents another compatible arrangement.
How the Data Travels Through Addressable LEDs
At its simplest, a digital addressable LED system has power, ground, and data connections. Some addressable protocols add a separate clock line, backup data line, or other conductors. The exact Lumary connector should be treated as a manufacturer-specific interface rather than rewired according to a generic three-wire diagram.
During operation, the controller creates a sequence of digital values representing the desired output of the pixels. Conceptually, the data can be imagined as a list:
| Logical Pixel | Requested Output |
|---|---|
| Pixel 0 | Warm white, 30% |
| Pixel 1 | Warm white, 30% |
| Pixel 2 | Amber, 40% |
| Pixel 3 | Red, 60% |
| Pixel 4 | Green, 60% |
| Pixel 5 | Blue, 50% |
The controller transmits this sequence rapidly. Each compatible pixel or pixel-control circuit extracts the data intended for its position and passes the remaining information downstream. Once the complete frame has been received, the pixels update their outputs. WLED repeats this process many times per second when an animation is running.
The visible motion is therefore not produced by color physically traveling through the wire. WLED calculates a series of still frames in which different pixels receive different values. Displaying those frames quickly creates the appearance of motion.
A chase effect might be represented conceptually as:
| Frame | Pixel 0 | Pixel 1 | Pixel 2 | Pixel 3 | Pixel 4 |
|---|---|---|---|---|---|
| 1 | On | Off | Off | Off | Off |
| 2 | Off | On | Off | Off | Off |
| 3 | Off | Off | On | Off | Off |
| 4 | Off | Off | Off | On | Off |
| 5 | Off | Off | Off | Off | On |
Actual WLED effects can use gradients, brightness transitions, palettes, speed parameters, and far more pixels, but the underlying principle remains the same: change the values assigned to each address over time.
Some products treat every physical LED as an independently addressable pixel. Others combine several physical LEDs into one logical address. For example, WLED’s compatibility documentation notes that certain 12V or 24V strips control groups of three or six physical LEDs as one logical pixel. Therefore, “individually addressable” should be interpreted according to the product’s actual pixel architecture rather than assumed from the number of visible LED chips.
For permanent outdoor puck lights, the visible light module is typically the practical pixel unit. The buyer should rely on the manufacturer’s documented zone and individual-control behavior rather than assuming that every internal LED channel is independently accessible.
Power and Data Perform Different Jobs
One of the most important WLED concepts is that data control and electrical power are related but separate.
The ESP32 calculates effects and transmits data. It does not generate the high-power electrical supply required by an extended lighting run. The power adapter and distribution system supply that energy.
This means that WLED cannot correct an undersized power supply, excessive voltage drop, an unsupported extension arrangement, or an overloaded connector. Software can reduce brightness or apply a current limit in supported configurations, but it cannot make physically incompatible hardware safe.
A useful conceptual model is:
| System Element | Primary Function |
|---|---|
| Household receptacle | Supplies AC power |
| Power adapter | Converts AC input to the required DC output |
| Controller | Runs WLED and generates data |
| Data line | Carries pixel instructions |
| Positive and negative conductors | Deliver electrical power |
| Addressable pixel | Interprets data and creates light |
| Power-injection point | Adds power at an approved point without redefining pixel addresses |
| WLED segment | Creates a software-defined zone within the logical pixel order |
Power injection does not create another copy of the lighting data. It supplies electrical energy at an additional point so distant lights receive adequate voltage and current. The data path can continue to define the logical pixel order independently.
WLED’s general DIY wiring guidance recommends considering power injection in larger installations because an LED strip or string can carry only a limited amount of current through its conductors. It also emphasizes correct wire sizing, fusing, voltage-drop planning, and strict separation of positive rails when multiple power supplies are involved.
Those general DIY recommendations should not be converted into permission to modify a packaged Lumary system. The Lumary WLED-compatible permanent lights publish their own expansion and power architecture: expansion up to 1,200 feet, additional power supplies every 300 feet, and 24.6-foot expansion segments sold separately. Follow the Lumary installation guide and use compatible accessories rather than applying a generic WLED wiring diagram.
Lumary also markets dual-output functionality. In a multi-output arrangement, one ESP32 controller can generate separate data streams for two physical branches while WLED represents those branches within a unified logical address space. The light count and starting index of each output must be configured correctly so effects appear in the intended order.
WLED’s official multi-strip documentation confirms that ESP32 controllers can operate multiple LED outputs. Each output can be assigned a light type, GPIO, length, color order, and starting index. WLED recommends ESP32 hardware for multi-output installations.
The product-specific controller interface and output mapping still take priority. Do not reassign GPIO pins, connectors, or output electrical characteristics unless that procedure is documented for the Lumary controller.
What WLED Does With Pixel Addresses
WLED assigns each logical pixel a numerical position beginning with zero. A 60-light system is conceptually addressed as pixels 0 through 59. A 180-light system is conceptually addressed as pixels 0 through 179, although the physical outputs may be divided across more than one branch.
WLED uses this logical order to calculate effects. If the order matches the physical roofline, a chase moving from pixel 0 upward will travel through the installation in the expected direction. If the physical and logical orders do not match, effects may:
-
Begin in the wrong location
-
Jump from one roof section to another
-
Reverse unexpectedly
-
Stop before reaching the final lights
-
Continue through an unintended branch
-
Appear asymmetrical on matching gables
The light count is therefore not a cosmetic setting. It tells WLED how many pixel addresses it should calculate and transmit.
For multiple outputs, WLED can assign cumulative indices automatically or use custom bus starting indices. An illustrative two-output configuration might look like this:
| Physical Output | Number of Lights | Logical Address Range |
|---|---|---|
| Output 1 | 30 | 0–29 |
| Output 2 | 30 | 30–59 |
If the second branch physically begins at the opposite side of the house, it may also need to be reversed or logically remapped so a center-out effect moves symmetrically.
The WLED settings documentation includes controls for output length, start index, color order, reversal, skipped pixels, per-output current limits, and automatic creation of a segment for each output. These settings are powerful, but an incorrect value can cause wrong colors, missing pixels, or unexpected effect direction.
Segments, Mapping, Presets, and Effects
WLED builds higher-level lighting behavior on top of the pixel address order.
Segments
A segment is a range of logical pixels treated as a zone. One segment could represent the porch, another the center gable, and another the garage.
Each segment can use its own:
-
On/off state
-
Brightness
-
Color
-
Palette
-
Effect
-
Effect speed
-
Effect intensity
-
Direction
-
Grouping
-
Spacing
-
Offset
The official WLED segment guide states that ESP32 systems normally support up to 32 segments, with higher counts possible on certain hardware configurations. It also explains how grouping, spacing, reversal, and offset modify the way effects move through a segment.
Lumary’s published 32-zone capability aligns naturally with this ESP32 segment model. A homeowner can divide the installation according to architectural sections rather than treating the complete roofline as one uniform strip.
Mapping
Mapping changes the relationship between physical wiring order and logical effect order. It is useful when the installation route does not follow the visual order that an effect should use.
For example, a cable might physically travel:
-
Left lower eave
-
Left gable
-
Garage
-
Center porch
-
Right gable
But the desired visual sequence might be:
-
Left lower eave
-
Left gable
-
Center porch
-
Right gable
-
Garage
A WLED map can tell the software to treat the pixels in the desired visual order without physically rewiring the entire installation. WLED supports JSON-based LED maps and can switch among multiple maps through presets.
Mapping is an advanced configuration feature. For a normal linear eave installation, correct physical planning and output mapping are usually simpler than creating a complex custom map after mounting.
Presets
A preset saves a complete lighting state. Depending on the save options, it can include:
-
Global brightness
-
Segment boundaries
-
Segment colors
-
Effects
-
Palettes
-
Effect speed and intensity
-
Mapping choice
-
Power state
-
API commands
WLED documents support for up to 250 preset IDs, although very large or frequently edited preset collections can affect controller responsiveness. A practical residential installation generally needs a smaller, organized set.
Useful permanent-light presets might include:
-
Everyday Warm White
-
Late Evening
-
Thanksgiving Amber
-
Halloween Purple and Green
-
Christmas Red and Gold
-
Independence Day
-
Sports Team
-
Party
-
All Off
JSON API
The WLED JSON API allows compatible software to read device information and control power, brightness, colors, segments, effects, palettes, presets, playlists, and even individual pixel values. The API can also report information such as the configured LED count, firmware version, frame rate, and estimated current when automatic brightness limiting is configured.
Home Assistant uses WLED’s integration capabilities to expose the controller and its segments as smart-home entities. This lets the lighting respond to schedules, household modes, sensors, calendars, or other automations while WLED continues to perform the pixel calculations.
Product Recommendation Analysis
The Lumary Permanent Outdoor Lights 3 system is relevant to buyers who want WLED-level pixel control without designing an entire outdoor lighting system from separate controllers, bare pixel strings, power supplies, connectors, enclosures, fuses, and mounting channels.
Lumary explicitly documents ESP32 WLED integration. ESP32 is a strong controller platform for addressable lighting because it supports multiple outputs, more pixels, and more segments than older ESP8266 configurations.
The system is available in four standard sizes:
-
100 feet with 60 lights
-
150 feet with 90 lights
-
200 feet with 120 lights
-
300 feet with 180 lights
The power ratings scale correspondingly from 48W to 144W. Each version uses a 36V DC light-string input, while the adapter accepts household AC power.
Lumary describes the color system as RGBAI plus adjustable white and also uses RGBICW terminology on the product page. The dedicated 2200K–6500K white range matters because addressability alone does not guarantee attractive everyday white illumination. The same system can display multicolor WLED effects during events and warm static white during ordinary evenings.
The 32-zone capability provides a practical balance between individual pixel control and whole-house usability. Most homeowners do not want to adjust 180 individual lights every evening. Zones and presets convert the underlying pixel addresses into meaningful architectural controls.
The system also includes more than 150 Lumary scenes, 28 music-responsive modes, and AI-assisted effect creation. These proprietary app features should not be assumed to correspond one-for-one with every WLED effect or Home Assistant entity. Lumary, WLED, and Home Assistant are related control environments, but each can expose different functions.
The product’s packaged power architecture is equally important. Lumary publishes a 300-foot interval for additional power supplies and a maximum expansion of 1,200 feet. WLED can calculate effects for a large logical installation, but physical power must still be distributed according to the manufacturer’s approved design.
Technical Specification Table
| Specification | Lumary Permanent Outdoor Lights 3 |
|---|---|
| Product type | Addressable permanent eave and roofline lighting |
| Controller platform | Manufacturer-documented ESP32 WLED integration |
| Models | PO3A1/PO3A2, PO3B1/PO3B2, PO3C1/PO3C2, PO3D1/PO3D2 |
| Housing colors | White / Black |
| Standard lengths | 100 ft / 150 ft / 200 ft / 300 ft |
| Number of addressable lights | 60 / 90 / 120 / 180 |
| Published system power | 48W / 72W / 96W / 144W |
| Light-string input | DC 36V; 1.33A / 2A / 2.66A / 4A |
| Adapter input | 120V AC, 50/60Hz |
| Color system | RGBAI plus adjustable white |
| Published color range | 16 million colors |
| Adjustable white | 2200K–6500K |
| Output per light | 60 lumens |
| Lumary zone control | Up to 32 zones |
| Preset scenes | More than 150 |
| Music modes | 28 |
| AI capability | AI Lighting Creator |
| Smart control | Lumary app, WLED, Home Assistant, Alexa, and Google Home |
| Physical control | Remote and control box |
| Current published ingress protection | IP67 for string lights, control box, and adapter |
| Current published operating range | -4°F to 113°F (-20°C to 45°C) |
| Mounting system | Patented low-profile slide-base |
| Expansion segment | 24.6 ft, sold separately |
| Maximum published expansion | Up to 1,200 ft |
| Power requirement for long runs | Additional power supplies required every 300 ft |
| Addressability benefit | Independent pixel or logical-zone colors, effects, gradients, and movement |
| Critical limitation | WLED compatibility does not override voltage, protocol, connector, power, or accessory requirements |
The values above reflect the current product listing and should be confirmed for the exact kit and accessories purchased.
How to Evaluate Addressable WLED Lighting Before Buying
| Key Purchasing Criterion | Common Sign of a Poor-Quality Unit | How This Lumary Permanent Outdoor Lights 3 Addresses It | Long-Term Usage / Performance Impact |
|---|---|---|---|
| Documented WLED compatibility | Seller uses “addressable” without identifying a supported control platform | Lists ESP32 WLED integration | Provides access to established effects, segments, presets, APIs, and automation |
| Defined pixel count | Product length is published but controllable light count is omitted | Lists 60, 90, 120, or 180 lights by kit | Allows accurate controller and effect planning |
| Multi-output capability | Branches cannot be mapped or configured predictably | Product page identifies dual-output functionality | Supports more flexible physical routing when configured according to the manual |
| Dedicated white output | White is created only by combining RGB channels | Provides adjustable 2200K–6500K white | Improves ordinary architectural use between holidays |
| Zone organization | User must control every pixel manually or run one whole-string effect | Publishes 32-zone control | Converts individual addresses into practical architectural sections |
| Power transparency | Voltage and wattage are omitted | Publishes 36V string input and 48W–144W system ratings | Reduces the risk of selecting incompatible power hardware |
| Long-run architecture | “Expandable” is advertised without power limits | Requires additional power supplies every 300 ft and publishes a 1,200-ft maximum | Makes large installations plan-driven rather than improvised |
| Local integration | Control depends entirely on one cloud app | Supports WLED and Home Assistant alongside the Lumary app | Enables local effects and broader smart-home automation |
| Preset support | Complex scenes must be rebuilt manually | Offers Lumary scenes and WLED preset capabilities | Allows repeatable everyday and holiday configurations |
| Outdoor installation design | Bare indoor strip and generic controller are adapted for exterior use | Provides outdoor-rated components and a low-profile mounting system | Reduces custom enclosure and mounting work |
| Accessory compatibility | Similar-looking connectors are presented as interchangeable | Product-specific extensions and power accessories are available | Protects the intended voltage, pinout, weather sealing, and power architecture |
| Manual fallback | Lights become unusable when Wi-Fi is interrupted | Includes remote and control-box operation | Maintains basic control during network interruptions |
Competitive Landscape
WLED addressable-lighting options can be divided into four broad categories.
Custom 5V addressable strips
Products such as WS2812B-style strips are common in DIY WLED projects. They offer dense individual-pixel control and extensive community support. Their low operating voltage can require substantial current and frequent power injection over long runs.
They are suitable for indoor accent lighting, short installations, and experienced builders. Creating a permanent exterior roofline system requires careful selection of weatherproof pixels, power supplies, enclosures, wiring, fusing, mounting channels, and signal-conditioning hardware.
Custom 12V or 24V addressable pixels
Higher-voltage addressable products can reduce current and voltage-drop challenges compared with equivalent 5V loads. Some control physical LEDs in groups rather than individually, and their protocol, color order, white-channel behavior, and backup-data features vary.
They remain engineering components rather than complete consumer installations. The builder is responsible for matching every electrical and mechanical element.
Proprietary app-controlled permanent lights
Many consumer permanent-light systems offer addressable effects, app scenes, music modes, and voice-assistant support. Their ease of installation can be attractive, but some use closed controllers that offer limited local automation or cannot be configured through WLED.
Buyers should verify whether “individual control” means true accessible pixel control, predefined zones, or only manufacturer-created effects. They should also confirm whether Home Assistant compatibility is native, cloud-dependent, or unofficial.
Packaged WLED-compatible systems
The Lumary addressable permanent outdoor lights occupy a hybrid category. They provide a coordinated consumer product—lights, mounting design, controller, adapter, app, and accessories—while documenting WLED and Home Assistant compatibility.
This approach can reduce hardware engineering work without eliminating advanced customization. The tradeoff is that owners must respect the packaged system’s voltage, connectors, power supplies, extensions, and firmware configuration rather than treating it as a generic open-hardware kit.
Professionally installed permanent-lighting systems
Professional systems may provide custom aluminum channels, concealed wiring, installer-designed power distribution, and service support. They can produce a highly integrated daytime appearance, especially on complex or tall houses.
Their controllers may be proprietary, and ownership cost is generally higher. Buyers interested in WLED should ask whether local pixel control, APIs, presets, and third-party integrations are officially supported before installation.
Application Scenarios
1. A 100-Foot One-Story Roofline
Consider a one-story house using the 100-foot, 60-light configuration. The installation begins at the garage, crosses the porch, follows the main eave, and ends near a side return.
The simplest logical order is:
-
Lights 0–14: Garage
-
Lights 15–29: Porch
-
Lights 30–49: Main eave
-
Lights 50–59: Side return
Create four WLED segments matching those ranges. Each segment can then use its own brightness and color while remaining part of whole-house effects.
For everyday use, all four segments might display warm white. During Halloween, the garage can use purple, the porch green, and the main eave a moving purple-blue gradient.
The practical requirement is to confirm the real light count and direction before mounting. Number the planned positions on paper and test a chase effect on the ground. If the chase moves opposite the intended installation direction, correct the branch orientation or approved WLED configuration before fastening every base.
2. Two Matching Gables With a Center-Out Effect
A house has two symmetrical front gables. The homeowner wants effects to begin near the central entrance and move outward toward both sides.
The physical cable route may run continuously from left to right, which would cause a normal chase to cross the first gable before reaching the second. To create symmetry, divide the two gables into segments and reverse the appropriate segment direction.
WLED’s segment controls support reversal, grouping, spacing, and offsets. Two visually matched sections can therefore move in opposite physical directions while appearing to travel outward together.
Test the effect from the street before saving the preset. If one gable contains more lights, the speed may appear different because the effect travels across unequal segment lengths. Adjust grouping, boundaries, or effect selection to create a balanced appearance.
This scenario demonstrates the distinction between physical wiring direction and visual animation direction.
3. A Dual-Output House and Garage Layout
An illustrative property has one controller location near the center of the facade. One controller output serves the main house, while the second serves the attached garage.
The configuration must identify the correct light count on both outputs. An incorrect count can cause one branch to stop early, create unused logical addresses, or shift the beginning of the second branch.
After both outputs are configured, WLED can represent them in one logical address space or create a segment for each output. The main-house and garage branches can then run:
-
One synchronized whole-property effect
-
Matching effects with different brightness
-
Separate colors
-
Independent everyday schedules
-
A coordinated preset with mirrored direction
The exact connector, output capacity, and light-count procedure must follow Lumary’s documentation. Generic WLED GPIO instructions are not a substitute for the product controller’s approved interface.
4. A 300-Foot Multi-Gable Installation
The 300-foot Lumary configuration contains 180 lights and is rated at 144W. A large facade may include lower eaves, upper gables, a porch, garage bays, and side returns.
Before installation, create a physical-light map:
| Architectural Area | Illustrative Light Range |
|---|---|
| Left garage bay | 0–19 |
| Right garage bay | 20–39 |
| Lower left eave | 40–64 |
| Front porch | 65–84 |
| Center gable | 85–114 |
| Lower right eave | 115–139 |
| Right upper gable | 140–164 |
| Side return | 165–179 |
These numbers are illustrative and must be replaced with the real installation counts.
Create WLED segments only after confirming the actual start and stop positions. Save a basic diagnostic preset using a different solid color for each segment. This immediately reveals whether the boundaries match the architecture.
Once verified, build effects and everyday presets. Keep a record of the segment table because future firmware changes, resets, or maintenance will be easier when the logical design is documented.
5. A 600-Foot Property With Multiple Power Sections
A large home and detached garage require 600 feet of permanent lights. Lumary’s published expansion limit is 1,200 feet, but additional power supplies are required every 300 feet.
The physical design must therefore account for at least two powered intervals. That does not automatically determine how many controllers, data branches, adapters, or injection accessories are required; those details must follow the Lumary installation manual.
From WLED’s perspective, the owner may want the property to behave as one coordinated visual system. From the electrical perspective, the installation contains defined power sections that cannot be ignored.
A safe planning sequence is:
-
Measure each building and roof section.
-
Define controller and approved power-supply locations.
-
Divide the project according to manufacturer power rules.
-
Establish the pixel order and output count for every branch.
-
Test each powered section independently.
-
Configure segments and presets.
-
Coordinate controllers through supported WLED or Home Assistant functions.
-
Document every power boundary, controller address, and segment range.
Do not join positive outputs from separate power supplies or improvise injection wiring because the effects appear correct in software. Visual synchronization does not prove electrical compatibility.
Editorial Assessment
Addressable LEDs work with WLED because each logical pixel can receive a separate digital instruction. The ESP32 controller continuously calculates color and brightness values, transmits them in the configured order, and repeats the process quickly enough to produce smooth effects.
The most important technical distinction is between control and power. WLED controls what the lights should display. The power supply, wiring, connectors, and injection system determine whether the lights receive appropriate electrical energy. Software cannot compensate for an incompatible voltage, undersized power supply, incorrect connector, or unsupported long-run arrangement.
Segments make large addressable installations practical by converting hundreds of pixel positions into meaningful zones. Mapping can correct unusual physical order, while presets save complete multi-segment states for later use. The JSON API and Home Assistant integration then allow those presets and zones to participate in broader smart-home automation.
Lumary’s advantage is that it combines documented ESP32 WLED compatibility with a packaged permanent outdoor lighting system. Buyers gain access to addressable effects and local automation without starting from bare LED components.
The system is not universally interchangeable with other WLED hardware. Its 36V input, controller outputs, channel structure, accessories, connectors, power-supply intervals, and firmware settings are product-specific. Use only compatible components and follow the installation guide.
Who Should Buy This Product: Choose the Lumary Permanent Outdoor Lights 3 if you want a complete roofline-lighting system with addressable effects, adjustable white, WLED, Home Assistant, 32 zones, and defined expansion options. It is especially suitable for homeowners who want more control than a closed scene library provides but do not want to engineer an exterior pixel system entirely from separate parts. A fully custom WLED build may better suit advanced electronics enthusiasts who need unrestricted controller and protocol selection, while professional installation is preferable when roof access, power design, or mounting complexity exceeds safe DIY work.
Frequently Asked Questions
Q1. What is the difference between addressable and non-addressable LEDs?
Addressable LEDs contain or connect to pixel-level control electronics that allow different positions on the same run to display different colors and brightness levels. A controller sends digital data identifying what each logical pixel should show.
Non-addressable RGB strips normally share red, green, and blue channels across the complete connected section. Every LED on that section therefore displays the same color and brightness.
WLED can support both categories, but addressable lights enable its most recognizable chases, gradients, segment effects, and individual-pixel control.
Q2. Does WLED provide power to addressable LEDs?
WLED is software and does not itself provide the main operating power. The ESP32 controller generates data, while a compatible power supply delivers electrical energy to the lights.
Some small DIY strips may receive limited power through a controller board during testing, but extended permanent installations require a properly sized external supply and distribution system.
The Lumary Permanent Outdoor Lights 3 uses a 36V light-string input and product-specific power architecture. Do not power it from a generic ESP32 development board or substitute a 5V, 12V, or 24V supply.
Q3. Does every visible LED have its own WLED address?
Not necessarily. Some products treat each physical LED as one logical pixel, while others group multiple LED chips or light sources under one address. A permanent puck may also contain multiple internal channels that operate together as one visible addressable light.
The relevant value is the product’s documented logical light count. Lumary lists 60, 90, 120, or 180 lights for its four standard lengths. Configure the controller according to the kit and installation instructions rather than counting unseen internal LED chips.
Q4. What happens if the WLED pixel count is configured incorrectly?
If the count is too low, WLED may stop sending useful data before reaching the end of the installed run. If it is too high, the controller will calculate nonexistent pixels, which can shift segment boundaries and make effects appear slower or misaligned.
With multiple outputs, an incorrect count or starting index can also move the logical beginning of a branch. This can cause effects to jump, reverse, or start in the wrong architectural section.
Test solid colors, a single-pixel chase, and segment boundaries at ground level before completing permanent mounting.
Q5. Can I connect any addressable outdoor light to a WLED controller?
No. The light and controller must use compatible voltage, protocol, signal level, channel configuration, color order, pixel grouping, connector pinout, and electrical capacity.
Even when two products both advertise WLED support, their connectors and power supplies may be completely incompatible. A connector that physically fits does not prove that its pins carry the same voltage or signals.
For Lumary Permanent Outdoor Lights 3, use the documented controller, power supplies, expansion segments, and product-specific accessories. Treat third-party substitutions or rewiring as unsupported unless Lumary provides explicit compatibility information.
