@bpr, @all

I looked at the led modul on github, here the result.

This is to do:

At:
/boot/config.txt

change:
dtparam=spi=on

At:
/etc/eblocker-device.properties
change:
device.led.rgb.available = true

Plug in Led (WS2812)

Reboot eBlocker

And now its working ... tested  eBlocker 2.5.3 on Raspberry PI 3B

Pin-Out LED (WS2812)

        ________
       /                \
     /                    \
    I                      I
    I                      I
##############
    I       I      I      I
  Din Vdd Gnd Dout

    I       I      I     

  19     1     6
Pin on GPIO Port Raspberry PI

@bpr

is it possible to set these two settings for default?

nice evening 🍺 

PIO78

Thanks, the next days I look at the code.

regards

PIO78

The status values for the eblocker-led service are defined here:

https://github.com/eblocker/eblocker-led/blob/develop/lib/eblocker/led/status.rb

To activate a status you send the string "status=..." to localhost at port 9000 as described in the readme:

https://github.com/eblocker/eblocker-led

Unfortunately, I could not get the RGB LED to work on a Raspberry Pi. Maybe the timing of the SPI device is somehow different than on a Banana Pi M2+.

The low-level code for sending the bits via SPI to the LED is here:

https://github.com/eblocker/eblocker-led/blob/develop/lib/eblocker/led/spi.rb

Basically, a short pulse means 0 and a long pulse means 1. The timing specification is at:

https://cdn-shop.adafruit.com/datasheets/WS2812.pdf

Is there a documentation which values are send to the Led-Modul ?

regards

PIO78

Hi, it is not working with raspberry pi ...
In eblocker there is eblocker-led service on the SPI Pin.
I think it works only on Banana PI (kommercial eBlocker white case)

:o(

PI-eBlocker-Workshop

@benne