Can WLED Permanent Lights Work With Home Assistant?

Yes. WLED-compatible permanent outdoor lights can work with Home Assistant, provided the controller runs a supported WLED version and exposes the WLED JSON API. The Lumary Permanent Outdoor Lights 3 is particularly relevant because Lumary explicitly lists ESP32 WLED integration and Home Assistant compatibility alongside Alexa, Google Home, the Lumary app, a remote, and the physical control box.

The relationship is easiest to understand by separating the system into three layers:

• The permanent lights and power supplies provide the physical lighting hardware.

• WLED controls pixels, segments, colors, palettes, effects, speed, and presets.

• Home Assistant connects those lighting functions with schedules, sensors, calendars, dashboards, household modes, and other smart devices.

Home Assistant is therefore the automation layer, while WLED remains the specialized lighting engine. You might create a detailed Halloween effect in WLED, save it as a preset, and then have Home Assistant activate that preset automatically at sunset during the last week of October. At midnight, Home Assistant can switch to a low-brightness warm-white preset or turn the installation off.

According to the official Home Assistant WLED integration documentation, the integration requires WLED 0.14.0 or newer. Home Assistant can frequently discover a WLED controller automatically. If discovery does not work, the controller can be added manually by entering its hostname or local IP address under Settings > Devices & services > Add Integration > WLED.

Once connected, Home Assistant can expose more than a basic on/off switch. Depending on the WLED configuration, it can provide:

• A master light entity for overall power and brightness

• A separate light entity for each WLED segment

• Preset and playlist selectors

• A palette selector for each segment

• Effect speed and intensity controls

• Nightlight and synchronization switches

• LED-count, current, and uptime sensors when available

• Firmware-update information

• Controls for reversing or freezing individual segments

This creates substantially more flexibility than connecting a simple color-changing light through a generic smart plug. A smart plug can only energize or disconnect the system. The native WLED integration lets Home Assistant request actual lighting states and activate effects stored on the controller.

The most important planning concept is the WLED segment. A segment is a logical portion of the installed light run that can use its own color, effect, palette, brightness, direction, and animation parameters. The official WLED segment documentation explains that different zones can run different colors or effects and that ESP32 hardware normally supports up to 32 segments.

That aligns well with Lumary’s published 32-zone control. A homeowner could divide a roofline into zones such as:

• Front porch

• Left roof section

• Center gable

• Right roof section

• Garage

• Side entrance

• Rear patio

When two or more WLED segments are defined, Home Assistant creates an individual light entity for each segment as well as a master entity for overall power and brightness. This makes it possible to use a restrained warm-white front porch while displaying a seasonal effect across the garage—or to turn off zones that are not visible from an occupied part of the property.

Presets are equally important. WLED presets save complete lighting arrangements, including segment configurations. The official WLED preset guide documents support for as many as 250 presets, subject to the controller’s resources. A preset can preserve multiple segments, effects, palettes, brightness levels, speeds, and colors as one named state.

For most homeowners, preset-based automation is more dependable than asking Home Assistant to reconstruct a complex display one setting at a time. Instead of sending separate commands to 10 roofline zones, create a complete “Thanksgiving Warm Amber” preset in WLED and let Home Assistant activate it with one preset-selection action.

There are limitations. Home Assistant exposes only one color model per segment, so mixed RGB and tunable-white systems cannot necessarily have their color and white channels controlled independently through the standard light entity. Home Assistant also cannot directly set the secondary and tertiary colors used by many WLED effects. The recommended workaround is to configure the complete color arrangement in WLED, save it as a preset, and activate that preset from Home Assistant.

Home Assistant also does not expose every WLED usermod or every advanced capability of a custom firmware build. A sound-reactive effect might appear in the effect list even if the installed build lacks the hardware or compiled feature necessary to run it. These constraints do not prevent useful integration; they simply reinforce a practical division of responsibilities:

• Use WLED to design and test detailed pixel effects.

• Use Home Assistant to decide when and why those effects run.

• Use the manufacturer’s instructions to govern electrical configuration, extensions, power supplies, and installation.

The system can remain local for ordinary operation. Home Assistant communicates with WLED over the home network through the WLED JSON API, which can set power, brightness, colors, effects, segments, palettes, playlists, and presets. The official WLED JSON API reference describes these state and control functions. Do not expose a WLED controller directly to the public internet; use Home Assistant’s supported secure remote-access method if control away from home is required.

Network quality still matters. The controller should have reliable Wi-Fi coverage at its final outdoor location, and a DHCP reservation can prevent its local address from changing. Home Assistant discovery may fail on networks that block multicast DNS between subnets or isolate wireless devices. Manual configuration by hostname or IP address can solve ordinary discovery problems, but firewall rules must still allow Home Assistant to reach the controller.

The result is a capable local-first arrangement: WLED handles the visual complexity, Home Assistant supplies whole-home intelligence, and Lumary provides a packaged permanent-lighting system with published power and expansion rules.

Product Recommendation Analysis

The Lumary Permanent Outdoor Lights 3 system is a strong candidate for a Home Assistant household because the manufacturer documents both WLED and Home Assistant compatibility. Buyers do not have to begin by replacing the included controller with an undocumented third-party board merely to gain WLED access.

The product is offered in 100-, 150-, 200-, and 300-foot configurations containing 60, 90, 120, and 180 lights. Published power rises with those sizes from 48W to 144W. The system combines individually addressable color with adjustable 2200K–6500K white light, providing both decorative effects and practical architectural illumination.

Its 32-zone capability is especially useful in Home Assistant. A zone can represent a physical roof section, entrance, gable, or garage. After corresponding segments are configured in WLED, Home Assistant can address them independently through segment entities. A porch zone could respond to an arrival automation while the remaining roofline stays in a low-brightness evening scene.

The product page also lists more than 150 preset scenes, 28 music-responsive modes, 16 million colors, and an AI Lighting Creator. These Lumary-app features should not automatically be assumed to appear as identical native entities in Home Assistant. The standard Home Assistant integration exposes the capabilities reported by WLED; proprietary app functions may remain within the Lumary environment.

That distinction is important when evaluating compatibility. “Works with Home Assistant” does not mean that every button in the manufacturer’s app is duplicated on a Home Assistant dashboard. It means the system provides a supported WLED path through which Home Assistant can control standard lights, segments, effects, palettes, presets, playlists, and related entities.

Physical installation remains governed by the product’s own system architecture. Lumary publishes expansion up to 1,200 feet, with additional power supplies required every 300 feet. Home Assistant cannot eliminate voltage, controller, adapter, extension, or power-supply limits. Follow the installation manual for permitted cutting, extensions, controller arrangement, and power placement.

For a technically inclined homeowner, the principal benefits are:

• A complete outdoor lighting package with documented WLED support

• Native Home Assistant integration rather than smart-plug-only control

• Up to 32 logical lighting zones

• Adjustable white light for everyday use

• Addressable color effects for events and holidays

• Multiple fallback controls if Home Assistant is unavailable

• Clearly defined standard lengths and power levels

• Long-run expansion with stated power-supply intervals

The main tradeoff is configuration complexity. Home Assistant adds powerful automation, but a polished result requires the installer to map the light order, name entities, define segments, create WLED presets, and test how each state looks on the actual house. Buyers who only want a few scheduled scenes may find the Lumary app sufficient. Buyers who want lighting connected to calendars, occupancy, weather, alarm modes, or whole-home routines gain much more from Home Assistant.

Technical Specification Table

Specification	Lumary Permanent Outdoor Lights 3
Product type	Permanent outdoor eave and roofline lighting
WLED support	Manufacturer-documented ESP32 WLED integration
Home Assistant support	Listed by manufacturer; uses the native WLED integration
Available lengths	100 ft / 150 ft / 200 ft / 300 ft
Number of lights	60 / 90 / 120 / 180
Published power	48W / 72W / 96W / 144W
Light-string input	DC 36V; 1.33A / 2A / 2.66A / 4A
Adapter input	120V AC, 50/60Hz
Lighting system	Addressable color plus adjustable white
Available colors	16 million colors
White range	2200K–6500K
Output per light	60 lumens
Zone control	Up to 32 zones
Lumary preset scenes	More than 150
Music-responsive modes	28
Control methods	WLED, Home Assistant, Lumary app, Alexa, Google Home, remote, control box
Housing colors	White / Black
Mounting design	Patented low-profile slide-base
Published ingress protection	IP67 for lights, control box, and adapter on the current listing
Published operating range	-4°F to 113°F
Maximum published expansion	Up to 1,200 ft
Long-run power rule	Additional power supplies required every 300 ft
Expansion segment	24.6-ft segments sold separately

Specifications reflect the manufacturer’s current listing and should be confirmed for the exact configuration purchased.

How to Connect WLED Permanent Lights to Home Assistant

Begin with the physical system operating correctly through its intended controller. Test every light, confirm the pixel order, and verify that the controller is connected to the same reachable local network as Home Assistant. Do not begin by changing wiring, flashing unrelated firmware, or replacing manufacturer-supplied components when the product already provides documented WLED integration.

A practical setup sequence is:

1. Complete the manufacturer’s initial setup.
   Install the system within Lumary’s length, extension, and power rules. Confirm that all lights operate before creating automations.

2. Open the WLED interface.
   Identify the controller’s hostname or local IP address. Confirm the reported WLED version and verify that the system is running WLED 0.14.0 or newer, as required by Home Assistant’s current integration.

3. Reserve the controller’s network address.
   A DHCP reservation in the router helps keep the address stable. This is not mandatory when hostname resolution works reliably, but it simplifies troubleshooting.

4. Configure the LED count and physical order.
   Confirm that the WLED configuration matches the installed hardware. Incorrect counts or output settings can cause missing lights or unexpected behavior.

5. Create meaningful segments in WLED.
   Divide the roofline according to architecture or intended automation—for example, porch, center gable, garage, and side elevation. WLED’s own interface is the best place to establish the segment boundaries.

6. Create and test presets.
   Save complete states such as Everyday Warm White, Arrival, Halloween, Christmas, Party, Quiet Evening, and All Off. Test each preset before involving Home Assistant.

7. Add the WLED integration.
   In Home Assistant, open Settings > Devices & services. Accept the discovered WLED device or select Add Integration, search for WLED, and enter the controller’s hostname or IP address.

8. Review the created entities.
   Check the master light, segment lights, preset and playlist selectors, palettes, effect speed, intensity, synchronization switches, and sensors. Disable entities you do not need, but avoid deleting useful controls before testing.

9. Rename entities in Home Assistant.
   The integration uses indexed segment names such as Segment 1 and Segment 2 rather than WLED’s custom segment labels. Rename the Home Assistant entities to architectural descriptions such as Front Porch or Garage Gable.

10. Build simple automations first.
    Start with one sunset activation and one bedtime shutoff. Once those are reliable, add calendars, occupancy, weather conditions, and multi-controller coordination.

A basic Home Assistant automation can activate the lights and then select a WLED preset:

alias: Roofline - Everyday Warm White at Sunset
triggers:
  - trigger: sun
    event: sunset
actions:
  - action: light.turn_on
    target:
      entity_id: light.roofline
  - action: select.select_option
    target:
      entity_id: select.roofline_preset
    data:
      option: "Everyday Warm White"
mode: single

Entity IDs and preset names vary by installation. Select them from the Home Assistant interface rather than copying example identifiers blindly.

For a complex preset, avoid issuing another light.turn_on command immediately after selecting it. Home Assistant’s documentation notes that changing the light state after preset activation can clear the displayed preset selection. Activate the light first and the preset second, as shown above.

The purchasing framework below separates genuine Home Assistant compatibility from marketing language that merely describes app control.

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 Home Assistant path	“Smart-home compatible” is claimed without naming an integration or protocol	Manufacturer explicitly lists WLED and Home Assistant support	Provides a defined local integration path instead of relying only on cloud routines
WLED controller support	Addressable lights use a closed controller with no documented WLED access	Includes ESP32 WLED integration	Enables native segment, effect, palette, preset, and playlist control
Logical zone capacity	The entire roofline must display one state	Publishes 32-zone control	Architectural sections can become individual Home Assistant entities
Everyday white lighting	Product supplies color effects but lacks adjustable white	Provides 2200K–6500K adjustable white	One system can support subdued daily lighting and colorful events
Preset strategy	Complex effects must be reconstructed through many commands	WLED can save full multi-segment presets; Lumary also lists 150+ app scenes	Home Assistant can trigger repeatable displays with fewer network transactions
Control redundancy	Lights become unusable when one hub or cloud service is unavailable	Supports Home Assistant, WLED, app, remote, control box, Alexa, and Google Home	Multiple control paths improve operational resilience
Published power data	Wattage and system sizes are omitted	Lists four lengths with 48W–144W ratings	Supports circuit, energy, and operating-cost planning
Expansion architecture	Long-run claims omit power boundaries	Publishes expansion to 1,200 ft and additional supplies every 300 ft	Large properties can be planned as defined powered sections
Outdoor component rating	Only the visible lights have an environmental rating	Current page publishes IP67 protection for the lights, controller, and adapter	Reduces uncertainty, though placement and connections must still follow the manual
Network maintainability	Controller address and local integration cannot be identified	WLED supplies a local web interface and JSON API	Easier diagnostics, local control, and Home Assistant reconnection

Competitive Landscape

There are four broad approaches to combining permanent outdoor lights with smart-home control.

The first is a proprietary app-only lighting system. These products can be easy to set up and may include polished scene generators, but their usefulness in Home Assistant depends on whether the manufacturer maintains an official integration, offers a documented local API, or requires a cloud bridge. Basic Alexa or Google Home support does not automatically imply rich Home Assistant access.

The second is a fully custom WLED installation. A DIY enthusiast can select an ESP32 controller, addressable pixels, power supplies, wiring, enclosures, connectors, fuses, and mounting channels independently. This offers extensive hardware freedom, but the owner assumes responsibility for electrical compatibility, voltage drop, weather protection, data integrity, and system documentation.

The WLED-enabled Lumary permanent light package sits between those two approaches. It supplies a coordinated permanent-lighting product while preserving access to WLED and Home Assistant. That can be attractive to buyers who want WLED effects without designing the entire electrical system from individual components.

The third approach is ESPHome. ESPHome is a broad framework for connecting ESP-based sensors, switches, relays, lights, and custom devices to Home Assistant. It can control addressable LEDs, but WLED is more purpose-built for rich pixel effects, palettes, segments, playlists, and browser-based effect creation. ESPHome may be preferable when lighting is one function within a custom device containing sensors and relays. WLED is usually more convenient when elaborate addressable-light control is the principal task.

The fourth category is a professionally installed permanent-lighting system. Professional products may provide custom-cut channels, installer support, and an integrated finished appearance. However, some use closed controllers and proprietary cloud services. Homeowners should ask whether the installed system offers documented local control, whether Home Assistant integration is native or unofficial, and what functionality remains if the vendor’s cloud service changes.

Philips Hue represents a different ecosystem. Its Home Assistant integration is mature, but Hue’s conventional outdoor fixtures and light strips are not direct equivalents to an extended addressable-pixel roofline. Hue may be preferable for fixture-based path, wall, and landscape lighting. WLED is generally better suited to individual-pixel animations across long architectural runs.

Govee and Eufy offer consumer-oriented permanent outdoor lighting with extensive app scenes and smart-assistant features. Their appeal often lies in straightforward onboarding and coordinated proprietary ecosystems. The decisive comparison for a Home Assistant user is not the number of app scenes alone; it is whether the exact product offers the desired local entities, segment control, preset access, and automation behavior without depending entirely on cloud services.

Lumary’s differentiating combination is documented WLED support, explicit Home Assistant compatibility, 32-zone control, adjustable white light, multiple physical lengths, and a published long-run expansion plan. It is most compelling when those features will actually be used. A household that wants only a fixed dusk-to-midnight schedule may not need the added administration of Home Assistant.

Application Scenarios

1. Everyday Warm-White Lighting From Sunset to Bedtime

Consider a home with 150 feet of lights divided into porch, main roofline, center gable, and garage segments. The owner wants a warm architectural outline after sunset but does not want a saturated color display every evening.

Create an “Everyday Warm White” preset in WLED using a restrained brightness and a warm point within the system’s 2200K–6500K range. Save the complete segment configuration, including any zones that should remain off.

Home Assistant can activate the preset 15 minutes before sunset, reduce overall brightness at 10:00 p.m., and turn the installation off at midnight. A household “Guest Mode” helper could extend the schedule during a gathering.

Using a preset is preferable to sending separate white-temperature and brightness commands to every segment. The preset preserves the intended appearance and applies the zones as one coordinated state. The Lumary WLED-compatible roofline system provides the adjustable white range, while Home Assistant supplies the sunset and household-mode logic.

The final visual level should be judged from the street. Smart control cannot determine whether a particular brightness is excessive for the home, neighboring windows, or local lighting rules.

2. Calendar-Based Holiday Presets

A household wants autumn amber lighting during November, a red-and-green display in December, and a calm white state during the rest of the year. Manually selecting the correct scene every night eventually becomes inconsistent.

Design and save each complex effect in WLED:

• Everyday Warm White

• Fall Amber

• Thanksgiving Welcome

• Winter Red and Green

• New Year Sparkle

Home Assistant can select a preset based on calendar dates or a user-controlled seasonal helper. The automation should still include a cutoff time so an efficient LED system does not remain illuminated simply because the scene is automated.

Complex holiday effects demonstrate why WLED presets matter. The native Home Assistant integration cannot directly control the secondary and tertiary colors used by some effects. Saving the full design in WLED allows the preset to restore those parameters when Home Assistant activates it.

The Lumary Permanent Outdoor Lights 3 collection lists addressable color, 32 zones, and extensive scene options, while WLED and Home Assistant convert those capabilities into a repeatable seasonal schedule.

3. Arrival Lighting for the Porch and Garage

Suppose a family usually keeps the roofline at low brightness, but wants the porch and garage zones to brighten when someone arrives after dark. Home Assistant can combine a presence event, garage-door sensor, or approved outdoor motion sensor with a sun condition.

The automation might:

1. Confirm that the sun is below the horizon.

2. Activate an “Arrival” preset.

3. Brighten the porch and garage segments.

4. Wait five minutes after the garage closes or motion clears.

5. Restore the previous evening preset.

This is more nuanced than turning the entire roofline on at maximum brightness. Separate WLED segments let Home Assistant affect only the zones associated with arrival.

Permanent architectural lights should not be assumed to replace code-required entrance, stair, or security lighting. The smart permanent eave-light system can contribute to an arrival scene, but dedicated safety lighting should retain its intended function.

Careful automation design also prevents repeated triggers from constantly restarting an effect. Use an appropriate Home Assistant automation mode and include a cooldown or state check when necessary.

4. Main House and Detached Garage With Multiple Controllers

A property may have one WLED controller on the main house and another on a detached garage. Each controller appears as its own device in Home Assistant. This separation is often preferable to attempting an undocumented inter-building cable route.

Create matching preset names on both controllers—for example, Everyday Warm, Halloween, and Winter. Home Assistant can activate both selectors in the same scene or automation. If simultaneous visual timing is critical, investigate WLED’s native synchronization capabilities rather than assuming that two separate Home Assistant service calls will start on the exact same frame.

Home Assistant remains useful for high-level coordination:

• Both systems follow the same seasonal calendar.

• The garage can turn off earlier than the house.

• A maintenance helper can disable one building.

• A dashboard can show whether either controller is unavailable.

Reliable Wi-Fi is essential at both structures. If discovery does not cross network boundaries, add each controller by its reserved local address and confirm that firewall rules allow Home Assistant to reach it.

This scenario shows why local integration is valuable. The homeowner can coordinate physically separate installations without pretending they are one electrical run.

5. A 600-Foot Multi-Zone Property

Imagine a large home with 600 feet of selected eaves. Lumary publishes expansion up to 1,200 feet and requires additional power supplies every 300 feet. A 600-foot design therefore needs to be planned as more than a single ordinary 300-foot powered installation.

Home Assistant does not alter that rule. The physical design must follow the manufacturer’s manual for controller count, adapters, extension limits, power supplies, and permitted connections. A qualified installer should be involved when height, access, new receptacles, or electrical work makes the project unsuitable for ordinary DIY installation.

After the physical topology is documented, WLED segments can represent major facade areas. Home Assistant can then provide a simplified dashboard with controls such as:

• Whole Property – Everyday

• Front Facade – Event

• Rear Patio – Warm White

• Garage – Off

• Quiet Hours

• All Exterior Decorative Lights – Off

Do not expose dozens of rarely used technical entities on the primary household dashboard. Keep detailed WLED controls on an administrative view and give everyday users a small set of verified presets.

For a project of this scale, save configuration records, controller addresses, entity names, power-supply locations, and preset definitions. The expandable Lumary permanent-light platform makes the physical scope possible within its documented limits; Home Assistant makes the resulting zones manageable.

Editorial Assessment

WLED permanent lights can work very well with Home Assistant, and the integration is much deeper than basic voice-assistant control. Home Assistant can represent WLED segments as individual lights, activate presets and playlists, select palettes, adjust effect speed and intensity, and connect the installation to household schedules and sensors.

The most reliable operating model is to build complex lighting states in WLED and use Home Assistant to choose when they run. That approach avoids attempting to reproduce every color and effect parameter through a long series of automation actions. It also works around the integration’s limited access to secondary and tertiary effect colors.

Lumary’s strongest advantage for this use case is that it explicitly documents WLED and Home Assistant support as part of a complete permanent outdoor lighting system. The 32-zone design aligns naturally with WLED’s ESP32 segment capacity, while adjustable white light makes the installation useful beyond holiday effects.

Compatibility does not eliminate planning. The controller needs WLED 0.14.0 or newer for the current native integration, the local network must allow communication, and mixed color-plus-white hardware has integration limitations. Proprietary Lumary app features should not be assumed to appear identically in Home Assistant.

Physical limits remain separate. Use the manufacturer’s guide to determine allowable lengths, extensions, cuts, adapters, and power supplies. Home Assistant can automate a 600-foot installation, but it cannot power one or make an unsupported electrical arrangement safe.

Who Should Buy This Product: Choose the Lumary Permanent Outdoor Lights 3 if you want a packaged permanent-lighting system with documented WLED and Home Assistant support, expect to use segments or presets, and are comfortable performing moderate network and automation setup. Choose an app-only product if simple scheduled scenes are your entire requirement. Consider a professionally installed system when roof access, power distribution, or facade complexity—not smart-home configuration—is the main challenge.

Frequently Asked Questions

Q1. Does Home Assistant automatically discover WLED permanent lights?

It often does. Home Assistant uses network discovery to find compatible WLED devices and displays them as discovered integrations. If the controller does not appear, go to Settings > Devices & services > Add Integration, select WLED, and enter its hostname or local IP address.

Automatic discovery can fail when multicast DNS is blocked, Home Assistant and the controller are on isolated networks, or wireless client isolation is enabled. Assigning the controller a DHCP reservation can also make manual configuration and future troubleshooting easier.

The current native integration requires WLED 0.14.0 or newer. Confirm the version reported by the controller rather than assuming compatibility from the presence of a WLED-looking interface.

Q2. Can Home Assistant control individual WLED zones?

Yes. WLED calls these zones segments. When one segment is configured, Home Assistant normally creates one light entity for the installation. When two or more segments are present, it creates separate segment light entities and a master light entity for overall power and brightness.

Define segment boundaries in WLED first, verify their physical locations, and then rename the resulting Home Assistant entities. The integration does not currently use WLED’s custom segment names, so labels such as “Segment 1” may need to be changed to “Front Porch” or “Garage Gable” inside Home Assistant.

Q3. Can Home Assistant activate WLED presets?

Yes. The WLED integration creates a preset select entity, allowing an automation, script, scene, or dashboard control to activate presets stored on the controller.

Presets are the preferred method for complex multi-zone effects because they can preserve colors, palettes, effects, brightness, speed, and segment configuration. They also provide a workaround for effect parameters that the native integration does not expose directly.

Create and test each preset in WLED first. Give it a short, distinctive name and then select that exact option in the Home Assistant automation.

Q4. Can Home Assistant control Lumary’s adjustable white and RGB colors independently?

Not always in the way a user might expect. The native WLED integration exposes one color model per segment. For mixed RGB-plus-CCT or RGBW-plus-CCT configurations, Home Assistant cannot currently control the color and tunable-white channels independently at the same time through a single segment entity.

Use straightforward Home Assistant controls for compatible basic states. For carefully tuned warm-white settings or effects using multiple colors, configure the desired result in WLED and save it as a preset. Home Assistant can then activate the finished preset without reconstructing its channel settings.

Q5. Will the lights still work if Home Assistant goes offline?

The lighting hardware and controller do not depend exclusively on Home Assistant for every control path. The Lumary product page lists the Lumary app, WLED, Alexa, Google Home, a remote, and the physical control box in addition to Home Assistant.

Automations hosted by Home Assistant will not execute while the Home Assistant server is unavailable, and Home Assistant dashboards will not control the device during that outage. However, presets and schedules stored directly on the WLED controller may continue according to their own configuration, and the product’s alternative controls can remain available.

For a resilient installation, save essential effects as WLED presets, keep at least one local control method accessible, document the controller address, and avoid making the system’s only practical off command dependent on a single automation server.