No Lightberry option in HyperCon system settings

Kaylesh SIvaguru · 21. Juni 2016

Using the Lightberry HD kit with rp3, openelec and hyperion. I am able to get the LEDs + ambilight working using the default hyperion settings - however I am unable to configure these settings via HyperCon (I am still able to change the colour of the LEDs via the HyperCon terminal but not after choosing a particular ambilight system; I tried APA102 with no luck). I have also tried the other ambilight system choices with no luck (the LEDs stop working and I have to run the default setup again on hyperion). I am wondering why the lightberry selection is missing as it has shown in setup screenshots I have seen online.

Also, I am unable to find where the default hyperion config file is saved. Even after sending config via SHH, I still cannot find it anywhere on the rp3.

Can anyone help with this?

Wastl · 22. Juni 2016

I had the same "problem" with my config of the lightberry-kit. it seems, lightberry changed the type of LEDs. my old kit is working with WS2801, the new ones with APA102.
I solved my problem by choosing "WS2801" in HyperCon. just give it a try

Kaylesh SIvaguru · 22. Juni 2016

APA102 works but only on the rpi3 hyperion settings. When I create a custom config file using hypercon (APA102) and upload them to storage/.config, the LEDs stop working and I can no longer change the colours via the colourwheel. There are two config files - hyperion.config.json and hyperion.config.json_bak. I tried changing both with no luck.

Brindosch · 22. Juni 2016

Greetings,
"Lightberry" is "WS2801"
So if you used "Lightberry" before just set it to WS2801 and you get the same result.

Here is the code line, as you see it is the same "device"
https://github.com/hyperion-pr…LedDeviceFactory.cpp#L136

Fietspomp · 27. Juni 2016

Hi, using Lightberry HD with APA102 LED strip, this is what I used in the config:

Code

{
    // DEVICE CONFIGURATION
    "device" :
    {
        "name"       : "HTPC",
        "type"       : "AdalightApa102",
        "output"     : "/dev/ttyACM0",
        "rate"     : 100000,
        "delayAfterConnect"     : 0,
        "colorOrder" : "bgr"
    },

Alles anzeigen

Brindosch · 27. Juni 2016

Greetings,
was this a question or a statement?

Fietspomp · 29. Juni 2016

This was a statement, using APA102 these settings work perfect for me!
My setup BTW, HTPC running LibreElec with Lightberry HD connected directly to USB port, which operates an APA102 strip with 60LEDS/m behind my TV.

EDIT: Found it here on the Lightberry website:
http://lightberry.eu/getting-started/

Code

USB Converter APA102
    "device": {
        "colorOrder": "bgr",
        "rate": 500000,
        "type": "adalightapa102",
        "name": "MyPi",
        "output": "/dev/ttyACM0"
    },

Also, if I choose APA102 as device, I get the following response:

Code

LEDDEVICE ERROR: Unknown/Unimplemented device apa102

But that's a different story I think

Brindosch · 29. Juni 2016

The device "apa102"
Is not compiled at x86 builds of Hyperion, cause it uses SPI (via GPIO) which is just available on a Raspberry PI and other boards like this.

The adalight device is for USB (so a connected arduino flashed with the appropriated sketch)

No Lightberry option in HyperCon system settings

Jetzt mitmachen!

Benutzer online in diesem Thema