Schau mal in Dein log. Dort sind lauter Netzwerk Issues...
Starte hyperion nochmal neu.
Hast Du ggf. noch einen andere Anwendung laufen, die zum Nanoleaf streamt?
Und welches Nanoleaf hast Du?
Schau mal in Dein log. Dort sind lauter Netzwerk Issues...
Starte hyperion nochmal neu.
Hast Du ggf. noch einen andere Anwendung laufen, die zum Nanoleaf streamt?
Und welches Nanoleaf hast Du?
@Tyler983 How do you shutdown your pi?
Kriege meine Nanoleaf nicht zum laufen.
Teile mal den LogOutput mit uns...
Im UI System->Log
When I put to sleep all of my devices, leds staying on showing random lights.
That should be fixed with alpha 9.
Give it a try...
Hi
sorry, that I do not respond in Dutch....
Set the Baud rate to 115200 and try again.
In addition, I would suggest you install the latest release which is alpha9.
@snikcers Das hyperion-team würde gerne mit dem HyperHDR Entwickler zusammenarbeiten und wir hatten auch mehrmalige Versuch gestartet ihn zu überzeugen PRs einzureichen damit alle davon profitieren.
Wenn jemand aber darauf nicht eingeht und nur die Infrastruktur (und die Arbeit anderer) benutzt, um sein eignes Ding zu machen, sind uns auch die Hände gebunden.
"dass er es HDR to SDR Conversion nennt obwohl es doch keine sei"
Da magst Du die Diskussion hier im Forum mit der PR Diskussion zu verwechseln.
Im PR ging es vor allem um Code-Qualität und generelle Verwendbarkeit.
Ziel von hyperion ist es einer breiten Community die Features verfügbar zu machen.
Wir geben hier nicht auf... aber ich hoffe es gibt Dir ein wenig Einblick, wo wir diesbezüglichen (leider) stehen.
@Bub4 Das ist ein bekanntes Problem und wurde schon korrigiert.
https://github.com/hyperion-project/hyperion.ng/pull/1047
Ist im nächsten Release gefixt.
Hey
Lightpack hat in Alpha8 ein Problem.
Siehe https://github.com/hyperion-project/hyperion.ng/issues/1015
Das ist im nächsten Release behoben.
Alternativ, kannst Du hyperion selber „bauen“ und bekommst den Fix schon früher...
I would assume that you are running APA with rewrite time > 0.
Then you might be affected by the following bug: https://github.com/hyperion-project/hyperion.ng/issues/1007
Two options:
a) Wait for the next release
b) Build hyperion from the latest master yourself
Good to hear to it works in general.
Did you found a working setup with Arduino and Flirc?
Looks like you have two USB devices
crw-rw---- 1 root dialout 166, 0 Nov 11 13:09 /dev/ttyACM0
crw-rw---- 1 root dialout 166, 1 Nov 11 13:19 /dev/ttyACM1
Have you tried configuring "/dev/ttyACM1" ?
Or could you execute the following commands? Does one come back with "Ada"?
1.
cat /dev/ttyACM0
To stop press, ctrl-C
2.
cat /dev/ttyACM1
To stop press, ctrl-C
3.
dmesg | grep usb
4.
dmesg | grep tty
Please share the output...
Keine Ahnung...
Wenn der Browser die URL nicht auflösen kann, kann Hyperion das auch nicht...
Was kommt beim nslookup auf die IP-Adresse?
And that is the problem....
It has nothing to do with Hyperion, but that the hostname is not resolved on your local network...
Suggest you check the name assigned in the Fritzbox.
What does the url I asked you to run in the browser return back?
Could you also ping me which Hyperion build you are using?
UI: System->Hyperion about
Hi
Good that it is working now.
I am of the opinion that it should also with the hostname and with and without domain.
What does the url I asked you to run in the browser return back?
sorry, I had a typo....
Could you do a ls -la /dev/tty*
Hey
the communication with the bridge already fails at the very beginning.
You see it that the Bdrige details are all empty.
That the device is not put in error at that point in time is a different story...
2020-11-10T22:26:22.410Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRestApi.cpp:124:get()) GET: [http://philips-hue.fritz.box:80/api/-ThXP8g2K2Sn7BOdj9JScFsi******************/]
2020-11-10T22:26:22.413Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRestApi.cpp:182:getResponse()) Reply.httpStatusCode [0]
....
2020-11-11T10:50:26.248Z [hyperiond LEDDEVICE] (DEBUG) (LedDevicePhilipsHue.cpp:417:log()) Bridge Name :
2020-11-11T10:50:26.248Z [hyperiond LEDDEVICE] (DEBUG) (LedDevicePhilipsHue.cpp:417:log()) Model :
2020-11-11T10:50:26.248Z [hyperiond LEDDEVICE] (DEBUG) (LedDevicePhilipsHue.cpp:417:log()) Bridge-ID :
2020-11-11T10:50:26.248Z [hyperiond LEDDEVICE] (DEBUG) (LedDevicePhilipsHue.cpp:417:log()) SoftwareVersion :
2020-11-11T10:50:26.249Z [hyperiond LEDDEVICE] (DEBUG) (LedDevicePhilipsHue.cpp:417:log()) API-Version : 0.0.0
2020-11-11T10:50:26.249Z [hyperiond LEDDEVICE] (DEBUG) (LedDevicePhilipsHue.cpp:417:log()) EntertainmentReady : 0
2020-11-11T10:50:26.249Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'philipshue' signals error: 'No light-IDs found at the Philips Hue Bridge'
Could you give it a try with the following reconfigurations:
a) Use the hostname without domain (i.e. "philips-hue")
b) Use the IP-address of the bridge
c) Open the following URL via a Browser. What do you get back?
Replace the client name with the not masked one.
http://philips-hue.fritz.box:8…JScFsi******************/
Thank you!
I checked the log again
I looks like that your bridge is reachable, but could not access the values:
2020-11-10T21:43:35.306Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRestApi.cpp:124:get()) GET: [http://philips-hue.fritz.box:80/api/-******************************************/groups/6]
2020-11-10T21:43:35.308Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRestApi.cpp:182:getResponse()) Reply.httpStatusCode [0]
Valid answer from the bridge should be a StatusCode = 200 rather than 0
2020-11-11T10:59:24.337 hyperiond LEDDEVICE : <DEBUG> ProviderRestApi.cpp:179:getResponse() | Reply.httpStatusCode [200]
Is your "Benutzername" correct? It confuses me that it starts with a minus "-"
Could you provide a full log, please?
Please enable
You might need putting Settings Level to "Expert" first.
You could share the full log with me privately... Just start a Conversation with me in the Forum.
The error indicates that your system does not provide any serial devices... or the device is busy
2020-11-11T08:31:49.324Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'adalight' signals error: 'No serial device found automatically!'
Could you please post more details about your system.
Copy/Paste the System Info from "about hyperion"
In addition, could you do a ls -la /dev/ttyp*
If you running on an rpi, do you have Bluetooth on?