1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

RPi + OSMC Installing Hyperion.ng

Discussion in 'Software Support' started by Braulio, 27 March 2019.

  1. StimpyMGS

    StimpyMGS New Member

    Messages:
    2
    Hardware:
    RPi3
    I would also like some more detailed information on how to install hyperion.ng
    I have trouble getting my sk6812 led strip to work and I've read that the alpha might have better support for it. However, I don't know how to compile and run hyperion.ng. I have found the step-by-step guide.
    Running wget -qN https://raw.github.com/hyperion-project/hyperion.ng/master/bin/scripts/docker-compile.sh && chmod +x *.sh && ./docker-compile.sh -t armv7hf
    doesn't seem to do anything.
     
  2. Paulchen-Panther

    Paulchen-Panther Active Member Developer

    Messages:
    260
  3. Evox

    Evox New Member

    Messages:
    7
    Hardware:
    RPi3
    Hey guys, been using hyperion for a while now but wanna give this hyperion.ng ago. I've looked into this and was able to install it using this "
    wget -qN https://raw.github.com/hyperion-project/hyperion.ng/master/bin/scripts/docker-compile.sh && chmod +x *.sh && ./docker-compile.sh -t rpi-raspbian" it seems as though it completed correctly. It seems to have installed into the /pi/deploy folder but after restarting it doesn't seem to be working. Am I missing a simple step here?

    To get this to work I had to use rasbian stretch (wouldn't work on the latest rasbian for me)

    Also, I'm not trying to hijack this post, just feel like im in a similar situation.
     
    Last edited: 19 July 2019
  4. Paulchen-Panther

    Paulchen-Panther Active Member Developer

    Messages:
    260
  5. Paulchen-Panther

    Paulchen-Panther Active Member Developer

    Messages:
    260
    I will still create a raspbian buster image. thanks for the hint. :thumbsup:
     
  6. Paulchen-Panther

    Paulchen-Panther Active Member Developer

    Messages:
    260
  7. Evox

    Evox New Member

    Messages:
    7
    Hardware:
    RPi3
    Thanks I’m at work currently but will try when I get home. Sorry for all the noob questions I’m not very familiar with Linux.
     
    • Like Like x 1
  8. Evox

    Evox New Member

    Messages:
    7
    Hardware:
    RPi3
    Got it working, Thanks so much Paulchen-Panther. I actually just found the folder clicked on the application and it installed. Seems to be working great. Is there any fix for the flickering lights when the screen goes black. No big deal if not it doesn't really bother me. Really appreciate all the help.
     
  9. bnealon

    bnealon New Member

    Messages:
    17
    Hardware:
    +PhilipsHue
    @Paulchen-Panther i wondered if you could help me out please?

    I've just made a install of raspbian buster on my rpi, compiled latest hyperion.ng with your buster image:
    `wget -qN https://raw.github.com/hyperion-project/hyperion.ng/master/bin/scripts/docker-compile.sh && chmod +x *.sh && ./docker-compile.sh -t rpi-raspbian-buster`

    Then from within the deploy directory i ran:
    `sudo dpkg -i Hyperion.NG-Beta.1.0.0-Linux-rpi.deb`

    I get the following output:

    Code:
    Selecting previously unselected package hyperion.ng-rpi.
    (Reading database ... 99346 files and directories currently installed.)
    Preparing to unpack Hyperion.NG-Beta.1.0.0-Linux-rpi.deb ...
    /var/lib/dpkg/tmp.ci/preinst: 1: /var/lib/dpkg/tmp.ci/preinst: #!/bin/sh: not found
    ---Hyperion ambient light preinst ---
    Unpacking hyperion.ng-rpi (1.0.0) ...
    Setting up hyperion.ng-rpi (1.0.0) ...
    ---Hyperion ambient light postinstall ---
    ---> init deamon: systemd
    Invalid unit name "[email protected]
    pi
    pi.service" was escaped as "[email protected]\x0api\x0api.service" (maybe you should use systemd-escape?)
    Created symlink /etc/systemd/system/multi-user.target.wants/[email protected]\x0api\x0api.service → /etc/systemd/system/[email protected]
    Invalid unit name "[email protected]
    pi
    pi" was escaped as "[email protected]\x0api\x0api" (maybe you should use systemd-escape?)
    Failed to start [email protected]\x0api\x0api.service: Unit [email protected]\x0api\x0api.service has a bad unit file setting.
    See system logs and 'systemctl status [email protected]\x0api\x0api.service' for details.
    ---> Install Hyperion desktop icons
    --> systemctl start hyperiond for user pi pi pi
    -----------------------------------------------------------------------------
    ---> Hyperion has been installed/updated!
    --->
    ---> Hyperion has been installed as service, it will start on each system startup
    ---> For configuration, visit with your browser: 10.26.25.78:8090
    ---> or if already used by another service try: 10.26.25.78:8091
    -----------------------------------------------------------------------------
    Webpage: www.hyperion-project.org
    Wiki: wiki.hyperion-project.org
    Forum: forum.hyperion-project.org
    -----------------------------------------------------------------------------
    As instructed i then run:
    `systemctl status [email protected]\x0api\x0api.service`

    and i get:

    Code:
    systemctl status [email protected]\x0api\x0api.service
    ● [email protected] - Hyperion ambient light systemd service  for user pix0apix0api
       Loaded: loaded (/etc/systemd/system/[email protected]; disabled; vendor preset: enabled)
       Active: activating (auto-restart) (Result: exit-code) since Fri 2019-08-02 16:55:46 BST; 2s ago
      Process: 1917 ExecStart=/usr/bin/hyperiond (code=exited, status=217/USER)
    Main PID: 1917 (code=exited, status=217/USER)
    
    Aug 02 16:55:49 raspberrypi systemd[1]: [email protected]: Service RestartSec=2s expired, scheduling restart.
    Aug 02 16:55:49 raspberrypi systemd[1]: [email protected]: Scheduled restart job, restart counter is at 450.
    Aug 02 16:55:49 raspberrypi systemd[1]: Stopped Hyperion ambient light systemd service  for user pix0apix0api.
    If i restart the service and tail the logs i get:


    Code:
    journalctl -f
    -- Logs begin at Fri 2019-08-02 16:33:30 BST. --
    Aug 02 16:56:29 raspberrypi systemd[1944]: [email protected]: Failed at step USER spawning /usr/bin/hyperiond: No such process
    Aug 02 16:56:29 raspberrypi systemd[1]: [email protected]: Main process exited, code=exited, status=217/USER
    Aug 02 16:56:29 raspberrypi systemd[1]: [email protected]: Failed with result 'exit-code'.
    Aug 02 16:56:30 raspberrypi sudo[1945]:       pi : TTY=pts/0 ; PWD=/home/pi/Hyperion.ng/02.08.19/deploy ; USER=root ; COMMAND=/bin/systemctl restart [email protected]
    Aug 02 16:56:30 raspberrypi sudo[1945]: pam_unix(sudo:session): session opened for user root by pi(uid=0)
    Aug 02 16:56:30 raspberrypi systemd[1]: Stopped Hyperion ambient light systemd service  for user pix0apix0api.
    Aug 02 16:56:30 raspberrypi systemd[1]: [email protected]: Start request repeated too quickly.
    Aug 02 16:56:30 raspberrypi systemd[1]: [email protected]: Failed with result 'exit-code'.
    Aug 02 16:56:30 raspberrypi systemd[1]: Failed to start Hyperion ambient light systemd service  for user pix0apix0api.
    Aug 02 16:56:30 raspberrypi sudo[1945]: pam_unix(sudo:session): session closed for user root

    Any idea what i am doing wrong?
    How come the service is now called '[email protected]\x0api\x0api.service` whereas when i built this back in march this year, it was only `[email protected]\x0api.service`?
    I control my hyperion setup using ssh commands to start/stop the service, so it would be perfect if you knew what the correct commands to start/stop are.

    Do i need to install a config somewhere for this to start maybe?

    Thank you!
     
  10. Paulchen-Panther

    Paulchen-Panther Active Member Developer

    Messages:
    260
    What kind of RPi do you use?
     
  11. bnealon

    bnealon New Member

    Messages:
    17
    Hardware:
    +PhilipsHue
    3 model b+

    Is it a mistake that the service references the pi user twice? I’m SSH’d into the RPi btw when im installing, as the default user ‘pi’. Im not too familiar with services taking usernames in, if i run without a user it complains also.
     
  12. Paulchen-Panther

    Paulchen-Panther Active Member Developer

    Messages:
    260
  13. bnealon

    bnealon New Member

    Messages:
    17
    Hardware:
    +PhilipsHue
    @Paulchen-Panther thanks very much for the build, doesnt seem to have changed much sadly :eek:(

    I made a fresh install of Raspbian Buster, then SSH'd in from another machine as the default user 'Pi' and this was the first thing i did after that:

    Heres my download and install output:

    Code:
    [email protected]:~/Hyperion.ng/03.08.19 $ wget -qN https://github.com/Paulchen-Panther/hyperion.ng/raw/systemctl/Hyperion.NG-Beta.1.0.0-Linux-rpi.deb
    [email protected]:~/Hyperion.ng/03.08.19 $ ls
    Hyperion.NG-Beta.1.0.0-Linux-rpi.deb
    [email protected]:~/Hyperion.ng/03.08.19 $ dpkg -i Hyperion.NG-Beta.1.0.0-Linux-rpi.deb
    dpkg: error: requested operation requires superuser privilege
    [email protected]:~/Hyperion.ng/03.08.19 $ sudo dpkg -i Hyperion.NG-Beta.1.0.0-Linux-rpi.deb
    Selecting previously unselected package hyperion.ng-rpi.
    (Reading database ... 91802 files and directories currently installed.)
    Preparing to unpack Hyperion.NG-Beta.1.0.0-Linux-rpi.deb ...
    /var/lib/dpkg/tmp.ci/preinst: 1: /var/lib/dpkg/tmp.ci/preinst: #!/bin/sh: not found
    ---Hyperion ambient light preinst ---
    Unpacking hyperion.ng-rpi (1.0.0) ...
    dpkg: dependency problems prevent configuration of hyperion.ng-rpi:
    hyperion.ng-rpi depends on libqt5serialport5 (>= 5.5.0); however:
      Package libqt5serialport5 is not installed.
    hyperion.ng-rpi depends on libavahi-compat-libdnssd1 (>= 0.6.31); however:
      Package libavahi-compat-libdnssd1 is not installed.
    hyperion.ng-rpi depends on libpython3.5; however:
      Package libpython3.5 is not installed.
    
    dpkg: error processing package hyperion.ng-rpi (--install):
    dependency problems - leaving unconfigured
    Errors were encountered while processing:
    hyperion.ng-rpi
    [email protected]:~/Hyperion.ng/03.08.19 $ sudo apt-get install -f
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Correcting dependencies... Done
    The following package was automatically installed and is no longer required:
      rpi.gpio-common
    Use 'sudo apt autoremove' to remove it.
    The following additional packages will be installed:
      libavahi-compat-libdnssd1 libpython3.5 libpython3.5-minimal libpython3.5-stdlib libqt5serialport5
    The following NEW packages will be installed:
      libavahi-compat-libdnssd1 libpython3.5 libpython3.5-minimal libpython3.5-stdlib libqt5serialport5
    0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
    1 not fully installed or removed.
    Need to get 3,905 kB of archives.
    After this operation, 17.8 MB of additional disk space will be used.
    Do you want to continue? [Y/n] Y
    Get:1 http://raspbian.raspberrypi.org/raspbian buster/main armhf libqt5serialport5 armhf 5.11.3-2 [31.2 kB]
    Get:2 http://raspbian.raspberrypi.org/raspbian buster/main armhf libavahi-compat-libdnssd1 armhf 0.7-4+b1 [46.4 kB]
    Get:3 http://raspbian.raspberrypi.org/raspbian buster/main armhf libpython3.5-minimal armhf 3.5.4-4 [572 kB]
    Get:4 http://raspbian.raspberrypi.org/raspbian buster/main armhf libpython3.5-stdlib armhf 3.5.4-4 [2,095 kB]
    Get:5 http://raspbian.raspberrypi.org/raspbian buster/main armhf libpython3.5 armhf 3.5.4-4 [1,160 kB]
    Fetched 3,905 kB in 1s (3,652 kB/s)
    Selecting previously unselected package libqt5serialport5:armhf.
    (Reading database ... 91826 files and directories currently installed.)
    Preparing to unpack .../libqt5serialport5_5.11.3-2_armhf.deb ...
    Unpacking libqt5serialport5:armhf (5.11.3-2) ...
    Selecting previously unselected package libavahi-compat-libdnssd1:armhf.
    Preparing to unpack .../libavahi-compat-libdnssd1_0.7-4+b1_armhf.deb ...
    Unpacking libavahi-compat-libdnssd1:armhf (0.7-4+b1) ...
    Selecting previously unselected package libpython3.5-minimal:armhf.
    Preparing to unpack .../libpython3.5-minimal_3.5.4-4_armhf.deb ...
    Unpacking libpython3.5-minimal:armhf (3.5.4-4) ...
    Selecting previously unselected package libpython3.5-stdlib:armhf.
    Preparing to unpack .../libpython3.5-stdlib_3.5.4-4_armhf.deb ...
    Unpacking libpython3.5-stdlib:armhf (3.5.4-4) ...
    Selecting previously unselected package libpython3.5:armhf.
    Preparing to unpack .../libpython3.5_3.5.4-4_armhf.deb ...
    Unpacking libpython3.5:armhf (3.5.4-4) ...
    Setting up libqt5serialport5:armhf (5.11.3-2) ...
    Setting up libavahi-compat-libdnssd1:armhf (0.7-4+b1) ...
    Setting up libpython3.5-minimal:armhf (3.5.4-4) ...
    Setting up libpython3.5-stdlib:armhf (3.5.4-4) ...
    Setting up libpython3.5:armhf (3.5.4-4) ...
    Setting up hyperion.ng-rpi (1.0.0) ...
    ---Hyperion ambient light postinstall ---
    ---> init deamon: systemd
    Invalid unit name "[email protected]
    pi
    pi.service" was escaped as "[email protected]\x0api\x0api.service" (maybe you should use systemd-escape?)
    Created symlink /etc/systemd/system/multi-user.target.wants/[email protected]\x0api\x0api.service → /etc/systemd/system/[email protected]
    Invalid unit name "[email protected]
    pi
    pi" was escaped as "[email protected]\x0api\x0api" (maybe you should use systemd-escape?)
    Failed to start [email protected]\x0api\x0api.service: Unit [email protected]\x0api\x0api.service has a bad unit file setting.
    See system logs and 'systemctl status [email protected]\x0api\x0api.service' for details.
    ---> Install Hyperion desktop icons
    ---> Raspberry Pi found, but SPI is not set, we write "dtparam=spi=on" to /boot/config.txt
    --> systemctl start hyperiond for user pi pi pi
    -----------------------------------------------------------------------------
    ---> Hyperion has been installed/updated!
    --->
    ---> Hyperion has been installed as service, it will start on each system startup
    ---> For configuration, visit with your browser: 192.168.0.6:8090
    ---> or if already used by another service try: 192.168.0.6:8091
    Please reboot your Raspberry Pi, we inserted dtparam=spi=on to /boot/config.txt
    -----------------------------------------------------------------------------
    Webpage: www.hyperion-project.org
    Wiki: wiki.hyperion-project.org
    Forum: forum.hyperion-project.org
    -----------------------------------------------------------------------------
    Processing triggers for libc-bin (2.28-10+rpi1) ...
    [email protected]:~/Hyperion.ng/03.08.19 $ systemctl status [email protected]\x0api\x0api.service
    ● [email protected] - Hyperion ambient light systemd service  for user pix0apix0api
       Loaded: loaded (/etc/systemd/system/[email protected]; disabled; vendor preset: enabled)
       Active: inactive (dead)
    I then restarted the service, and here's the logs. It appears to keep cycling the service due to a failure for user `pix0apix0api`, is this user correct?

    Code:
    Aug 03 20:43:36 raspberrypi systemd[1]: [email protected]: Main process exited, code=exited, status=217/USER
    Aug 03 20:43:36 raspberrypi systemd[1]: [email protected]: Failed with result 'exit-code'.
    Aug 03 20:43:38 raspberrypi systemd[1]: [email protected]: Service RestartSec=2s expired, scheduling restart.
    Aug 03 20:43:38 raspberrypi systemd[1]: [email protected]: Scheduled restart job, restart counter is at 35.
    Aug 03 20:43:38 raspberrypi systemd[1]: Stopped Hyperion ambient light systemd service  for user pix0apix0api.
    Aug 03 20:43:38 raspberrypi systemd[1]: Started Hyperion ambient light systemd service  for user pix0apix0api.
    Aug 03 20:43:38 raspberrypi systemd[1123]: [email protected]: Failed to determine user credentials: No such process
    Aug 03 20:43:38 raspberrypi systemd[1123]: [email protected]: Failed at step USER spawning /usr/bin/hyperiond: No such process
    Aug 03 20:43:38 raspberrypi systemd[1]: [email protected]: Main process exited, code=exited, status=217/USER
    Aug 03 20:43:38 raspberrypi systemd[1]: [email protected]: Failed with result 'exit-code'.
    Aug 03 20:43:41 raspberrypi systemd[1]: [email protected]: Service RestartSec=2s expired, scheduling restart.
    Aug 03 20:43:41 raspberrypi systemd[1]: [email protected]: Scheduled restart job, restart counter is at 36.
    Aug 03 20:43:41 raspberrypi systemd[1]: Stopped Hyperion ambient light systemd service  for user pix0apix0api.
    Aug 03 20:43:41 raspberrypi systemd[1]: Started Hyperion ambient light systemd service  for user pix0apix0api.
    Aug 03 20:43:41 raspberrypi systemd[1124]: [email protected]: Failed to determine user credentials: No such process
    Aug 03 20:43:41 raspberrypi systemd[1124]: [email protected]: Failed at step USER spawning /usr/bin/hyperiond: No such process
    Aug 03 20:43:41 raspberrypi systemd[1]: [email protected]: Main process exited, code=exited, status=217/USER
    Aug 03 20:43:41 raspberrypi systemd[1]: [email protected]: Failed with result 'exit-code'.
    Aug 03 20:43:43 raspberrypi systemd[1]: [email protected]: Service RestartSec=2s expired, scheduling restart.
    Aug 03 20:43:43 raspberrypi systemd[1]: [email protected]: Scheduled restart job, restart counter is at 37.
    Aug 03 20:43:43 raspberrypi systemd[1]: Stopped Hyperion ambient light systemd service  for user pix0apix0api.
    Aug 03 20:43:43 raspberrypi systemd[1]: Started Hyperion ambient light systemd service  for user pix0apix0api.
    Aug 03 20:43:43 raspberrypi systemd[1125]: [email protected]: Failed to determine user credentials: No such process
    Aug 03 20:43:43 raspberrypi systemd[1125]: [email protected]: Failed at step USER spawning /usr/bin/hyperiond: No such process
    Aug 03 20:43:43 raspberrypi systemd[1]: [email protected]: Main process exited, code=exited, status=217/USER
    Aug 03 20:43:43 raspberrypi systemd[1]: [email protected]: Failed with result 'exit-code'.
    Aug 03 20:43:45 raspberrypi systemd[1]: [email protected]: Service RestartSec=2s expired, scheduling restart.
    Aug 03 20:43:45 raspberrypi systemd[1]: [email protected]: Scheduled restart job, restart counter is at 38.
    Aug 03 20:43:45 raspberrypi systemd[1]: Stopped Hyperion ambient light systemd service  for user pix0apix0api.
    Aug 03 20:43:45 raspberrypi systemd[1]: Started Hyperion ambient light systemd service  for user pix0apix0api.
    Aug 03 20:43:45 raspberrypi systemd[1126]: [email protected]: Failed to determine user credentials: No such process
    Aug 03 20:43:45 raspberrypi systemd[1126]: [email protected]: Failed at step USER spawning /usr/bin/hyperiond: No such process
    Aug 03 20:43:45 raspberrypi systemd[1]: [email protected]: Main process exited, code=exited, status=217/USER
    Aug 03 20:43:45 raspberrypi systemd[1]: [email protected]: Failed with result 'exit-code'.
    Aug 03 20:43:47 raspberrypi systemd[1]: [email protected]: Service RestartSec=2s expired, scheduling restart.
    Aug 03 20:43:47 raspberrypi systemd[1]: [email protected]: Scheduled restart job, restart counter is at 39.
    Aug 03 20:43:47 raspberrypi systemd[1]: Stopped Hyperion ambient light systemd service  for user pix0apix0api.
    Aug 03 20:43:47 raspberrypi systemd[1]: Started Hyperion ambient light systemd service  for user pix0apix0api.
    Aug 03 20:43:47 raspberrypi systemd[1127]: [email protected]: Failed to determine user credentials: No such process
    Aug 03 20:43:47 raspberrypi systemd[1127]: [email protected]: Failed at step USER spawning /usr/bin/hyperiond: No such process
    Aug 03 20:43:47 raspberrypi systemd[1]: [email protected]: Main process exited, code=exited, status=217/USER
    Aug 03 20:43:47 raspberrypi systemd[1]: [email protected]: Failed with result 'exit-code'.
    Cheers!