WLED Smart-Home-Integration, kostenlos und Open Source
WLED-Controller für LED-Streifen im lokalen Netzwerk: Farben, Effekte, Paletten, Presets, Segmente.
Veröffentlicht von guim31
- Geräte
- Version 1.1.0
- Erfordert Gladys >=5.1.0
- ★ 0
Die Dokumentation dieser Integration wird von ihrem Autor geschrieben und ist bisher nur auf Englisch verfügbar.
Control your WLED LED strips from Gladys, over your local network: color, brightness, effects, palettes, presets and segments, updated in real time.
Developed without the hardware: feedback welcome. This integration was built and tested against real answers of WLED controllers, not against physical strips. If something does not work as described, please say so on the Gladys forum or in the issues.
What you need
- Gladys Assistant 5.1.0 or later.
- A WLED controller (ESP8266 or ESP32) connected to the same network as Gladys. WLED 0.14 or later is recommended; 0.13 should work.
Add your controllers
- Install the integration from the Gladys catalog. The install screen asks to
let Gladys look for WLED controllers on the network (mDNS,
_wled._tcp): accept. - Open the Discovery tab: every controller found is listed, with the name set in WLED. Click Add, pick a room, save.
- A controller is missing? Find its IP address in the WLED app (Config → WiFi Setup) or in your router, enter it in Configuration → Controller IP addresses (several addresses separated by commas), save, then open Discovery again.
Tip: give each controller a fixed IP address in your router (DHCP reservation). The integration recognizes a controller by its MAC address and follows it when its address changes, but a fixed address is found faster.
What each device offers
Each controller is one device:
| Feature | What it does |
|---|---|
| Light | On / off |
| Brightness | 0 to 100 % (0 turns the strip off) |
| Color | The color of the strip (RGB strips); picking one turns it on |
| Color temperature | From warm (2000 K) to cold (6535 K) white, on strips with CCT whites |
| White channel | The white LEDs of RGBW strips, 0 to 100 |
| Effect | The effect list of your controller (Solid, Rainbow, Fire 2012…) |
| Palette | The color palette used by the effect |
| Effect speed | 0 to 100 |
| Effect intensity | 0 to 100 |
| Preset | Your WLED presets and playlists; "None" once the state changed |
| Nightlight | Starts the WLED nightlight (duration and mode set in WLED) |
| UDP sync | Sends the changes to the other WLED controllers in sync with this one |
Only what your strip can do is offered: no color temperature on a plain RGB strip, no white channel without white LEDs.
The effect, palette and preset lists are read on the controller. A preset you save in WLED shows up in the list on its own, within seconds.
Segments
WLED can split a strip into segments. By default, the controller device drives the segments selected in WLED, exactly like the WLED interface; on a strip with a single segment, that is the whole strip.
To control each segment on its own, choose Also one device per segment in Configuration → Segments, save, then add the new devices from Discovery. They are offered for controllers with at least two segments, and are named after the segment names set in WLED. A segment device has its own light, brightness, color, effect, palette, speed and intensity; turning a segment on also turns the controller on. Presets, nightlight and sync stay on the controller device.
Feature names are given when you add a device, in the language chosen in Configuration → Language of the feature names: English, French, German or Spanish. The integration's own texts (configuration, widget, scenes, messages) follow the language of your Gladys in these four languages.
Real time
Every controller tells Gladys about each change the moment it happens, whatever made it: the WLED app, a physical button, a schedule, an infrared remote, or another controller in sync. If the connection drops, the integration asks the controller for its state every 30 seconds while it reconnects.
The badge on each device shows local when the controller answers, and unreachable when it does not (unplugged, Wi-Fi lost). Commands sent to an unreachable controller fail with a message.
Scenes
The integration adds its own cards to the scene editor, under Integrations:
- Apply a WLED preset (action): applies a preset or starts a playlist, given by its name (as written in WLED, case does not matter) or its number. The following actions can read the preset number and name.
- Start a WLED effect (action): turns the light on and starts an effect,
given by its name (for example
Rainbow) or number, with an optional palette (for exampleParty), speed and intensity (0 to 100). Choose a segment device to start the effect on that segment only. - WLED preset activated (trigger): starts the scene when a preset or
playlist is started outside Gladys (WLED app, button, schedule, remote).
Optionally pick the controller and type the preset name; left empty, any
preset matches. The following actions can read
preset(its name) andpreset_id(its number). Presets applied by Gladys itself do not fire it, so a scene cannot loop on itself.
Turning on, brightness and color are the standard Gladys light actions.
Dashboard
Add the WLED widget to a dashboard and pick a controller (or a segment device) in its settings. It shows:
-
the brightness, live;
-
whether the light is on, the current effect, palette and preset;
-
one-tap buttons, four at most:
- your favorite presets: the ones you marked in WLED (give them a Quick load label in the preset settings), or your first presets if none is marked;
- the effects chosen in the widget settings, under Effect buttons (Solid and Rainbow until you change them; an effect your controller does not have is left out). With presets on the widget, two places stay for the effects.
The active preset or effect has a check mark. To start any other effect, use the Effect list of the device, or the Start a WLED effect scene action.
Troubleshooting
- No controller in Discovery: Gladys and the controller must be on the same network (mDNS does not cross routers or VLANs). Enter the IP address in Configuration, then use Search for controllers: the message under the button lists the controllers found and how they are reached.
- A controller stays unreachable: check that its web page opens at
http://<its address>from a computer on the same network. Names ending in.localdo not work in the integration: use the IP address. - States arrive late: on a controller built without WebSocket support, changes made outside Gladys take up to 30 seconds to show. WLED also accepts a limited number of WebSocket clients at once: close the WLED app tabs you do not use.
- The integration logs everything it does: open the integration logs from the
Gladys interface, with
LOG_LEVEL=debugfor the full detail.
This integration is not affiliated with the WLED project.
Konfigurationseinstellungen
Diese Einstellungen fragt WLED in seinem Konfigurationsbildschirm in Gladys ab.
| Einstellung | Typ | Pflichtfeld | Beschreibung |
|---|---|---|---|
| Deine Controller finden | section | Nein | WLED-Controller im selben Netzwerk wie Gladys werden automatisch gefunden (mDNS): Öffne den Tab „Entdecken“. Fehlt einer, gib unten seine IP-Adresse ein (in der WLED-App unter Config, WiFi Setup angezeigt). |
| IP-Adressen der Controller | string | Nein | Optional, durch Kommas getrennt. Nur für Controller nötig, die die automatische Erkennung nicht findet. |
| Segmente | select | Nein | Jeder Controller ist ein Gerät, das die in WLED ausgewählten Segmente steuert (den ganzen Streifen, wenn es nur eines gibt). Du kannst auch ein Gerät pro Segment erhalten. |
| Sprache der Funktionsnamen | select | Nein | Namen, die den Funktionen neuer Geräte gegeben werden (Licht, Helligkeit, Effekt…). |
So installierst du WLED in Gladys
- Öffne in Gladys Integrationen: WLED erscheint im Katalog neben den nativen Integrationen, mit einem Community-Badge.
- Klicke auf Installieren. Gladys lädt das Docker-Image (
ghcr.io/guim31/gladys-wled:1.1.0) herunter, startet es in einer vom Kern isolierten Sandbox und erzeugt die Oberfläche der Integration (Geräte, Erkennung und Konfiguration). - Öffne den Bildschirm Konfiguration der Integration, fülle die Einstellungen aus und speichere.
- Du kannst sie auch direkt über die URL ihres Repositorys installieren: https://github.com/guim31/gladys-wled.
WLED benötigt Gladys >=5.1.0. Der Katalog in Gladys wird stündlich aktualisiert, eine neue Version ist also spätestens eine Stunde nach ihrer Veröffentlichung verfügbar.
Du nutzt Gladys noch nicht? Es ist kostenlos und Open Source: folge der Installationsanleitung, um loszulegen.
Über externe Integrationen
WLED ist eine externe Integration: eine Community-Integration, die als Docker-Container verpackt und auf GitHub veröffentlicht wird. Gladys installiert sie mit einem Klick und führt sie in einer vom Kern isolierten Sandbox aus. Sie wird von guim31 veröffentlicht und gepflegt, nicht vom Gladys-Kernteam.
- Alle externen Integrationen durchsuchen
- Die nativen Integrationen entdecken, die in Gladys eingebaut sind
- Deine eigene externe Integration bauen und veröffentlichen
- Quellcode auf GitHub — Quelle dieser Dokumentation