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.
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.
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.
You need to run under root.
With that error you need to run under root!
In the upcoming release this will be possible using the Qt-Grabber
Das der sich der Starteffekt nicht automatisch beendet ist ein bekanntes Problem und wird im nächsten Release behoben.
Starte mit
"Sudo hyperiond -d &"
dann läuft der Hyperion Daemon auch nach nach dem Schließen des Terminals….
Baumtreter FYI, mit dem nächsten Release kannst Du auch LEDs „blacklisten“. Nur falls Du es ggf.doch noch brauchst.
Siehe auch
See the last post of the following thread
Or search for rainbow …
You need to run Hyperion under root for this LED setup.
Skye You can use Hyperion without external input.
With the setup you have in mind, you can set colors or run build-in effects on your LEDs via Hyperion.
Great, Websockets is a good alternative too.
There you can execute as many commands as you like after opening the websocket.
See the following thread
You need to execute both requests in one context/session.
With curl use the —next option
USB Capture will be available with the next Hyperion release.
You can already test, if you would like…
Install the windows artifact from the following PR:
So should I update `hardwareLedCount` simultaneously with setting the LED layout?
Please do not!
There were multiple problems with the previous approach that the number of LEDs from Lay-out were used, even when the number exceeded the physical number of the LEDS. Therefore, the HwLedCount is now the leading one again. In the coming Ui, the User is forced to have the HwLedCount set and the Ui ensures that the layout will not exceed that number (and yes, the API should check that too and return an error going forward).
Until then please ask the user to have the HwLedcount matching the physical number of LEDs. The layout you create can then be <= HwLedcount.
I ask for here your Support that we do not get inconsistent configs via a „Backdoor “ into the system.
dinvlad From the next Hyperion release onwards, the HWLedcount of an LEDDevice will be leading. Therefore, please take care that you do not configure more LEDs in the layout than configured as per given LED Controller.
You can test against the current Master Branch…
Edit: As you anyway read the config, the HwCount is part of it…