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.
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.
@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.
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.
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
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!
@bradsjm This is amazing! Works perfectly! Thank you!
Just to let you know, I’m using ws2801 and video signal comes from USB grabber.
Only thing I had to do is enable spi manually on hassio to control led lights (login as root and uncommented this line dtparam=spi=on under /mnt/boot/config.txt).
I’m using raspberry pi3 (but i’ll move soon to pi4)
Fantastic stuff, thanks for this @bradsjm
Only recently started messing with hyperion, and this saves me needing to have a dedicated raspberry pi on the go.
All working perfectly here for me, on a Pi 3b using a usb grabber for image capture & WLED devices.
Delighted!
Update:
USB grabber works perfectly but causes bluetooth issues for me on pi3.
Have checked by running without the addon, with the addon default settings and with the addon with usb grabber active.
Bluetooth fails shortly after activating usb capture.
Get multiple Bluetooth: hci0: Frame reassembly failed (-84) errors under supervisor -> host logs.
Googling the error got me some leads that would indicate lowering the baud rate would fix this for me, but I’m not sure how to go about that under hassio… Any suggestions?
I’m aware this may be a host issue rather than the addon, and that you’re not using usb capture yourself. Just posting here in case anyone else has encountered the issue or has any tips.
Edit: If it is relevant I am also seeing mutliple logs along the lines of retire_capture_urb: XXX callbacks suppressed
Glad to hear it mostly works for you, the addon as you thought has no settings for bluetooth, there is simply an option for addons to access bluetooth or not (yes/no)
