What control interfaces and integrations does WLED support?

Updated

WLED exposes a broad set of control interfaces that fall into three groups: network protocols for real-time lighting data (E1.31/Art-Net, DDP, UDP realtime, tpm2.net), application-level APIs for automation (HTTP Request API, JSON API, MQTT, Websocket), and hardware or ecosystem integrations (DMX input/output, Philips Hue, ESPNow remotes, UDP sync between WLED devices). The right choice depends on what is sending the data: a lighting console, a home automation hub, a media server, or another WLED node.

Network protocols for real-time light data

These interfaces stream pixel data to WLED over the network, so they suit media servers, lighting desks, and visualizers rather than simple on/off automation.

Interface Typical sender Notes
E1.31 (sACN) / Art-Net Lighting consoles, VJ software, xLights Listed together as a DMX-over-IP input
DDP Realtime Pixel-mapping and LED control tools Efficient distribution of large pixel counts
UDP Realtime / tpm2.net Realtime visualizers Low-latency streaming to the strip
UDP Sync Other WLED instances Keeps multiple WLED devices in step with each other

DMX also works in both directions: WLED can output DMX and accept DMX input, so it can act as a bridge between a DMX chain and addressable LEDs.

Application APIs and home automation

If you are triggering effects, presets, or colors from software rather than streaming frames, these are the relevant interfaces:

  • HTTP Request API — send commands over HTTP; the documentation notes presets can be used to automatically execute API calls.
  • JSON API — structured state and control, the usual target for scripts and dashboards.
  • MQTT — publish/subscribe control, the common path for home automation systems.
  • Websocket — persistent connection for live state updates and control.
  • Remote Control — grouped in the docs alongside the API options above.

For broader automation, WLED documents a Home Automation section and Remote Access / IFTTT, which covers reaching a device from outside the local network. There is also an OTA Lock option and an "Accessing WLED over Internet" topic, so remote reachability is a documented configuration rather than an assumed default.

Ecosystem and hardware integrations

  • Philips Hue — listed as a supported interface, for integrating WLED into a Hue-centric setup.
  • ESPNow Remotes — low-latency remote control between ESP devices without Wi-Fi infrastructure.
  • Relay Control — switch a relay alongside the LEDs.
  • Audio Reactive WLED — drive effects from sound input.
  • Ethernet (LAN) — wired networking as an alternative to Wi-Fi.

How to choose

  • Streaming frames from a PC or console → E1.31/Art-Net, DDP, or UDP Realtime.
  • Triggering presets from a smart home hub → MQTT or the JSON/HTTP API.
  • Keeping several WLED strips identical → UDP Sync.
  • Mixing WLED into an existing Hue or DMX installation → Philips Hue integration or DMX input/output.

The project's own documentation organizes all of this under an Interfaces section, with setup details in the Quick Start and Getting Started pages.