Aircoookie / WLED

Control WS2812B and many more types of digital RGB LEDs with an ESP8266 or ESP32 over WiFi!
https://kno.wled.ge
MIT License
14.57k stars 3.12k forks source link

Hyperion Config? #212

Closed OliPassey closed 4 years ago

OliPassey commented 5 years ago

Hey - i have WLED working fully, and attached to the back of my tv - but i can't get hyperion to connect to it. Would anyone who has got this going mind taking a look at my config?

hyperion.config.json: https://gist.github.com/OliPassey/691fc97d30e759ba3b4330071994f4e3

My WLED is running on 10.0.0.97 - and is reachable by the raspberrypi running kodi / hyperion. (did a ping test)

In the hyperion logs i see:

ssh out:    /storage/hyperion/bin/hyperion-remote.sh  -c 855dff
ssh in:     hyperion-remote:
ssh in:         version   : V1.03.5 (GitHub-66bef6b/fb413cd-1566231780
ssh in:         build time: Aug 25 2019 10:39:08
ssh in:     Connected to localhost:19444
ssh in:     Set color to 133 93 255

I presume the localhost:19444 is hyperion connecting to something local which then forwards onto the WLED IP as detailed in the top of the config file:

"device" : { "name" : "MyHyperionConfig", "type" : "udpraw", // also tried regular udp "output" : "10.0.0.97:19446", "rate" : 1000000, "maxpacket" : 1450, "protocol" : 0, "colorOrder" : "grb" },

But the LEDs don't light up. WLED is able to control them from the GUI - but not Hyperion. Am i missing something from the forwarders section?


    // JSON SERVER CONFIG
    "jsonServer" : 
    {
        "port" : 19444
    },

    // PROTO SERVER CONFIG
    "protoServer" : 
    {
        "port" : 19447
    },

Any help would be greatly appreciated

OliPassey commented 5 years ago

Always 5 minutes after asking for help....

Removing these lines from the config and now all is well.

    // JSON SERVER CONFIG
    "jsonServer" : 
    {
        "port" : 19444
    },

    // PROTO SERVER CONFIG
    "protoServer" : 
    {
        "port" : 19447
    },

Updated the gist for anyone looking in the future.

sjude68 commented 5 years ago

I am using the Hyperion capture app on my Sony Android TV and Wled. What config changes should I do to make Hyperion work.

https://play.google.com/store/apps/details?id=nl.hyperion.hyperionfree

OliPassey commented 5 years ago

When you say Hyperion Capture App, do you mean the one you've linked to? That app doesn't do screen capture, and it connects to the Hyperion Daemon that you need to have running in your network. I have mine on a RaspberryPi that also runs kodi, doing the screencapture, it then forwards the lighting commands onto WLED via UDP.

Mariu86 commented 5 years ago

It's a way to screen capture the Netflix?

Aircoookie commented 5 years ago

It may not be possible to make it work with Netflix due to anti-DRM measures, but using it in a browser on a (Linux) computer might be your best bet. 4K won't work for sure, though.

phamre commented 5 years ago

When you say Hyperion Capture App, do you mean the one you've linked to? That app doesn't do screen capture, and it connects to the Hyperion Daemon that you need to have running in your network. I have mine on a RaspberryPi that also runs kodi, doing the screencapture, it then forwards the lighting commands onto WLED via UDP.

i think me means this app..

https://play.google.com/store/apps/details?id=com.abrenoch.hyperiongrabber

sjude68 commented 5 years ago

Yes this app also does screen capture and forwards to the IP:port specified I have a RPi3 running hyperion and it works. How to link it to WLED connected ws2812 led strip On Wed, 4 Sep, 2019, 9:02 PM Oli Passey, notifications@github.com wrote:

When you say Hyperion Capture App, do you mean the one you've linked to? That app doesn't do screen capture, and it connects to the Hyperion Daemon that you need to have running in your network. I have mine on a RaspberryPi that also runs kodi, doing the screencapture, it then forwards the lighting commands onto WLED via UDP.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Aircoookie/WLED/issues/212?email_source=notifications&email_token=AD35TY3SGC4IGVSEXZLSTKDQH7IJHA5CNFSM4IRUFWPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD537KLQ#issuecomment-527955246, or mute the thread https://github.com/notifications/unsubscribe-auth/AD35TY5NGM5G5OMG7JQGW23QH7IJHANCNFSM4IRUFWPA .

tpmodding commented 4 years ago

in hyperion.ng you can choose the e1.31 device, and at hyperion you can choose the udp device

as above mentioned you have to put in the WLED IP at the Output part

"device" : { "name" : "MyHyperionConfig", "type" : "udpraw", // also tried regular udp "output" : "192.168.1.97:21324", <-----ip and port from your wled device "rate" : 1000000, "maxpacket" : 1450, "protocol" : 0, "colorOrder" : "grb" },

piowys commented 4 years ago

hyperion.ng controller type should be udpraw and you should use your WLED IP as Target IP and port 19446 as stated in documentation: https://github.com/Aircoookie/WLED/wiki/E1.31-&-UDP-Realtime-Control#hyperion (UDP realtime is enabled and E1.31 multicast is disabled in WLED my sync settings).

Nevertheless, I can't find this 19446 port in WLED settings anywhere, @Aircoookie IMO it should be at least pointed/described somehow in the sync settings page.

And thanks for WLED! It's great! ;-)

daekka commented 4 years ago

I'm not able to connect from android hyperion apps. I use WLED version 0.9.0-b2

preslav87 commented 4 years ago

I have also the same issue. All the hyperion apps from the market can't connect to the wled. I had tried the 19446 and no effect.. I am using the wled version 0.9.0-b1

sjude68 commented 4 years ago

Hyperion app doesn't connect to wled directly. The app captures the screen and sends to hyperion server. Hyperion should be running on Raspberry Pi. The server forwards to wled.

This is how I have configured it.

recliq commented 4 years ago

Just to expand on @sjude68 comment:

Hyperiond (the server component) accepts two types of input on two different ports, by default these are 19444 and 19446. Port 19444 accepts JSON messages and is used by the eg. the adroid hyperion remote app. Port 19446 accepts binary data and is used to receive the captured image data.

WLED understands neither of these, instead it can be used by hyperiond as an output device (udpraw protocol on port 19446).

The use of port 19446 for updraw protocol on the WLED side might be a bit misleading...

sjude68 commented 4 years ago

So 1st setup Hyperion server on Raspberry Pi or any other device. Then instead of using the led strip directly connected to the server, use wled connected led strip.

When hyperion server is off the strip works as configured on wled.

shafr commented 4 years ago

My config is:

Was anyone able to make it work and can provide reasonable manual on that ?

austwhite commented 4 years ago

DrZzs did a video of hyperion a little while ago and he used a WLED module. It works well. I have done it as well.
Hyperion can use E1.31 but it can also send out raw data. WLED can accept both of these. Use the web config for Hyperion which is http://your.hyperion.ip.address:8090

austwhite commented 4 years ago

In Hyperion under Configuration and LED hardware, setup your Controller Type as upde131 or updraw depending on your preferred method. Default ports should work. Target IP is the IP address of your WLED board. E1.31 uses port 5568. Can't remember off hand the raw port. From there it's pretty well the same as any other Hyperion setup 🙂

stale[bot] commented 4 years ago

Hey! This issue has been open for quite some time without any new comments now. It will be closed automatically in a week if no further activity occurs. Thank you for using WLED!