Hi everyone! ![]()
We continue with the light
: here is WLED, the open-source firmware found on almost all DIY LED strips based on ESP8266 or ESP32. Everything works locally, via the WLED API, without any cloud.
What it does
Automatic discovery of WLED controllers in the Discovery tab, with an IP entry as a backup. A controller keeps its device even if its box changes its address.
On/off, brightness, color, white temperature (CCT strips), and white channel (RGBW).
Effects, palettes, and presets in lists read directly from the controller, with the speed and intensity of the effect in sliders.
Nightlight and UDP sync.
Optionally, one device per segment, to control each piece of strip separately.
Real-time updates: a change made from the WLED app appears immediately in Gladys.
Scenes „Apply a preset“ and „Launch an effect“, a trigger „Preset activated“, and a widget with your favorite presets and effects, in one gesture.
The cool thing
Sunset → the living room strip switches to your „Cosy“ preset
Someone rings → the strip flashes red
Installation
Gladys 5.1 minimum.
It will arrive in the store during the day. In a hurry? Integrations → Install from GitHub, with the address GitHub - guim31/gladys-wled: WLED LED strips over the local network (effects, palettes, presets) for Gladys Assistant · GitHub
- In Gladys: Integrations → WLED → Install.
- Discovery tab: your controllers appear automatically. Otherwise, enter their IP address in the configuration.
Honest small reservations: only the main color is managed, preset and effect names are typed manually in the scenes, and you need IP addresses (.local names don’t work).
Developed without the hardware: I don’t have any WLED at home. Tests are based on real responses from controllers (WLED 0.14 to 16), but nothing beats your own strip. Give me the version of WLED and the type of strip in your feedback!
Like the previous ones, it is developed with Claude Code
. Independent project, not affiliated with the WLED project.
Do you have WLED at home? I’m counting on you ![]()
