Compatibility
Find out whether your desktop and lights are a match.
On this page
LedAlert's home turf is Linux x86_64, KDE Plasma on Wayland, and one WLED RGB strip. Here's what fits.
Desktop
| Your desktop | Status |
|---|---|
| Supported | |
| Unverified | |
| Unverified | |
| Unverified | |
| Unverified | |
| Unverified | |
| Unsupported | |
| Unsupported |
Notifications must use the freedesktop notification service. In-app-only messages and other notification transports are not observed. Media markers need an MPRIS-capable player. The session must allow notification monitoring and provide a working lock service.
Lights
| Your lights | Status |
|---|---|
| One WLED RGB controller and stripOne continuous path, mapped in your room. | Supported |
| Up to 8,192 RGB LEDsConfiguration limit; actual performance depends on the device and network. | Supported |
| Multiple controllers, separate runs or matrices | Unsupported |
| RGBW/CCT-specific output and other controller protocols | Unsupported |
Use a trusted local network and one realtime controller. WLED needs HTTP 80 for connection and UDP 4048 for RGB output. LedAlert does not change persistent WLED settings; the device's own limits and realtime timeout still apply.
Your setup is not listed? See the roadmap for where support is headed and the contribution policy for how to land it — verified additions from real environments are exactly what we want.
Before you install
The Linux binary needs glibc 2.36 or newer, a graphical session, session D-Bus and working OpenGL/EGL. Check the bundle's BUILD-INFO.json for its measured requirements. A matching CPU or glibc version alone does not guarantee desktop compatibility.
Ready? Install and connect. Something not responding? Find a fix. For exact protocol behavior, see Lighting and integrations.