The config for pi should be in the pi user‘s home Directory. Just look for the .hyperion/db directory. You can copy the db file to the root users director, same place.
Suggest you backup the current dB file for root before…
Posts by Lord-Grey
-
-
With WLED should should not run Hyperion under root (but you could).
2. You can configure the WLEDs hostname rather than the IP. Nevertheless, having a static IP on top, is helpful too.
-
After you plugged in your grabber, there is not need to reboot. Just refresh the browser page.
This triggers the discovery of the grabber.
Can you post the output of:v4l2-ctl --all
Just too see what other capabilities your grabber has which are missing from the selection.... -
smoga If you do not see all configuration options expected, have you switch to settings level "Expert"?
-
Most of the users face the issue that they running ws281x LEDs but that by default do not work. The reason is that for ws281x LEDs Hyperion needs to be run under root.
For security reasons Hyperion does not longer run under root per default on a Hyperbian image.
Before you go through the burden of compiling yourself or install other images, I would suggest you first check why Hyperion alpha10 is not working on your case.
That will
a) Help all of us, if is a general Problem
b) Save you a good effort of time…
PS: If you see an „mmap“ Error in your log, it is the „run under root“ problem.
The solution is already described in the forum.
-
james2brite May I ask you to open an issue on Hyperion‘s GitHub and describe step by step how to create the issue, please?
Additional screenshots might be helpful too.
-
Quote
"hardware led count" field wont let me input anything when Use Hue Entertainment API checked. Any suggestions?"
Hardware led count is resolved automatically, if everything is configured correctly.
I just retested and I have to admit that my previous statement that you can configure without the wizard seems to be wrong.
Given there is a page error, the page does not work as expected..... -
Maybe I was not clear. It was fixed after release alpha10.
You could load the artifact from the given PR, if you would want to test it.
-
@irlinnel
, I had assumed that any stuff like "run at root privilege" would have already been set in the disk image.
With the latest HyperBian images, Hyperion is not longer run under root per default to do justice to security.
Nevertheless, for one LEDs this is still required. Here you have the option to change it yourself.
-
wylekyot This is a known issue and was already fixed. See https://github.com/hyperion-project/hyperion.ng/issues/1276
-
slowie I guess what you are referring to.
In Alpha 9 and before you e.g. see the background effect in the priority list while it is „overlaid“ with a source of higher prioritiy.
Unfortunately, the effect still runs in the background and consumes resources unnecessarily.
With the latest release an effect getting out of scope is stopped rather eating resources.
Edit: if we are talking about background effect, it will restart automatically, if no other priority is there.
-
nikolas_3 There is currently not native IP-WebCam support in Hyperion.
If you run Hyperion on a Unix based device, you might search, if it is possible to stream Webcam output into a v4l2-loopback device.
Alternatively, someone might build an adapter turning a WebCam stream into a protobuf or flatbuffer stream hyperion understands.
So a kind of DIY Solution in the spirit of Hyperion…
Happy hearing back, if you found some way.
-
slowie See the Error stated in the log…
You need to run Hyperion under root with this LED type.
LEDDEVICE] (ERROR) Device disabled, device 'ws281x' signals error: 'Failed to open. Error message: mmap() failed'
-
Mr.Shakes You can ran Hyperion on an Desktop image. That is not causing the issue.
-
Connect a WLED your instance on your Hyperion Windows.
Run a 2nd Hyperion on the rpi and forward instance 0 from your Windows Hyperion to the rpi.
Thank should be possible.
But you cannot run WLED on the rpi. -
Use connect your LEDs to an ESP board and run WLED on it (for more details see the WLED page).
You can then stream from Hyperion.ng on Windows to WLED easily.
There is no need for an extra rpi. -
davieboy It depends on your setup... (which you are not outlining. And yes, LibreElec 10 is not working).
In case you e.g. run rpi4 + Raspberry Pi OS with desktop you can use the Qt Grabber.
Just start hyperiond with the "--desktop" option and you have the screen grabbed (see screenshot for your reference below).
Suggest you try starting via command line first.... in a terminal session opened from the desktop -
NeeeeB I confirm that is an issue.
I am running three instances, but only instances 2 and three are turning off....
-
NeeeeB Thanks for reporting. It indeed looks like a bug.
Did you identify the issue on alpha9 or alpha10?
Would you mind opening an issue on GitHub that we can plan for it?
https://github.com/hyperion-project/hyperion.ng/issues -
The picture shows that you installed as root.
I am asking that after installation you need to change that hyperion runs under root.
The error shows that the user that runs Hyperion (after installation) has not the right permissions. This is unfortunately required for the LED type you are using. Other type work without running under root.
Hoping that clarifies.
Edit: Look into the forum, there are different articles describing what needs to be updated.
