katagia Simplest would be that you make use of the existing Gif-Effect. No need for development...
Just provide an animated Gif and it is played and mapped to the LED-Matrix you configured per layout.
Posts by Lord-Grey
-
-
TPmodding I updated the thread…
-
Wenn ich jetzt die Ziel IP in der Hyperion App eintrage connectet die App nicht.
Wie gesagt, wenn Du die Hue-Bridge direkt per APP steuern willst (über Ihre IP), nimmt die Hue App.
Wenn ich die IP von Hyperion NG nehme dann leuchtet das Ambilight egal welche Farbe ich nehme aber nicht die Hue Lampen über die App
1. Kannst Du denn die Hues über das Hyperion-Web Frontend steuern? Also eine Effekt über die Fernsteuerungsseite abspielen?
2. Welche Hyperion Version verwendest Du? Kannst Du die Details teilen; am Besten über System->Log->Copy to Clipboard
-
See here why Hyperion‘s default channel is 10 now
-
Die Hue App steuert die Hue Bridge
Die Hyperion App steuert Hyperion
Hast Du allerdings die Hue Bridge in Hyperion als LED Device konfiguriert, kannst Du die Hyperion App benutzen, um alles mit dem LED zu machen was angeboten wird (der Hyperion App ist egal, welcher DeviceTyp in hyperion konfiguriert ist
-
hapo1313 Besides Router settings, best practice is to use the device’s hostname rather that the IP address. This exactly is to avoid you are running in those issues.
-
hapo1313 Normally, you can do it in the router. Just check, if your router provide you with that feature.
-
Joel13 You might have seen in the releasenotes that we are providing with alpha.11 a script to switch the user now.
-
sL0w Ich habe es jetzt nochmal unter alpha.11 gestestet und bei mir geht es.
Hattest Du auch gespeichert? -
Danke. Muss ich mir anschauen.
-
Am besten einfachen den Assistenten benutzen...
-
Houstonwehaveproblem Unfortunately, an older ws821x library version got linked into alpha11.
That library does not support your hardware.
This will be fixed in the next release.
Until then, you can make use of alpha.10 or build hyperion yourself after the library was updated again.
-
Dann richtest du dir zwei zusätzliche LED-Instanzen in Hyperion.ng ein und weist jeder Instanz jeweils den Steuerungstyp "philipshue" zu.
Für die Konfiguration empfehle ich Dir:
Du definierst beide Lampen als eine Entertainment-gruppe in der Hue App. (Lampen müssen Entertainment fähig sein).
Dann definierst Du Dir eine! zusätzliche Instanz in Hyperion und konfigurierst die Entainment-gruppe über den Wizard.
Die Hue-Lampen einzeln anzusteuern war der alte, nicht performante Weg; das geht jetzt besser.... -
That the host information is not available after discovery is a Nanoleaf issue which you see as an effect in Hyperion.
See the feedback by Nanoleaf:
„Hi @Lordgrey
This is a known issue and will be resolved soon. Thanks for reporting it. I will let you know once its ready for release. There is an internal ticket for this already and we are working on it.
Apologies for the inconvenience caused.
Regards“
I will forward when they come back.Until then, please provide the hostname/IP-Address manually using the custom configuration possibility.
-
Try adding the user running hyperion into the group "dialout"
-
Thank you.
Would you mind checking the ssdp-esp.txt file again, please?
It contains the Nanoleaf data and not the ssdp output from the script.
You can also post the file via a private conversation, if you like. -
2. Would you mind to put the following into your browser url field and press return
http://192.168.1.126:16021/api/v1/sEW4TXvovYhmBy0K330zXMnQ2MfOqx35
Share the output
I assume that the device with IP=192.168.1.126 is the one that you have the LED-Number/Layout problem with? -
jackthias Let us sort one thing after each other. I need to see how the Shapes respond to the ssdp discovery. Strange is that the responses do not contain an IP-address, but that might be to the fact that the message looks different.
Would you mind
a) download the attached python script (ssdp.py.txt) and rename it to ssdp.py
b) upload ssdp.py to the server where Hyperion is executed
b) run the script in the directory where the script resides
python ssdp.py
c) Share the output with me -
You have given the IP Address with port. That will not work.
Just give hostname or IP-Address, i.e. host: 192.168.1.126 -
2021-10-05T08:43:38.696Z [hyperiond SSDPDISCOVER] (DEBUG) (SSDPDiscover.cpp:294:discoverServices()) [2] service record(s) found 2021-10-05T08:43:38.697Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1428:handleLedDeviceCommand()) response: [{"devices":[{"cache-control":"no-cache=\"Ext\", max-age = 60","id":"http://:16021","ip":"","location":"http://:16021","other":{"ext":"","nl-deviceid":"CF:8A:E4:90:74:CE","nl-devicename":"Shapes E76F","s":"uuid:e91115d9-6634-471a-8b03-0a7715fbee0e"},"port":16021,"server":"","st":"nanoleaf:nl42","usn":"uuid:e91115d9-6634-471a-8b03-0a7715fbee0e"},{"cache-control":"no-cache=\"Ext\", max-age = 60","id":"http://:16021","ip":"","location":"http://:16021","other":{"ext":"","nl-deviceid":"62:E1:C7:7A:30:97","nl-devicename":"Shapes 2ADB","s":"uuid:c0b1d9b0-b603-4507-be8f-611e027f1a8f"},"port":16021,"server":"","st":"nanoleaf:nl42","usn":"uuid:c0b1d9b0-b603-4507-be8f-611e027f1a8f"}],"discoveryMethod":"ssdp","ledDeviceType":"nanoleaf"}]
I would need to check what happens during discovery.
The response does not include the IP-Address and I would need to investigate why.
To get it working, you can select "Custom Device" and configure the device's IP-Address manually until we figure out more...
