Yeelight Color S1 Problem (RPi + USB HDMI + Yeelight)

Hello, I'm trying to get Hyperion set up for the first time and was hoping for some help with a problem. My end goal is to use HyperBian with HDMI input and an LED strip wired to the GPIO. I have a Pi 3B and splitter/capture devices for HDMI but don't have an LED strip, and wanted to try to get a feel for Hyperion before buying more hardware. I noticed Hyperion supports Yeelight, and I have a couple of Color S1 bulbs, so I'm trying to set these up as a first step.

Installing Hyperion on the Pi and accessing the web interface is straightforward. The USB capture seems to work fine, and I've also tried the 3rd-party Android app as an alternate source - both appearing in the live feed and showing an appropriate hue in the LED overlay.

However the bulb itself never seems to change, although it does respond when testing with the wizard. Trying to load an effect via Effect Configurator will appear successful in the UI, and load the effect in Remote Control > Source Selection, but still has no impact on the bulb.

These are the logs from the webUI: [MEDIA=pastebin]8rc4ytiS[/MEDIA]
(I couldn't seem to find the logs on the Hyperbian file system over SSH, if someone could point me there that would also be appreciated)

I gave this a shot and the logs look quite a bit different:
[INDENT][INDENT] 2021-02-23T04:26:53.312Z [hyperiond LEDDEVICE] (ERROR) Yeelight device '192.168.0.42' signals error: 'Socket operation timed out'
2021-02-23T04:27:39.620Z [hyperiond LEDDEVICE] (ERROR) Yeelight device '192.168.0.42' signals error: 'Socket operation timed out'
2021-02-23T04:27:39.621Z [hyperiond LEDDEVICE] (ERROR) Failed to open [192.168.0.42]
2021-02-23T04:27:39.621Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'yeelight' signals error: 'All Yeelights failed to be opened!'
2021-02-23T04:29:50.037Z [hyperiond LEDDEVICE] (ERROR) Previous line repeats 1 times
2021-02-23T04:29:50.038Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.0.13
2021-02-23T04:29:52.673Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1063:handleLoggingCommand()) log streaming deactivated for client ::ffff:192.168.0.13
2021-02-23T04:31:41.819Z [hyperiond LEDDEVICE] (DEBUG) (LedDeviceYeelight.cpp:1185:stopMusicModeServer()) Stop MusicModeServer
2021-02-23T04:31:41.820Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) LED device: disabled
2021-02-23T04:31:42.572Z [hyperiond LEDDEVICE] (DEBUG) (LedDeviceYeelight.cpp:1171:startMusicModeServer()) The music mode server is running at 192.168.0.73:39615
2021-02-23T04:31:43.575Z [hyperiond LEDDEVICE] (ERROR) Yeelight device '192.168.0.42' signals error: 'Socket operation timed out'
2021-02-23T04:31:43.575Z [hyperiond LEDDEVICE] (ERROR) Failed to open [192.168.0.42]
2021-02-23T04:31:43.575Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'yeelight' signals error: 'All Yeelights failed to be opened!'
2021-02-23T04:31:49.768Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.0.13[/INDENT][/INDENT]
I'm not too sure what you mean by "Power-LAN"; googling that came up with ethernet-over-power which I definitely don't have. If you're just talking about wiring up the Pi to the router over ethernet, I gave that a try and also repositioned the bulb. The bulb has been mounted behind my TV for a few months now and responding fine to commands issued from Home Assistant, but I guess music mode is more sensitive to connection issues and these new logs would definitely seem to back that up.
This was still causing some errors (didn't manage to capture, sorry), but after some experimentation it seems like changing the LED Configuration > Transition to Sudden got things working for both solid colours and HDMI via USB capture. I need to spend some more time from here to see how it works with the bulb behind the TV again and/or the Pi back on Wifi. But thanks! I'm glad it's now responsive

Were you asking about power-LAN because it might introduce issues, or just as a convenient way to connect the Pi? Fortunately my Pi is about 30cm closer to a network switch than a power socket so a direct connection is actually easier I don't own any power-LAN adaptors right now but I've experimented in a few homes I've rented and old or new it's always been a poor experience.

Have also tried experimenting with latch times as high as 1000 but it doesn't seem to make a noticeable difference. There have also been a few under-voltage warnings popping up so I'll need to sort that out before fiddling around much more... Probably a job for another day though.