I’m a new Hyperion user on a Raspberry Pi 5 (LibreELEC) with an SK6812 RGBW strip.
On the Pi 5 the provided ws281x driver doesn’t work (This came by on this forum too). Hyperion gives:
Device disabled, device 'ws281x' signals error:
Failed to open. Hardware revision is not supported
That makes sense—the Pi 5 removed the old DMA/PWM path that the ws281x backend relied on. What does work, is the newer ws2812-pio overlay.
I enabled the kernel overlay:
The kernel creates this device:
I can write RGBW data to it manually and the LEDs work fine:
So the kernel side is working.
What happens in Hyperion
I had an idea, and set the LED device to “file” and point it at /dev/leds0, Hyperion does send data and the LEDs turns on. But I cannot define WLED and remote control doesn't work (Tyring to change colour) It looks like using the generic file output for continuous LED updates isn’t a good solution.
Request
Would it be possible to add proper support in Hyperion for the Pi 5 PIO LED device (/dev/leds0)?
A dedicated backend would avoid the issues seen when using the “file” device and would let Raspberry Pi 5 + SK6812 users drive LED strips normally again.
Environment details:
-
Raspberry Pi
Kernel: Linux kodi 6.12.56
-
LibreELEC
-
SK6812 RGBW
-
GPIO 18
-
Device:
/dev/leds0
If you need any additional logs or testing, I can provide them.