Raspberry Pi 2 & Lightberry = <3

Have you seen the news? Raspberry Pi 2 is out and gues what?

It’s AWESOME! Quad core processor and 1GB of ram makes this thing fly over movies, and be the greatest media center to ever be under my TV. While I’ve been used to Raspi 1 occasional slowness and still loved it, this has no sign of slowing. Highly recommended.

We get a ton of emails whether RPI2 works with lightberry, it does, however we have to make an alteration to openELEC as it comes with SPI disabled. It’s fairly simple process (as described below) but The Simple Way ™ is avaliable here.

It’s required for Raspberry Pi 2 only.

Let’s get to it, first, start either with fresh openELEC installation on modify your current one. Plug your sd card to computer and open it. Place enable-spi-overlay.dtb file in overlays folder in main folder of SD Card. Then open config.txt in editor that recognize linux endings. Add below line to the end of the file:

And viola, safely remove from computer, put in your RPI2, boot and enjoy :)

Here is your raspberry pi ampilight system!
  • James

    Hi. I purchased my STK1160 grabber from lightberry. I was so pleased to see the build OpenELEC 5.0.1 (Custom build) with stk1160 support for RPi2 on this site. Thanks !!!
    It works perfectly. I have a question. Is it easy to upgrade to the later versions of OpenElec. It is now at 5.0.3. As an experiment I tried to upgrade but this causes the grabber to have random flashes. It nearly works so it is capturing but not usable. I am just interested what steps are needed to take an openelec build and add the STK1160 support.
    Thanks for the great work !

    • http://raspberry-at-home.pl/ Tomasz Szczerba

      You have to compile it for yourself. The problem is with the stk1160 driver that is not performing very well. We will try to keep it up to date.

      • James

        Excellent news. Thanks.

        I must say that this 5.0.1 release is brilliant. I have tuned my hyperion config file and the STK1160 device is giving very good smooth results. As good as the internal grabber almost.

        • Luigii

          can you show me your hyperionconfig? matthias.luig@gmail.com

          • James

            These are the two config files I use to either use internal or external grabber

            Good Luck !

            https://copy.com/oKaW1VI6nWeSlkdW

            https://copy.com/Ax2pwFTxwAJzUiNl

          • Wyatt

            Hello I have flashing too … in priority when i take 900 garbber work but not when i play video with kodi and when i take 1100 input hdmi flashing but play video with kodi work …

        • Michael Bovet

          Would also be happy to have a look at your config since my RPi2 + stk1160 is flashing as hell also with the image provided on the Lightberry website. Could you mail it to mbovet85@gmail.com? Thanks!

  • hari-bo

    I’m using Rasplex (build upon OpenElec) and tried this fix but it still won’t work, maybe it is the GPIO position which i’m using because your picture above the article show another position as the one here on page four, http://img.lightberry.eu/download/doc/Lightberry_manual_EN.pdf
    Which one are you using?

  • Legacy

    I have both a Raspberry Pi B+ and a Raspberry Pi 2 running the correct versions of OpenELEC for the aforementioned models. I’m also running the Lightberry HD and HDMI Premium Kit with my setup. I can confirm that there is definitely something wrong when running the Raspberry Pi 2 with the current OpenELEC (Custom Build). My Raspberry Pi B+ and Lightberry HD/HDMI Premium Kit work perfectly together, but as a test I ran the same wiring, hyperion config file, and system settings with the Raspberry 2. The Raspberry Pi 2 either produces the correct color from the grabber with an intense strobe effect or does not react to the grabber image at all. After much testing/troubleshooting, the lights eventually stopped reacting altogether. I loaded the img file on my SD card two more times with the same result. I then switched the grabber and HD back to my Raspberry Pi B+ model, and everything worked immediately/perfectly again. I really would like to use the Raspberry Pi 2 model if possible, as it is so much faster… is anyone out there having any luck with this setup?

  • Stephan

    Bought a lightberry and this image is working flawlessly. Thanks a lot. There is only one thing missing to perfection: I want to add a second hyperion instance which controls my philips hue lights in addition to the lightberyy leds. I need a second instance and vloopback in order to have a second device for framegrabber. Do you have any guidance how to add this?

    • Rui Ramos

      x2 :)

    • Jacek

      Unfortunately we haven’t had time to play with it this way. I suggest you have a look at hyprion’s issue list to get more info

  • James

    Hi guys. Will there be any updated builds in the future for latest Open Elec versions.

    If not is there any guide that would let me do the updates manually ?

    I’m still using

    OpenELEC 5.0.5 (Custom build) with stk1160 support for RPi2

    Which has been fine but would like to keep up with latest OpenElec builds.

    Many thanks !

    Note I’m willing to paypal donations for this service.

    Thanks !

    • Jacek

      Yes. I am waiting for OE6.0 official release before preparing new image

      • James

        Thank you Jacek. That’s great news !

      • James

        Hi guys. I see OE6 is official now. Fingers crossed on the new image coming :)

        Thanks.

        James

        • Jacek

          img.lightberry.eu/download/OpenELEC-RPi2.arm-lightberry-6.0.0.zip

          • Cláudio Castro

            Hi Jacek! Is there any change in the Hyperion code in this version, or can we simply update our old Openelec version with the stock stable one? Since I updated my build I’ve been having some issues. When I turn my Raspberry Pi off, the LEDs stay on. Sometimes it shuts down with the lights, it is completely random. Any idea why?

          • Jacek

            Hi, yes, there is new version of hyperion there. I will work on turning off the leds when shutting down openelec. I saw that ‘issue’ but haven’t had time to fix this yet. I will update it soon,

          • Cláudio Castro

            Nice! Will be looking forward to that! Thanks for your quick reply! Always on top of things! ;)

          • Cláudio Castro

            Hi Jacek, I think I found a solution for that issue. Just change the stop section by the initscript under /hyperion/bin/hyperion.init.sh to the following:
            stop)
            if [ -f $PIDFILE ]
            then
            printf “%sn” “Set LEDs off”
            hyperion-remote -c black
            sleep 1
            printf “%-50s” “Stopping $NAME”
            PID=cat $PIDFILE
            cd $DAEMON_PATH
            if [ -f $PIDFILE ]; then
            kill -HUP $PID
            printf “%sn” “Ok”
            rm -f $PIDFILE
            else
            printf “%sn” “pidfile not found”
            fi
            else
            printf “%-50sn” “No PID file $NAME not running?”
            fi
            ;;

          • Jacek

            Thanks. I will give it a try

          • Jacek

            Did you create hyperion.ini.sh file?

          • Cláudio Castro

            No, it was already inside that folder. I just had to change the Stop section as I wrote above. I’ve been testing it and so far, it seems to have solved that issue.

          • Jacek

            Was that on openelec?

          • Cláudio Castro

            Yeah, why do you ask? Take a look at this screenshot.

          • Cláudio Castro

            Hi Jacek, any news on the code change? Is the hyperion folder not suposed to show up like this on Openelec?

          • Jacek

            FInally I had some time to look into this. I have slightly changed the code that you pasted and it works now:

            stop)
            if [ -f $PIDFILE ]
            then
            /storage/hyperion/bin/hyperion-remote.sh -c black
            sleep 1
            printf “%-50s” “Stopping $NAME”
            PID=cat $PIDFILE
            cd $DAEMON_PATH
            if [ -f $PIDFILE ]; then
            kill -HUP $PID
            printf “%sn” “Ok”
            rm -f $PIDFILE
            else
            printf “%sn” “pidfile not found”
            fi
            else
            printf “%-50sn” “No PID file $NAME not running?”
            fi

            ;;

          • Cláudio Castro

            Cool! I’m happy it worked! By the way, any idea about why doesn’t Openelec run autostart.sh everytime it starts? I made a script for launching hyperion and turning the grabber on and off, so that is not such a big issue for me, but I bet it is for many other users. I am also happy to share the code with you, if you want.

  • Samuel Torres

    Hi, I want to buy rasberry pi2 and lightberry do I need something to install my ps4

    • Jacek

      Yes, you will also need HDMI Premium kit to have video from PS4 split and delivered to raspberry pi.

  • Cláudio Castro

    Hi guys! Has anybody had any problems with the latest Hyperion version? I opened an issue on Hyperion Github, but had no helpful reply so far(https://github.com/tvdzwan/hyperion/issues/561). Here is my issue:

    I have a Raspi 2 with a Lightberry kit for the past two years and a Fushicai USBTV007 grabber, which was working flawlessly until I did a factory reset on my installation and reinstalled the updated Hyperion software. Since then, my grabber simply won’t work.

    The grabber is working, I just took a snapshot of the captured image. Also I have added the enable-spi-overlay.dtb file on the overlays folder and the respective line on config.txt. I also have the dev/video0 file. Also the IP address is correct and the “allow remote control” option is active on Kodi. Lsusb shows the grabber as well.

    Still, when I turn on the grabber I get no lights from the LEDs. They simply turn off after the initial rainbow splash. This was not happening before I updated Hyperion.

    Here is my configuration: http://www.jsoneditoronline.org/?id=8073fcad20710b7cfc86ba7ef96c07f9

    Was there any code change that I am not aware of? Also, how do I access the Hyperion log? And more importantly, how do I fix this?

    • Cláudio Castro

      @disqus_gawBZeon7X:disqus, Penfold and Brindosch from Hyperion helped me solve this issue. My grabber priority was set to 1100, based on the Lightberry config file I had. Hyperion has changed the standard grabber priority to 900 so this one wasn’t working.

      I ended up setting my grabber priority to 950, since 1000 was algo getting me no signal. This issue is now solved but I want to give up a heads up about it.

      Have a nice day!

      • Jacek

        Thanks a lot for sharing!