Home Assistant Add-on: Hyperion-NG

Do you know the command?
Tried “Ha Update --version=5.10”, but without success

ha os update --version 5.10

ahh yes this worked. but hyperion still does not work.
I have now:
core-2021.1.1
supervisor-2021.03.4
Home Assistant OS 5.10

Try to delete hyperion.ng and add again, or delete the config file on your hyperion config path.

Made a SU downgrade to 2021.02.1. Hyperion is working now, but the SU sets back to actual Version. I think a restart would crash Hyperion again, lets hope System can stay like that for ever.

Thanks for all the help @isibizi !

On my system everything is updated to the latest version, only the OS is on 5.10. No Problem with reboots.

I’ve just added /dev/mem explicitly to the devices list in the add-on configuration in hopes that this will fix the issue with the newer HA OS.

So there will come an update for Hyperion Add-on or can we do it ourself?

Going into the hyperion device and disabling/enabling remote connectivity fixes the issue. At least for me it did.

where/how to do it? Hyperion web page?

Forked the updated, but still get the 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.
Can't open /dev/mem: Operation not permitted
2021-03-16T22:32:45.438 hyperiond LEDDEVICE    : <ERROR> Device disabled, device 'ws281x' signals error: 'Failed to open. Error message: mmap() failed'
Can't open /dev/mem: Operation not permitted

Correct - hyperion web page:8090

Where there?

ahh ok you mean the Instance. Already tried that, but LED device status is still off.

I had to cycle it on and then off. Then everything began working again. I have not had to downgrade my HassOS, Supervisor or CORE. Running latest versions.

In my frustrations I did operate Hyperion through my HA integrations and forced a solid color to ensure connectivity was still happening. Then I did the above and viola everything was back to normal.

Thanks for the help, but i dont get it to work. What i tried:
-Cycle status in Hyperion Page
-Cycle status via hassio integration
-Downgrade everything possible (HA 5.10, Core 2021.1) / SU not possible to downgrade
-Reinstall Hyperion

This is very frustrating and time intensive…

Edit1:
I got it.
Just add
"privileged": ["SYS_ADMIN","SYS_RAWIO"],
to the Config.json

Edit2: i can now turn it on and off, but the showed colors are random. e.g.: Solid shows different changing colors.

Any ideas? Anybody who has a working solution?

I got myself also some WS2815 and tried to hook them up directly to the GPIO Pins.
I get the following error when I try to use it:

[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.
2021-03-25T00:48:30.178 hyperiond DISPMANXGRAB : <ERROR> Snapshot failed: -1
2021-03-25T00:48:50.318 hyperiond DISPMANXGRAB : <ERROR> Previous line repeats 200 times
2021-03-25T00:49:10.419 hyperiond DISPMANXGRAB : <ERROR> Previous line repeats 200 times
Can't open device file
: Operation not permitted
2021-03-25T00:49:12.430 hyperiond LEDDEVICE    : <ERROR> Device disabled, device 'ws281x' signals error: 'Failed to open. Error message: Failed to create mailbox device'
2021-03-25T00:49:30.518 hyperiond DISPMANXGRAB : <ERROR> Previous line repeats 200 times

Can't open device file happens when I change my device from file to ws281x.
I am using the newest version of Hyperion.ng (Add-on) on my Pi 4 with the following system:

core-2021.3.4
supervisor-2021.03.6
Home Assistant OS 5.12
1 Like

I’m also experiencing a similar issue with the Hyperion NG add-on and have tried the above fixes with no luck… Does anybody else have any idea how to fix this?