wesleymc21 If the LED switch does not stay on, I suggest you lock in the Hyperion Log ("System->Log")
and see what the error reported is....
Most likely its is
LEDDEVICE] (ERROR) Device disabled, device 'ws281x' signals error: 'Failed to open. Error message: mmap() failed'
Then you need to run Hyperion under root, given your setup and LED type used...
kart-able The latest error is due to the fact, that the grabber cannot be found at the configured place...
First, I would suggest you check, if the LEDs are working e.g. setting a Color-Effect via the remote-Control.
If the LEDs work in general, you then focus on the grabber piece. Otherwise address that the LED- issue first.
Track down things in a structured manner and not just look, if LEDs are on or not....
iJokerboy Please see the following PR https://github.com/hyperion-project/hyperion.ng/pull/1236
Note: I had to correct some records where variable content is injected, e. "$1" must stay as as and no blank must be added.
Please go through the UI to check, if everything is all accurate.
LEDDEVICE] (ERROR) Device disabled, device 'ws281x' signals error: 'Failed to open. Error message: mmap() failed'
You need to run Hyperion under root, given your setup and LED type used...
iJokerboy Thanks for your contribution. Let me have a look and have this integrated for the next release.
Bourner Kannst Du mal die Zeile, wie im dritten Post dieses Thread angegeben hinzufügen und testen?
siehe RE: WLED ist beim starten immer aus
Ist ein bekanntes Problem. WLED wird schon geöffnet, bevor das Netzwerk da ist.
Als Workaround kannst Du dem rpi eine statische IP geben. Das hat bei einigen Usern geholfen, dass das Netzwerk schneller da ist.
Just create two instances in hyperion, one for left, one for right and define the corresponding Ledlayout per each.
You can freely define which areas are mapped to the individual LEDs.
Find more details here.
Sample:
If you have two LEDs, one should use the full screen the other a part, you would configure as below. For many LEDs, you would repeat the respective definition.
Note: You need to have settings level minimum "advanced" to see the configuration elements.
[
{
"hmax": 1,
"hmin": 0.85,
"name": "LED with partial picture",
"vmax": 0.75,
"vmin": 0.25
},
{
"hmax": 1,
"hmin": 0,
"name": "LED with whole picture",
"vmax": 1,
"vmin": 0
}
]Und wie wäre es mir CEC Erkennung? Konfigurierst Du beim externen Grabber in Hyperion?
alexwaibel Sure, and sorry I diverted from answering the error itself...
The error is showing to a WS-socket protocol problem.
Lately, I identified and fixed a bug related to fragmented WS frames:
https://github.com/hyperion-pr…2354652d4471ff3452ef4fd19
Not sure, why a layout save resulted into this error which I have not seen before.
The current master already includes that fix.
In case you would be able to e.g. install a current PR like PR1164, you could check, if it would solve the issue on your end with the next release (plus giving us the confidence that the bug was fixed, too).
Starte das Programm zum Flashen mal als Administrator...
Unter LibreElec kannst Du keine Pakete (deb) installieren und auch nicht kompilieren.
Falls Docker unter LE geht, kannst Du versuchen pi-blaster darin zu installieren.
Wie, steht im Link den ich dir gegeben habe.
Alternativ, kannst Du auch einen zweiten rpi verwenden mit rpi-OS und dort installieren (Siehe mein Link). Dort installiert Du auch hyperion und streamst zum LE Hyperion.
Siehe auch 202 Led APA102 + 3 Zone pi-blaster
alexwaibel Unfortunately, I cannot reproduce the issue.
Nevertheless, one thing to note, if you use an adalight device, you need to pass the device to the docker.
But you might have already considered it. The above is not too clear how you started the docker...
docker run --device=/dev/ttyACM0 -d -v /home/thomas/hyperion.ng-docker:/root/.hyperion --name="Hyperion" --network host sirfragalot/hyperion.ng:2.0.0-alpha.9-x86_64
or you expose all devices via
-v /dev:/dev
Im UI unter System->Log bzw. Protokoll
Was sagt das Hyperion log dazu?
pi-Blaster findest Du hier: https://github.com/sarfata/pi-blaster
Du bekommst ihn allerdings nicht einfach über apt installiert.
Ich weiß nicht warum Du auf pi-Balster gekommen bist?
Hyperion unterstützt SPI und PWM Devices auch direkt.
Für PWM benutzt den den WS281X Controller type in Hyperion. Hier muss Hyperion allerdings unter root laufen.
Für SPI, die mit SPI....
Schau mal im Forum. dazu gibt es eine ganze Reihe von Posts.
Da Du über pi-Blaster gehen willst, hast Du pi-Blaster auch installiert und konfiguriert?
Was sagt das Hyperion log?
Seems there are still misalignments with the latest mbedtls library.
The mbedtls library has now been temporarily resetted to a previous version.
Do a pull from the master and compile again....
Just for completeness sake...
You can also delete the database starting hyperiond.exe with "---deleteDatabase"
hyperiond.exe --deleteDatabase
For other options do
hyperiond.exe -h
