"aber mal ließt viel das es noch viele bugs hat."
Du hast zwei Möglichkeiten,
a) weiter lesen (und versuchen eine unsupportete Version zum Laufen zu bringen)
b) Dir selbst ein Bild zu machen und z.B. die Hues auch jetzt per Entertainment API ansprechen zu können (weniger Delays etc.)
Your Call....
Or you load the latest masterbuild from the Hyperion Githib actions.
Hey
ich würde Dir vorschlagen, Du installiert Hyperion.ng, konfigurierst zwei Instanzen per Web-UI und bist fertig....
https://github.com/hyperion-project/hyperion.ng/releases/
Alpha 7 hat aktuell ein paar Probleme, darum starte am besten mit Alpha 6, oder Du baust Dir dem Master selbst. Der enthält die Fixes...
Would you mind either starting hyperion in debug mode (hyperiond -d) or set the log-level to Debug in the UI
and share the log output, please?
In addition, could you please post the output of:
nslookup 192.168.1.120
Yes, your expectation using hostname rather static IP is totally valid.
May I ask you to rename the device to a valid hostname, i.e. without underscore and without dot (unless it is your domain suffix) please
and try again. e.g. "wled-desk".
hostname:
"Each element of the hostname must be from 1 to 63 characters long and the entire hostname, including the dots, can be at most 253 characters long. Valid characters for hostnames are ASCII(7) letters from a to z, the digits from 0 to 9, and the hyphen (-). A hostname may not start with a hyphen."
„However it does not seem to handle hostname properly:„
@electricJP Just for my interest, does is work with the IP-Address?
Hey, is your Hue Bridge supporting the Entertainment-API?
Then you can create an entertainment group and you should not see an lag any longer... You might want to give it a try...
Edit: You should minimum run hyperion.ng alpha 6
Just use the hyperion hue wizard
You need to run hyperion as root with this configuration (device 'ws281x)
Given Jessie is End of Life, you might anyway want upgrading to a new version of the OS with a high likelihood that the library failure will go, too.
@Meph88 Maybe as a start, you might want to share some debug log with us.
As well as a detailed description what you did...
Put Hyperion.ng in debug mode and after the crash, get the log. Following command get the rpi log from the last hour.
sudo journalctl -S -1h
Share the output as a file here (but do not paste the content)
Hint for free: In case the changed configuration stops hyperion from starting, you might delete hyperion‘s configuration database and start new. There is no need to reinstall the whole system...
Hey
"The error message "Bad address" comes from the error code EFAULT, which happens when you pass an address to the kernel which is not a valid virtual address in your process's virtual address space."
Would you be able to compile hyperion yourself that we could test some code changes to ring-fence the problem?
@Meph88 If I got your initial post correctly, it seems that the WLED device works correctly.
The WLED is turned off and on and streaming of data seems to happen.
-> Either the input to the device is wrong (which the grabber problem might indicate) or the WLED is not configured correctly.
I suggest disabling the grabber, but run an effect.
Given a bug in Alpha7, I currently do not recommend testing with a static color until the bug is fixed.
@Meph88 Maybe you disable your Grabber (or Platform Capture) for the time being, just to see, if the active/inactive log lines go away.
Then we can have a look at the other log lines to ring-fence the problem.
Salut!
Vous voudrez peut-être jeter un œil au dernier Hyperion: https://github.com/hyperion-project/hyperion.ng
Désormais, le support natif de Yeelight est disponible.
Vous n'avez pas besoin d'utiliser de logiciel supplémentaire.
D'autres questions à moi s'il vous plaît en anglais ou allemand....
... but a fix will be in place with the next release...
The database is a MySQL one. So you can open and manipulate it with related tools. The config elements are stored in JSON. You should find the dB under the user‘s home directory in „.hyperion/db“.
We are currently looking creating the selection list dynamically from available devices, but that may take a while...
@Paul Barden "but even with hyperion disabled adalight is always connected to the wled instance. When I override the instance I have no ability to power off the light. Do you also have this experience or have you moved back to UDP"
You might want to look at LED Device Features, Fixes and Refactoring development item.
It does care that network devices incl. UDP will not seed updates when the device is disabled.
Furthermore, there is now a dedicated WLED device which leverage on the above, as well uses the WLED API to switch-off/on the WLED via it's API.
Hopefully, the changes on the hyperion/WLED integration & user experience will improve the situation you outlined.
Furthermore, it is planned to discover WLED devices to ease configuration, but a WLED change is pending for supporting this scenario.
You may want to test the development version or wait until changes make it to a release.
