hyperion NG installation

ben3218 · Sep 7th 2019

Hello,
I have raspberry 3 with ws 2801 led strip and was wondering, would it be possible to install hyperion NG on osmc or openelec operating system?

TPmodding · Sep 8th 2019

yes on osmc

https://github.com/hyperion-pr…ubuntuwin10linuxsubsystem

but as always: .ng is not final, so you have to do it on your own, if you know how to do it...

ben3218 · Sep 8th 2019

Quote from TPmodding

yes on osmc

but as always: .ng is not final, so you have to do it on your own, if you know how to do it...

I have OSMC kodi 17.6 up and running.
Then I used your Hyperion.NG kompilieren und installieren auf einem Raspberry Pi youtube tutorial (I skipped raspbian part).
I did include
sudo apt-get install rbp-userland-dev-osmc ( it seemed important since it mentioned OSMC)

From the looks of it,hyperion ng got installed. I can access configuration menu of hyperion,select controller type etc. But the lights are not responding.
When I putty hyperiond it says :
[hyperiond LEDDEVICE] <ERROR> Failed to open device (/dev/spidev0.0). Error message: No such file or directory
and it keeps repeating :
"No carrier"
"No carrier"
"No carrier"

Could it be I was on the right track? What else do I need to do?

hopfinger · Sep 8th 2019

Quote from ben3218

I have OSMC kodi 17.6 up and running.
Then I used your Hyperion.NG kompilieren und installieren auf einem Raspberry Pi youtube tutorial (I skipped raspbian part).
I did include
sudo apt-get install rbp-userland-dev-osmc ( it seemed important since it mentioned OSMC)

From the looks of it,hyperion ng got installed. I can access configuration menu of hyperion,select controller type etc. But the lights are not responding.
When I putty hyperiond it says :
[hyperiond LEDDEVICE] <ERROR> Failed to open device (/dev/spidev0.0). Error message: No such file or directory
and it keeps repeating :
"No carrier"
"No carrier"
"No carrier"

Could it be I was on the right track? What else do I need to do?

Display More

Do you enabled the SPI Interface with raspi-config?

ben3218 · Sep 8th 2019

Quote from hopfinger

Do you enabled the SPI Interface with raspi-config?

No but, I have made several attempts.
I used code:
sudo raspi-config
which works on raspbian,hoping it would let me in Raspberry Pi Configuration,but it didnt.
I then tried with:
# file in /boot/config.txt, need reboot
and
dtparam=spi=on
which i fount at [MEDIA=gist]moux2003/10bba6c8ccd908e35182[/MEDIA] , those 2 lines went pretty much ignored.
At last I turned on the tv and looked through OSMC setting but havent found anything related to SPI.
That's when I ran out of ideas.

Akriss · Sep 9th 2019

Osmc has a utility within the kodi interface to edit the "config.txt" file and add the needed line.
I haven't ran a osmc Rpi in a wile, but if I remember correctly edited by hand it reverts back, need to use the utility.
the utility was within the "Myosmc" tab, if I remember correctly.

Hope its of help.

ben3218 · Sep 9th 2019

Quote from Akriss

Osmc has a utility within the kodi interface to edit the "config.txt" file and add the needed line.
I haven't ran a osmc Rpi in a wile, but if I remember correctly edited by hand it reverts back, need to use the utility.
the utility was within the "Myosmc" tab, if I remember correctly.

Hope its of help.

Wonderful,I have found it! I have enabled SPI support but I get the same error on putty.
However, there are more options,such as gpio_out_pin (17) and gpio_in_pin (18). My raspberry connects to led strip on pins 19 and 23. Is this something I should alter as well?
And you were right about config.txt editor. It is there. But what is the needed line? The one that I mentioned in my previous reply?

Akriss · Sep 9th 2019

Quote from ben3218

there are more options,such as gpio_out_pin (17) and gpio_in_pin (18)

Are for infrared in/out. Don't need to bother with it as you are not using a infrared receiver of transmitter.

Quote from ben3218

But what is the needed line? The one that I mentioned in my previous reply?

Correct,

Code

dtparam=spi=on

Hope its of help.

Edit: this is a old thread with good tip to try:
https://hyperion-project.org/t…-with-osmc-kodi-16-1.370/

ben3218 · Sep 10th 2019

Quote from Akriss

Osmc has a utility within the kodi interface to edit the "config.txt" file and add the needed line.
I haven't ran a osmc Rpi in a wile, but if I remember correctly edited by hand it reverts back, need to use the utility.
the utility was within the "Myosmc" tab, if I remember correctly.

Hope its of help.

It definitely is of help. Thank you very much.
I did manage to write the code to the config.txt. So the lights are working now! Amazing:omg:! But only after I activate hyperion from my pc. Is there a way to have hyperion start automatically with OSMC?
I did encounter an issue when playing movies with black bar. The tv would be flickering,switching randomly from raspberry's HDMI to "no signal" screen. Activating or deactivating blackbar detection from hyperion setting changes nothing. Selecting "zoom" as a view mode on kodi kind of fixes the issue,but then again limits to only watching zoomed in movies.

Best regards,

Akriss · Sep 10th 2019

Quote from ben3218

Is there a way to have hyperion start automatically with OSMC?

Yes. It's requires a bit of work however.

There is a default service file to start Hyperion.NG located here:
https://github.com/hyperion-pr…/service/hyperion.systemd

And to make use of that file I can only point you to some reading on how to use that file on a linux system.
https://discourse.osmc.tv/t/ho…e-a-service-on-osmc/21873

https://www.devdungeon.com/con…ing-systemd-service-files

Quote from ben3218

The tv would be flickering,switching randomly from raspberry's HDMI to "no signal" screen.

Sorry I've not encountered that before. Is the RPI power supply >= 2.5 amp's ? if not maybe low current on the Rpi.

Hope it of help.

ben3218 · Sep 10th 2019

The power supply is 2.5 amps.
Thanks again,I'll look in to those links.

fir3drag0n · Oct 23rd 2019

If I wnat to start the service, I get the error:

Code

systemctl status hyperion.service
● hyperion.service - Hyperion ambient light systemd service  for user
   Loaded: bad-setting (Reason: Unit hyperion.service has a bad unit file settin
   Active: inactive (dead)


Oct 22 23:47:56 raspberrypi systemd[1]: /etc/systemd/system/hyperion.service:7:
lines 1-5/5 (END)
● hyperion.service - Hyperion ambient light systemd service  for user
   Loaded: bad-setting (Reason: Unit hyperion.service has a bad unit file setting.)
   Active: inactive (dead)


Oct 22 23:47:56 raspberrypi systemd[1]: /etc/systemd/system/hyperion.service:7: Invalid user/group name or numeric ID:

Display More

Akriss · Oct 23rd 2019

The error is clear. "Invalid user/group name or numeric ID:"

You need to change the "user" and "group" in hyperion.service to your user name.

Can you log in via ssh?

If yes then use that log in name for hyperion.service file's "user" and "group" line.

Hope it's of help.

fir3drag0n · Oct 23rd 2019

Sorry, but where do I edit the group here?

Akriss · Oct 23rd 2019

If the service file only has a reference to "user" just change that.
The "group" can be omitted.

Hope it's of help.

fir3drag0n · Oct 23rd 2019

Okay, now I get a different message:

Code

Hyperion ambient light systemd service  for user
   Loaded: loaded (/etc/systemd/system/hyperion.service; enabled; vendor preset: en   Active: activating (auto-restart) (Result: exit-code) since Wed 2019-10-23 07:15  Process: 690 ExecStart=/usr/bin/hyperiond (code=exited, status=200/CHDIR)
Main PID: 690 (code=exited, status=200/CHDIR)

Akriss · Oct 23rd 2019

Is there a log from Hyperion from after trying the service start up?
Can you post the log?
It seems as if Hyperion is having a problem that the log may have an answer for.

fir3drag0n · Oct 24th 2019

I had different paths for systemd file. It works now!

fir3drag0n · Feb 22nd 2020

I just wanted to update hyperion ng, but I get the error:

Code

-- Using protobuf compiler: /home/pi/hyperion/build/bin/protoc
-- Found PythonLibs: /usr/lib/arm-linux-gnueabihf/libpython3.7m.so (found suitable version "3.7.3", minimum required is "3.5")
-- Found PythonLibs: /usr/lib/arm-linux-gnueabihf/libpython3.7m.so (found suitable version "3.7.3", minimum required is "3.4")
CMake Error at /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the
  system variable OPENSSL_ROOT_DIR (missing: OPENSSL_CRYPTO_LIBRARY
  OPENSSL_INCLUDE_DIR) (Required is at least version "1.0.0")
Call Stack (most recent call first):
  /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.13/Modules/FindOpenSSL.cmake:412 (find_package_handle_standard_args)
  src/hyperiond/CMakeLists.txt:68 (find_package)
  src/hyperiond/CMakeLists.txt:260 (InstallDependencies)




-- Configuring incomplete, errors occurred!
See also "/home/pi/hyperion/build/CMakeFiles/CMakeOutput.log".
See also "/home/pi/hyperion/build/CMakeFiles/CMakeError.log".
make[2]: *** [src/hyperiond/CMakeFiles/hyperiond.dir/build.make:191: bin/hyperiond] Error 1
make[2]: *** Deleting file 'bin/hyperiond'
make[1]: *** [CMakeFiles/Makefile2:2991: src/hyperiond/CMakeFiles/hyperiond.dir/all] Error 2
make: *** [Makefile:152: all] Error 2

Display More

C

Determining if the pthread_create exist failed with the following output:
Change Dir: /home/pi/hyperion/build/CMakeFiles/CMakeTmp


Run Build Command:"/usr/bin/make" "cmTC_8655e/fast"
/usr/bin/make -f CMakeFiles/cmTC_8655e.dir/build.make CMakeFiles/cmTC_8655e.dir/build
make[1]: Entering directory '/home/pi/hyperion/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_8655e.dir/CheckSymbolExists.c.o
/usr/bin/cc   -Wno-psabi    -o CMakeFiles/cmTC_8655e.dir/CheckSymbolExists.c.o   -c /home/pi/hyperion/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c
Linking C executable cmTC_8655e
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_8655e.dir/link.txt --verbose=1
/usr/bin/cc  -Wno-psabi     -rdynamic CMakeFiles/cmTC_8655e.dir/CheckSymbolExists.c.o  -o cmTC_8655e
/usr/bin/ld: CMakeFiles/cmTC_8655e.dir/CheckSymbolExists.c.o: in function `main':
CheckSymbolExists.c:(.text+0x38): undefined reference to `pthread_create'
collect2: error: ld returned 1 exit status
make[1]: *** [CMakeFiles/cmTC_8655e.dir/build.make:87: cmTC_8655e] Error 1
make[1]: Leaving directory '/home/pi/hyperion/build/CMakeFiles/CMakeTmp'
make: *** [Makefile:121: cmTC_8655e/fast] Error 2


File /home/pi/hyperion/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
/* */
#include <pthread.h>


int main(int argc, char** argv)
{
  (void)argv;
#ifndef pthread_create
  return ((int*)(&pthread_create))[argc];
#else
  (void)argc;
  return 0;
#endif
}


Determining if the function pthread_create exists in the pthreads failed with the following output:
Change Dir: /home/pi/hyperion/build/CMakeFiles/CMakeTmp


Run Build Command:"/usr/bin/make" "cmTC_5526e/fast"
/usr/bin/make -f CMakeFiles/cmTC_5526e.dir/build.make CMakeFiles/cmTC_5526e.dir/build
make[1]: Entering directory '/home/pi/hyperion/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_5526e.dir/CheckFunctionExists.c.o
/usr/bin/cc   -Wno-psabi -DCHECK_FUNCTION_EXISTS=pthread_create   -o CMakeFiles/cmTC_5526e.dir/CheckFunctionExists.c.o   -c /usr/share/cmake-3.13/Modules/CheckFunctionExists.c
Linking C executable cmTC_5526e
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_5526e.dir/link.txt --verbose=1
/usr/bin/cc  -Wno-psabi -DCHECK_FUNCTION_EXISTS=pthread_create    -rdynamic CMakeFiles/cmTC_5526e.dir/CheckFunctionExists.c.o  -o cmTC_5526e -lpthreads
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
make[1]: *** [CMakeFiles/cmTC_5526e.dir/build.make:87: cmTC_5526e] Error 1
make[1]: Leaving directory '/home/pi/hyperion/build/CMakeFiles/CMakeTmp'
make: *** [Makefile:121: cmTC_5526e/fast] Error 2

Display More

What can I do?

Paulchen-Panther · Feb 22nd 2020

Alpha releases available from the Hyperion release page

Participate now!