Alles anzeigenI have built a nice AtmoOrb using an ESP8266. It works fine using the Android-App, or by manually crafting+sending UDP packets (i.e. I can send \xC0\xFF\xEE\x04\x01\x00\xFF\x00 to 239.15.18.2:49692 to make it very green)
But I can't figure out how to get Hyperion working with it. The configuration looks ok to me, I get no frightening error messages:
[MEDIA=pastebin]B8E06nUV[/MEDIA]
[MEDIA=pastebin]tLZKeqRZ[/MEDIA]
but it does not send any packages to the device -- except when I kill the daemon, then it sends an "switch off all lights" (C0FFEE0101000000), which successfully switches off the LED
I try controlling the daemon with hyperion-remote,
Code$ hyperion-remote -c Red --print hyperion-remote: version : master (brindosch-f92bfa8/21a4f0c-1462453483 build time: Jun 5 2016 17:11:38 Connected to localhost:19444 Set color to 255 0 0 Command: {"color":[255,0,0],"command":"color","priority":100} Reply: {"success":true}
which did not trigger any packages to the device. I also tried hyperion-x11 (I can see packages going to localhost:19445), but this also led to no data sent to the device (checked with wireshark).
Any suggestions? I fear it's something super-simple, and I'm going to feel stupid...
I had the exact same problem. I updated my Hyperion and the strange thing was that imediatly after an update it would work, but after a reboot the problem would come back.
Then I figured out then when the Rasberry Pi was already running killing Hyperion and starting it again after an reboot would fix te problem.
Then I realised the problem arises probably because hyperion starts to quickly before the Rasberry Pi has astablised its network connection and therfore it fails.
So I implemented a 30 second delay (sleep 30) in my autostart.sh script on the Pi that starts Hyperion after an reboot.
This worked and fixed my problems.
So for people that have the same problem, a delay in the \Configfiles\autostart.sh script might solve your problems.