Go to the following link of the PR
https://github.com/hyperion-pr…s?check_run_id=1368607344
Click on Artifacts and you can download a ready build package for your platform.
Posts by Lord-Grey
-
-
Das ist aber doch schon ungewöhnlich.
Meines wissens nach sendet hyperion keine Befehle an WLED, und wenn wäre das sich 'Power on'Beim Hyperion WLED Device schicke ich on bzw. Off Kommandos an WLED
, aber auch nur, wenn ein hyperion Device an oder ausgeschaltet wird bzw. nichts zu Streamen da ist.Anstatt nur die Konfiguration zu posten, wäre hier ein Debug log hilfreich...
System->Log
Dort sieht man, ob zusätzlich was an oder aus geschaltet wird.
Ansonsten empfehle ich mal einen Effect über die „Fernsteuerung“ d.h. Remote Control zu initiieren.Edit: Im log findet man auch ggf. Fehlermeldungen. Dann brauchst man nicht zu raten...
-
-
@iam960 I fixed the issue. You could try the fix downloading the version build as part of the following PR:
-
@iam960 I guess I know the issue.
I try splitting the domain from hostname.
If the Hostname is an IP-Address, then it looks like I am splitting wrongly...
I will have a further look into the scenario. -
Erstelle eine zweite Instanz und konfiguriere dort ein LED-Device vom Typ WLED mit dem Layout das WLED ansteuertet. Done!
-
But yesterday, in my router, it has the name 'yeelink-light-strip2_miap7fe2'.
Yes, this is what I expected to get back in the UI. If you see my screenshot, it exactly follows the same logic of the prefix.
Sometime it helps,if the lights are longer in the network...I still have not figured out the logic....
I might need to fall back to configure IP-addresses, which I currently avoided. In case an IP-address change, users complain that lights are not working...
And not everybody is able to configure fixed IPs in their routers.In addition, could you do me a ping with "-a" that the name is resolved during the ping, please?
I am not interested into the ping-time, but how the name is resolved. -
Thanks for coming back with the details.
It looks like that the routine resolves the hostname for the bulb as "192", but when using the name, it does not resolve into a proper IP-Address.In the 2nd case where the "identify" worked, do you have a screenshot there too.
Is in that case the value in brackets, e.g. (192) different?If you do a (replace 192.XXX.XX.XXX with the lights IP)
arp -a 192.XXX.XX.XXX
or
ping -a 192.XXX.XX.XXX
What name does it resolve in?
-
@ModuloFS Thanks for providing the output. That was helpful!
I opened an issue for you on the given problem:
https://github.com/hyperion-project/hyperion.ng/issues/1076I might need getting back to you for testing a fix, if this would be ok for you?
-
Are you able to start hyperiond from the Commandline in Debug Mode -d Option?
And then share the log output? -
@Iam Tobe I still need to do some documentation on Yeelight.
Nevertheless, after using the Wizard the Yeelights should work. Sometime you first need to restart hyperion...(for that we have an issue already logged).As it looks like that the configuration did not work at your end automatically.
Would you mind activating the debug log mode (in the UI System->Log),
plus then start the yeelight wizard and do the config again?Does the "Identify Light" button works for you? i.e. the respective Yeelight blinks red/blue?
Please share a screenshot of the wizard (see sample below) and the log-output with me, please.
I would like to explore, if it is a coding or documentation issue.Thanks for your support!
-
@Frogro Hier die erste Version zum Testen.
https://github.com/hyperion-project/hyperion.ng/pull/1070
Am besten starte die Konfiguration über der Wizard....
-
@Phil_T33 There is no need that you compile yourself. There are ready-made builds available on Git-Hub.
Alternatively you could check-out hyperbian which is a comple image for rpi.
You of course would need to configure your setup after installation. -
As the LEDs to not light up, are there any errors in the Log output?
You can access the log via System->Log.
Might be also good, if you put the log in Debug and share the output. -
@Frogro If you install hyperion.ng via package there is no need to install all the libraries you are referring to. hyperion.ng brings the required libraries via the package.
What you outline is when one would like to compile hyperion.ng himself. The only exception are platform specific libraries like libcec.
The rest nevertheless is a good outline of installation activities. -
@PaulWebster Thanks for providing more background information. I was not aware that the additional server component is required. Seems you are already set up well.
-
hyperion.ng has FadeCandy support. You might want to try, if this works and then you could avoid an extra component on between....
-
hyperion.ng is what I was referring to here.
If you start hyperion via " "sudo /usr/bin/hyperiond /etc/hyperion/hyperion.config.json"" then it is not hyperion.ng
and you followed the wrong instructions. -
a) To compile a local checked out hyperion.ng repository in a docker container, I tested a while ago.
Here is is modified script https://ufile.io/gtt43pv1
I have not manged to clean it up and merge it with the other compile script, but you might find it helpful.
Place the script in ./bin/scripts and run from the hyperion-home directory:sudo ./bin/scripts/docker-compile_local.sh -t amd64 -b Debug -p false
That will build hyperion.ng in Debug mode for unbuntu-x86 using docker.
Via -t you can also build for other platforms.Do ./bin/scripts/docker-compile_local.sh -h to see the other options.
b)
The binary packages suggested in the primary documentation on the website certainly do not work, as they're still based on the old QT4 build
Would you mind sharing the hyperion.ng documentation sites which still makes references to QT4?
That would get us in the position to have it fixed.... -
@sPOiDar hi, maybe saving you some time and effort...
Please note that the classical Hyperion is discontinued and is not maintained.I suggest you give Hyperion.NG a try either using ready made packages or compile yourself (incl. Qt5).
https://github.com/hyperion-project/hyperion.ng
Plus see input by @Paulchen-Panther above...
