OSMC and Hyperion


#182

So i almost read the whole thread but i have still a question… :slight_smile:

Do i still need a raspberry pi to set up the hyperion “thing” if i use a phlips hue LED-strip with bridge?


#183

“still need” implies you have a working solution. depending on your solution you will not. I have no experience with HUE bridge but I suspect this is nextwork connected? So no need to keep the RPI. You can use the Vero for that.


#184

No, i have nothing working right now, just wanted to know.
Yes the bridge it is network connected and controlls the Lamps.

But i think my skills are too low to install that by my own, if theres more to it than copy paste some scripts to the vero…


#185

Depends but there are some caveats.

I have some pre-compiled packages so you can you those.

As for configuring the Hue bridge. No experience with them so you’re on your own unless you find someone with a working config. Unfortunatly hyperion is not plug-and-play.
The AML-grabber used to capture the screen causing playback issues for me. The way the grabber in hyperion works it disabled HW-accelleration as reported a bit higher up this thread.


#186

Thanks to @hissingshark I managed to get Hyperion installed on my Vero4k.
I got my arduino attached with LEDStream compiled on it, powering WS2801 LEDs.

When I want to start the Hyperon-Daemon I get this status response:

osmc@Vero4k:/etc/hyperion$ sudo systemctl status hyperion.service
* hyperion.service - Hyperion Systemd service
   Loaded: loaded (/etc/systemd/system/hyperion.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2018-01-10 19:20:45 CET; 5s ago
  Process: 3978 ExecStart=/usr/bin/hyperiond /etc/hyperion/hyperion.config.json (code=exited, status=127)
 Main PID: 3978 (code=exited, status=127)

Jan 10 19:20:45 Vero4k systemd[1]: hyperion.service: Failed with result 'exit-code'.
Jan 10 19:20:45 Vero4k systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
Jan 10 19:20:45 Vero4k systemd[1]: Stopped Hyperion Systemd service.
Jan 10 19:20:45 Vero4k systemd[1]: hyperion.service: Start request repeated too quickly.
Jan 10 19:20:45 Vero4k systemd[1]: Failed to start Hyperion Systemd service.
Jan 10 19:20:45 Vero4k systemd[1]: hyperion.service: Unit entered failed state.
Jan 10 19:20:45 Vero4k systemd[1]: hyperion.service: Failed with result 'exit-code'.

Any Idea where this comes from?
Also I’m not quite sure what to put into my “Output” field in the config file…
After a little research with lsusb I found out that the arduino is connected via /dev/bus/usb/001/002. I guess this is the wrong input for the “Output” field…?


#187

Launch hyperiond (as root) from cli in stead of via the service.

/usr/bin/hyperiond /etc/hyperion/hyperion.config.json

See what error you get.


Boblight on a Vero 4K
#188

Sorry to hear you’re having problems here. Could you also check:
ls -l /usr/bin | grep hyperion

Just to make sure we’re good to launch.


#189

Use the installer @hissingshark provided a little earlier in this thread to install Hyperion on OSMC.

I’m also using hyperion with Hue, and you don’t need any additional hardware. On the Hyperion wiki there’s a guide on how to set up Hue. To create a good config.json you can use HyperCon, as the example in the guide is outdated. You can also use HyperCon to finetune your color settings.

Make sure you’re using amlgrabber and not framegrabber in your config.json. You can just change the name. The amlgrabber only works with video, for the rest, like images, you still need to use framegrabber.

I’ve not used hyperion for an entire movie, but in testing I’ve only noticed some slight audio sync issues while using amlgrabber, but as far as I recall that resolved itself.

If you feel the lights start to lag too much, there’s always a slight delay, then lower the frequency. don’t forget the one on the smoothing effect.

Here are the relevant parts of my config.json:

    // DEVICE CONFIGURATION 
	"device" :
	{
		"name"       : "Vero4K",
		"type"       : "philipshue",
		"output"     : "192.168.178.81",
		"transitiontime"     : 1,
		"switchOffOnBlack"     : false,
		"username"     : "*********************************",
		"colorOrder" : "rgb",
		"lightIds" : [2,3,6]
	},

	// SMOOTHING CONFIG
		"smoothing" :
		{
			"type"            : "linear",
			"time_ms"         : 100,
			"updateFrequency" : 6.0000,
			"updateDelay"     : 0
		}
	},

	// FRAME GRABBER CONFIG
	"amlgrabber" : 
	{
		"width" : 64,
		"height" : 64,
		"frequency_Hz" : 3.0,
		"priority" : 890
	},

You might also want to read my other posts in this thread as I encountered similar issues and they might tell you how to resolve them. (they’re all near the bottom)


#190
osmc@Vero4k:~$ ls -l /usr/bin | grep hyperion
-rwxr-xr-x  1 root root    993264 Jan 10 18:46 hyperion-aml
-rwxr-xr-x  1 root root    993948 Jan 10 18:46 hyperion-framebuffer
-rwxr-xr-x  1 root root    259204 Jan 10 18:46 hyperion-remote
-rwxr-xr-x  1 root root   1047012 Jan 10 18:46 hyperion-v4l2
-rwxr-xr-x  1 root root   1794816 Jan 10 18:46 hyperiond

This looks fine, everything has root.

When I tried to execute
/usr/bin/hyperiond /etc/hyperion/hyperion.config.json

I encountered this one:
/usr/bin/hyperiond: error while loading shared libraries: libpython3.4m.so.1.0: cannot open shared object file: No such file or directory

I already googled a bit and found out some python depency is missing there.

sudo apt-get install -y python3-pip
sudo apt-get install build-essential libssl-dev libffi-dev python-dev

(https://www.digitalocean.com/community/tutorials/how-to-install-python-3-and-set-up-a-local-programming-environment-on-debian-8)
Didn’t do the trick…can someone advice me?


#191

Have you just applied the January update by any chance? That’s just packed up my installation too.
libpython3.4 is no longer available. Now it’s on to 3.5, so we’ll need to rebuild again against that.

I’ll test it out, update the repo and report back.


#192

I reinstalled my Vero4k yesterday with the official tutorial because I fumbled around with boblight first (Boblight on a Vero 4K) and i didn’t want any overlaps with hyperion.
I ran the update in MyOSMC but, if I recall it right, there was no update available.

Thanks in advance! :slight_smile:


#193

I’m working remotely but that seems to have it fixed. Glad that’s all that broke! (so far as we know)

Repo won’t be fully updated until tonight.


#194

Thanks so much!
When the repo is updated I deinstall the current Vero4K folder and start from zero.

I’m still unsure what “output” i should use…


#195

I have the same configuration: Vero4k+arduino+ws2801 and my config file header looks like that:

	// DEVICE CONFIGURATION 
	"device" :
	{
		"name"       : "OSMC",
		"type"       : "adalight",
		"output"     : "/dev/ttyACM0",
		"rate"     : 115200,
		"colorOrder" : "rgb"
	},

The last update broke my hyperion installation due to the python dependencies. I’m waiting for the @hissingshark repo update to reinstall. Thank you man!


#196

Thanks for your advice!

Will try it tonight when the repo is updated.

Edit:

On behalf of everyone coming here for a solution: @Vince35 , you could edit your first post with the solution?


#197

Reinstalled from Repo 5 minutes ago:

osmc@Vero4k:~/hyperion-vero4k$ sudo /usr/bin/hyperiond /etc/hyperion/hyperion.config.json
/usr/bin/hyperiond: error while loading shared libraries: libpython3.4m.so.1.0: cannot open shared object file: No such file or directory

weird…

Any thoughts?

EDIT:

Now it works…I reinstalled with binaries and after the execute command leds flashed…really weird ! :stuck_out_tongue:
Now onto the config!


#198

Yeah, should be all good now.


#199

i get this…

 hyperion.service - Hyperion Systemd service
   Loaded: loaded (/etc/systemd/system/hyperion.service; enabled; vendor preset:
   Active: failed (Result: exit-code) since Thu 2018-01-11 19:56:14 CET; 11s ago
  Process: 5736 ExecStart=/usr/bin/hyperiond /etc/hyperion/hyperion.config.json
 Main PID: 5736 (code=exited, status=203/EXEC)

Jan 11 19:56:13 Vero4k systemd[1]: hyperion.service: Failed with result 'exit-co
Jan 11 19:56:14 Vero4k systemd[1]: hyperion.service: Service hold-off time over,
Jan 11 19:56:14 Vero4k systemd[1]: Stopped Hyperion Systemd service.
Jan 11 19:56:14 Vero4k systemd[1]: hyperion.service: Start request repeated too
Jan 11 19:56:14 Vero4k systemd[1]: Failed to start Hyperion Systemd service.
Jan 11 19:56:14 Vero4k systemd[1]: hyperion.service: Unit entered failed state.
Jan 11 19:56:14 Vero4k systemd[1]: hyperion.service: Failed with result 'exit-co

#200

What gives you this?

  1. Is it my repo?
  2. If so, when did you download it?
  3. And was it working before?
  4. Have you installed the January OSMC update yet?

What is the output of:
/usr/bin/hyperiond /etc/hyperion/hyperion.config.json
and
ls -l /usr/bin | grep hyperion


#201

Sorry :slight_smile:

sudo systemctl status hyperion.service gave me this output…

  1. Yes

  2. about 30mins ago

  3. No just installed it the firt time…

  4. I have 2017.12-1 i think this is the newest official release right?

    /usr/bin/hyperiond /etc/hyperion/hyperion.config.json
    gives me:
    -bash: /usr/bin/hyperiond: No such file or directory

and

ls -l /usr/bin | grep hyperion gives me nothing

hmm am i missing something? :blush: