Home Assistant Add-on: Hyperion-NG

Tags: #<Tag:0x00007f739627d5d8>

I’ve created an add on for Hyperion NG located at the repository https://github.com/bradsjm/hassio-addons

Hardware Limitations

I use WLED devices and the Hyperion Android Grabber so do not have any hardware devices connected to Hyperion so I am unable to test what hardware does and does not work from within Home Assistant OS add-on. If you manage to get any hardware devices working please let me know so I can update the documentation.

About Hyperion

Hyperion is an opensource Bias or Ambient Lighting implementation which you might know from TV manufacturers. It supports many LED devices and video grabbers.

4 Likes

Thank you bradsjm for a very useful application. Now about the problems. The container does not start. Here is the error log.

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] done.
[services.d] starting services
[services.d] done.
/run.sh: line 4: /hyperion/hyperiond: cannot execute binary file: Exec format error
[cmd] /run.sh exited 126
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.

hassio runs docker on PI4 on rasbian buster system

Thanks, must be an issue with the multiple architecture builds (Exec format error indicates its the wrong architecture) as the amd64 version I run works fine. I kicked off a rebuild of the containers and I’ll dig up a raspberry pi this weekend to test those builds.

1 Like

@genik I think I have resolved the cross-architecture build issue, could you try removing and re-installing. I just tested it on my Pi 4 and it appears to be working now.

OK will try and come back to you with report

installs and run’s fine on a Nuc HassOS. Although I did not test grabbing and output.

To bad my main Hyperion setup is all direct connect at the moment. I was getting lots packet loss and general wifi interference when using Wled devices. To many Wifi users in my area.

However I may Try, try again.

Thanks for sharing your project.
:+1:

Hyperion starts but reports a mistake and the LED does not work

hyperiond LEDDEVICE : <ERROR> Device disabled, device 'apa102' signals error: 'Failed to open device (/dev/spidev0.0). Error message: No such file or directory'

the file in the directory is present
Earlier the Hyperion was situated and worked in the host system.

Thanks. I’ve added a mapping for that device path to the add-on (/dev/spidev0.0) configuration. I’m not sure if just reloading the repository and restarting will use the new configuration or if it needs to be removed and re-installed to get the update. I’m still new at making add-ons.

something strange is going on. I uninstalled addon-hyperion-ng and now I cannot install. https://github.com/bradsjm/hassio-addons does not appear in the repository

Yes, I can no longer install the addon. Here’s the mistake

20-09-22 17:26:06 INFO (MainThread) [supervisor.store.git] Clone add-on https://github.com/bradsjm/hassio-addons.git repository
20-09-22 17:26:08 WARNING (MainThread) [supervisor.store.data] Can't read /data/addons/git/4c317cbd/addon-hyperion-ng/config.json: does not match regular expression @ data['devices'][0]. Got '/dev/spidev0.0:/dev/spidev0.0'

Ok, I don’t think I had the full syntax required for adding the spidev0 to the config however I just refreshed the repository and installed it and it didn’t complain so I think I might have fixed it!

Oh that would be cool

Thanks Jonathan, now everything works as it should. Using Hyperion is much more convenient.