Installation on RPi with OpenELEC - ntim/hyperion GitHub Wiki

Installation on the RPI running OpenELEC is a bit difficult due to the dependencies required by Hyperion. In order to make installation possible, the missing dependencies have been taken from a RPi running Raspbmc. Although things seem to be working for now (OpenELEC 3.2.4), updates of OpenELEC may break the installation in the future or require an updated set of dependencies.

Deployment

The installation of hyperion consists of several steps:

installation of the hyperiond and hyperion-remote (default installed to '/storage/hyperion/bin').
configuration file for the hyperion daemon (default file '/storage/.config/hyperion.config.json').
add hyperiond as a startup service (Startup line is added to '/storage/.config/autostart.sh').

All these steps are wrapped into a single installation script available from the github repository (bin/install_hyperion.sh). This will download and perform the above mentioned steps.

curl -L --output install_hyperion.sh --get https://raw.githubusercontent.com/tvdzwan/hyperion/master/bin/install_hyperion.sh
sh ./install_hyperion.sh

Note that the installed configuration file may need some changes dependent on your hardware setup. See the configuration page for more information. When you create a configuration file for your setup be sure to update the path to the effects to '/storage/hyperion/effects' as this path defaults to the normal installation location on other platforms.

After updating the config file, restart the RPi to enable Hyperion.

Usage

Using Hyperion is is the same as on other distributions with a small but important exception. The Hyperion executables can not be used directly, because they are not available on the path. Instead two scripts are available (/storage/hyperion/bin/hyperiond.sh and /storage/hyperion/bin/hyperion-remote.sh) which set the the path of the dependencies prior to execution.

You can restart Hyperion with these commands:

killall hyperiond
/storage/hyperion/bin/hyperiond.sh /storage/.config/hyperion.config.json </dev/null >/dev/null 2>&1 &

Test installation

Test the installation by checking if data can be send to Hyperion. The usage is a bit different because you need to start the .sh file instead of just typing "hyperion-remote". For example try setting all leds to red for 5 seconds. You can also check if the effect path is correct: ``` /storage/hyperion/bin/hyperion-remote.sh --priority 50 --color red --duration 5000 /storage/hyperion/bin/hyperion-remote.sh --effect "Rainbow swirl fast" --duration 3000 ```