Ändere die Priorität.
Die kleinere Prio „gewinnt“ und wird automatisch selektiert.
Posts by Lord-Grey
-
-
i can't use that code to update from 2.0.11 to 2.0.13 ? Can you tell me why or give me a way i can do it?
You can try,
I recall a problem that 2.0.11 did not do a proper clean-up..., but that might have been to local installs...
Maybe you uninstall 2.011 and then start with a fresh apt install... -
@Matrover & AbleWorker Hyperion's APT repository has been fixed and HyperBian should now be on version 2.0.13
Note: In case you already running HyperBian with 2.0.12 and only want updating Hyperion,
you could do a
Code# Update your local package index and install Hyperion: sudo apt-get update && sudo apt-get install hyperion
For previous version it is not recommended. -
There is currently a problem. We are looking into it.
The default "raspberry" password was not working.
Did you try typing in the password with an English keyboard in mind? E.g. for a German keyboard y and z are switched…
-
Would need to check this.
Was the first time doing a Hyperion release and expected same as you that Hyperbian is updated the same…
-
Am besten exportiert Du auf jeden Fall vorher Deinen Konfiguration. Wenn Du mehrere Instanzen hast, leider für jede separat.
Dann wie vorher installieren.
-
pho08 Thanks for sharing!
-
No. You can change the code that checks for an already running instance... and need to ensure that alls ports are not overlapping during configuration...
-
Wir planen demnächst mal wieder ein Release.
Vielleicht magst Du auch solange warten...
-
Execute this command in terminal in case hyperiond is found:
sudo updateHyperionUser -u root
-
der Zusammenhang zwischen zu alter Library und anderem Pi erschließt sich mir noch nicht ganz.
Die ws821x Library checkt, auf welcher Hardware Du läufst, da das ws821x Processing sehr hardwarenah ist.
Die Library "whitelisted" die unterstützte Hardware.
Darum siehst Du den Fehler, wenn Du die Hardware tauschst. -
Ist an Hyperion diesbezüglich irgendwas geändert worden vor kurzem?
Ja. Im Nightly Build wird immer die neuste ws281x Library eingebunden.
Hatte den Strip ja schon am laufen letzte Woche und hab auch nur das normale HyperBian hier aus der Dokumentation verwendet.
Da Du den PI gewechselt hast, kommt die Fehlermeldung.
Der Fehler wird durch die Hardware/Library getriggert....es ist kein Hyperion Problem.
Du könntest HyperBian mit dem Nightly Build aktualisieren... -
Der Fehler bedeutet, dass die in Hyperion 2.0.12 enthaltene ws281x Library Deine Hardware nicht unterstützt.
Du kannst Dir den Nightly Build installieren (https://apt.hyperion-project.org/#nightly)
oder auf das nächste Release warten... -
There was a minimum and maximum with 2.0.12 before, but in the process of capability alignment, I removed those too. I can add those back, if there is a real benefit…
PS: No Problem on the Yeelight. I can follow the rationale. They are not really designed for this use case…
-
pho08 The max brightness is influenced by the brightness Factor:
color.bri = (qMin((double)1.0, _brightnessFactor * qMax((double)0, color.bri)));
It ensures that brightness is not just capped, but it gives you a maximum range.
e.g. BightnessFactor = 0.8 -> maxBrightness 80% -
totol123 Have you had a look at the Network configuration?
Maybe you share what is configured now?
And it of course depend how you trigger your API calls.
In Case you use a WebSocket, you would not have a CORS issue.
-
One thing I am noticing too is the the "LED Output" button keeps staying in "off"
It is always good to share what is reported in the Log as an Error.
I assume it says that you are running Hyperion not under root which is required for this type of LEDS.
To fix that execute this command in terminal:
sudo updateHyperionUser -u root
-
The plug-in was developed, is provided and was tested for Hyperion.NG.
If you run HyperHDR, please raise your questions with the maintainer of HyperHDR.
-
You need to update to a newer version of the Ws281x Library. Try Hyperion‘s nightly build.
-
Hi Gab1288
a) Can you do anCodels -ltr /dev/*before attaching the adalight device and another time after you have connected it and share the results?
b) You can test, if teh user running Hyperion has the right permissions. Just do aCodeecho Hello > /dev/ttyUSB0Replace ttyUSB0 with the name you found out in a).
Note: Execute the command with the same user hyperiond is running with.
c) In case the OS does not present the vendor-identifiert to Hyperion (i.e. vendor identifier is empty),Hyperion 2.12 does not show the device.
This has be fixed in the latest development version.
