PicCap + Hyperion + WLED (WebOS) All installed, how do we get them to talk!

Hey guys,

As the title says, i've got my WLED lights all set up. I've installed PicCap and Hyperion to my TV everything seems to be running. I've also installed Hyperion to my laptop and configured the lights around the TV. I'm now though at the point where i'm looking at how do i actually get all of these things talking to each other.

Apologies if i've missed something in a guide.
All help is really appreciated,

Yep WLED is all configured and i can successfully control the LEDS

Hmm i guess my hyperion on the LG doesn't fully look like the interface you've posted on the left there. It has a black window saying:

Service Elevated: Yes

Daemon Running: Yes

Daemon Version -- Version info... etc etc

Autostart - set to true

Start

Stop

Reboot System

the result at the bottom says Daemon Started

So PicCap should have the IP address of my WLED instance ?

Again thanks for the help buddy this is going to be awesome and i can feel i'm close

Ah brill! Ok this makes all the sense i'll give it a go and report back.

pclin - Ok i had everything up and working and it was great. I then went into wled looking to increase brightness clicked override once, upped the brightness and removed the power limiter. However now i can't seem to connect to WLED at all. Even plugging this back into my laptop to reflash makes the device pop up for about a second. Lights go to orange for a second and then move to i think the last colour they were on (red).

Not sure how to progress and hope i haven't fried my board.

So plugged them back in and nope i can't seem to get to WLED at all. I've also tried plugging back into my laptop to reflash and it shows up as a device in WLED for a micro second. I haven't changed the DNS for WLED.

Following your hyperion instructons i can see this in the log:

2023-04-24T17:40:45.413Z [LEDDEVICE|First LED Hardware instance] (ERROR) Cannot resolve mDNS hostname for given service [lights._wled._tcp.local]!
2023-04-24T19:01:45.283Z [LEDDEVICE] (ERROR) Resolved mDNS hostname [lights.local.] timed out
2023-04-24T19:02:33.440Z [WEBSOCKET] (DEBUG) (WebSocketClient.cpp:213:sendClose()) Send close to ::ffff:192.168.1.68: 1000
2023-04-24T19:02:34.024Z [WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.1.68
2023-04-24T19:02:34.233Z [WEBSOCKET] (DEBUG) (JsonAPI.cpp:149:handleInstanceSwitch()) Client '::ffff:192.168.1.68' switch to Hyperion instance 0
2023-04-24T19:02:34.535Z [WEBSOCKET] (DEBUG) (JsonAPI.cpp:1220:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.1.68

I had it set up to lights.local as well as the IP but neither are working.

If i'm really quick i manage to get to the port selected when flashing and it starts to load before saying

There is another application using the serial port. Even if i turn off the wifi the board keeps defaulting to the red lights and is unresponsive.
I genuinely think i've just got a broken board. The problem is if i order another i want to make sure whatever settings i changed wouldn't do this to another board.

5v 2.1amp it's a usb plug and it's about 110 LEDS

So I looked at the wiring and embarrassingly one of the cables had come loose. After plugging it in, the device was connected to wled for about 15-20 seconds before then disconnecting.

I rechecked and everything is still plugged in and connected. It's very odd.