Skip to content

Home Automation

It is possible to interface WLED with home automation systems and other 3rd-party software. You can use any API WLED provides (JSON, HTTP, UDP, MQTT); JSON is preferred. This page is intended for sample code and configs others use to control WLED from various 3rd-party software.

Home Assistant

Using the native integration

Compatibility notice

WLED devices are not supported by Home Assistant 2022.2 or later if a CCT bus is configured or White Balance Correction is enabled.

We hope to resolve this issue as soon as possible. As a temporary workaround you can enable the option Calculate CCT from RGB in LED settings.

WLED can be configured using the WLED integration in the Home Assistant frontend.

Menu: Configuration -> Integrations.

In most cases, the WLED devices will be automatically discovered by Home Assistant. Those automatically discovered WLED devices are listed on the integrations page.

If for some reason (e.g., due to lack of mDNS support on your network), the WLED device isn't discovered, it can be added manually.

Click on the + sign to add an integration and click on WLED. After completing the configuration flow, the WLED integration will be available.

WLED integration documentation

Workarounds for known HA integration limitations

The native integration has known limitations documented in the official HA WLED integration docs. Below are practical workarounds using WLED's REST API.

Custom palettes not visible in HA

Palettes uploaded as palette0.json through palette9.json do not appear in Home Assistant's palette selector—only built-in palettes are available.

Workaround: Use a rest_command to set the palette by ID. Custom palettes are numbered backwards from 200: palette0.json = ID 200, palette1.json = ID 199, etc.

rest_command:
  wled_set_palette:
    url: "http://{{ ip }}/json/state"
    method: POST
    content_type: application/json
    payload: '{"seg":[{"id":0,"pal":{{ palette_id }}}]}'

Example automation: 

action: rest_command.wled_set_palette
data:
  ip: "192.168.1.100"
  palette_id: 200  # palette0.json

AudioReactive usermod not controllable

Home Assistant does not expose usermods (such as AudioReactive) as entities.

Workaround: Use rest_command to enable/disable the AudioReactive usermod:

rest_command:
  wled_audioreactive_on:
    url: "http://192.168.1.100/json/state"
    method: POST
    content_type: application/json
    payload: '{"AudioReactive":{"enabled":true}}'
  wled_audioreactive_off:
    url: "http://192.168.1.100/json/state"
    method: POST
    content_type: application/json
    payload: '{"AudioReactive":{"enabled":false}}'

Mixed RGB+CCT strips – only one color model active

WLED strips with both RGB and CCT channels (e.g., WS2508) cannot control RGB and CCT independently. Home Assistant activates only one color model at a time.

Workaround: In the WLED web UI, go to LED Settings and enable Calculate CCT from RGB. This makes WLED compute CCT values from RGB, allowing normal operation with Home Assistant.

For CCT-only strips with White Balance Correction enabled, disable WBC or enable "Calculate CCT from RGB" to restore HA 2022.2+ compatibility.

No master control for color/effect across all segments

There is no single entity to control color, effect, and brightness across all segments simultaneously. Light groups send separate requests per segment, causing staggered transitions and latency.

Workaround: Use presets. Create a preset in WLED with the desired configuration (effect, colors, parameters) applied to all segments. Then activate it from Home Assistant:

action: select.select_option
target:
  entity_id: select.wled_preset
data:
  option: "All Segments – Rainbow"

A preset encapsulates the complete state (effect, palette, brightness, speed, colors for all segments), ensuring all segments are updated simultaneously in a single transaction.

Alternatively, use a single REST API call to set all segments in one request:

rest_command:
  wled_all_segments_effect:
    url: "http://192.168.1.100/json/state"
    method: POST
    content_type: application/json
    payload: >-
      {"seg":[
        {"id":0,"fx":{{ fx }},"pal":{{ pal }},"bri":{{ bri }}},
        {"id":1,"fx":{{ fx }},"pal":{{ pal }},"bri":{{ bri }}}
      ]}

Create a script for commonly used effects (adjust segment IDs to match your WLED config):

script:
  wled_rainbow_all:
    sequence:
      - action: rest_command.wled_all_segments_effect
        data:
          fx: 9       # Rainbow effect
          pal: 11     # Rainbow palette
          bri: 200

Secondary and tertiary effect colors cannot be set from HA

Home Assistant's WLED integration exposes only the primary (foreground) color. Secondary (background) and tertiary colors used by many effects are inaccessible.

Workaround A – Use presets:

Configure the desired colors (primary, secondary, and tertiary) directly in the WLED web UI, save the configuration as a preset, then activate it from Home Assistant:

action: select.select_option
target:
  entity_id: select.wled_preset
data:
  option: "Rainbow with Custom Colors"

This is the simplest approach and does not require parameterizing colors.

Workaround B – Set all colors via REST API:

If dynamic color control is needed, use the WLED REST API:

rest_command:
  wled_set_colors:
    url: "http://192.168.1.100/json/state"
    method: POST
    content_type: application/json
    payload: >-
      {"seg":[{"id":0,"col":[
        [{{ r1 }},{{ g1 }},{{ b1 }}],
        [{{ r2 }},{{ g2 }},{{ b2 }}],
        [{{ r3 }},{{ g3 }},{{ b3 }}]
      ]}]}

Field mapping: col[0] = primary (Fx), col[1] = secondary (Bg), col[2] = tertiary (Cs).

Example call: 

action: rest_command.wled_set_colors
data:
  r1: 255
  g1: 0
  b1: 0
  r2: 0
  g2: 255
  b2: 0
  r3: 0
  g3: 0
  b3: 255

Using MQTT

Alternatively, MQTT can be used (not recommended). MQTT autodiscovery is not supported. In case you want to configure the device manually:

Expand to show MQTT configuration 

light:
  - platform: mqtt
    name: "Kitchen Floor Lights"
    command_topic: "wled/all"
    brightness_command_topic: "wled/all"
    rgb_command_topic: "wled/all/col"
    rgb_command_template: "{{ '#%02x%02x%02x' | format(red, green, blue)}}"
    effect_command_topic : "wled/all/api"
    effect_list:
    - "FX=0"
    - "FX=1"
    - "FX=2"
    - "FX=3"
    - "FX=4"
    - "FX=5"
    - "FX=6"
    - "FX=7"
    - "FX=8"
    - "FX=9"
    - "FX=10"
    - "FX=11"
    - "FX=12"
    - "FX=13"
    - "FX=14"
    - "FX=15"
    - "FX=16"
    - "FX=17"
    - "FX=18"
    - "FX=19"
    - "FX=20"
    - "FX=21"
    - "FX=22"
    - "FX=23"
    - "FX=24"
    - "FX=25"
    - "FX=26"
    - "FX=27"
    - "FX=28"
    - "FX=29"
    - "FX=30"
    - "FX=31"
    - "FX=32"
    - "FX=33"
    - "FX=34"
    - "FX=35"
    - "FX=36"
    - "FX=37"
    - "FX=38"
    - "FX=39"
    - "FX=40"
by @acid2000

openHAB

In openHAB 3-based environments, you are able to use the native openHAB WLED Binding, which also supports discovery of your WLED devices.

For older openHAB (2.5.x) environments, the connection can be configured via MQTT broker & Openhab MQTT Binding (2.5x) with configuration files. Please find the details here.

Other