HyperHDR did not connect to Wled

[D3ltorohd]

Hello,

when i start HyperHDR because i start my tv he cant connect to my wled. I have to change the ip, i have to change RGB. And after a while it connects and changed the led's how it should. After this procedur i have 1-3 days no problem. Then the problem is coming back.

Thats what im see on, when i go to the web interface.

When i was finishing watching, i shutdown hyperhdr with the json and wled plug off. It turns on when i start the tv at the evening.

Maybe this is a problem for hyper when he is in standby and no wled it there ?

2025-04-21T10:19:17.618Z [NET_DISCOVERY] Removing not responding WLED at 192.xxx.xxx.xxx (wled-ambilight-tv.local)

Greet's D3

[awawa-dev]

Hi
This is one of the reasons I don't recommend WLED for HyperHDR setup https://github.com/awawa-dev/HyperHDR/wiki/Quick-start#performance-pro-tips You can try downgrading WLED or turning off Wi-Fi sleep in the options, but there's no guarantee it will help in your environment. Your router may also be a factor: my WLED instances really didn't like my previous Asus router, dropping out of mdns usually after a few minutes, after upgrading to a newer model with Wifi 6 it worked much better, although they also sometimes drop out of the network during tests.

[D3ltorohd]

Hm i dont know why it happens now. I have the Setup for a year now. And never had this problems. I did not change anything on wled side. But i will have a look what you talking about, maybe it helps.

Hm the WLED itself and my fritzbox seems to be running fine. I can permanently go to the wled web interface and can change things that effect directly.

[awawa-dev]

maybe a neighbor bought a smart dishwasher with wifi and there is some kind of fight for the channel between the routers ;-) it's hard to say what's going on, there should be something in the logs but the message you posted only indicates that mdns is lame (it doesn't have to mean a complete lack of connection). and in order to restart the controller you don't have to change the ip (why? did it actually change?) just turn it off and on in remote.

[D3ltorohd]

What did you prefer to use ? I have a wemos d1 mini. What else can i use that worked better with hyperhdr ? But the wifi problem is the same, thats nothing to do with wled or ?

[awawa-dev]

Neither. I prefer a wired solution because we are using a constant color stream to the device and need reliability. WLED is a complicated program that also relies on a complicated Arduino/NeopixelbusLibrary layer, which relies on the much more complicated and constantly changing Expressid SDK. The quality of the board can also be a factor, for example the cheap esp32-s2 offers a rather awful Wi-Fi experience (but works fine on a wired connection) and there are many esp32 variants that are constantly changing...esp8266 is legacy model with limited resources and other hardware limitations and should not be used for recent WLED versions.

[D3ltorohd]

Wired did you mean over LAN ? I had no chance to wired it other, because the Server is in the cellar.

[awawa-dev]

Rather USB/Serialport. If you are stuck with wifi, such considerations are pointless anyway.

[D3ltorohd]

USB should work, my Video Capture Stick goes into a usb hub, and that cable goes into the cellar to the server.

Hm it works so fine in the past, no problems. At the evening i put the tv on and ambilight works. Since view Weeks i have this problems. I have change the wlan channel to, maybe it works better. I have too test some things, maybe that the led goes on with power wait some minutes and start then hyperhdr over the json api command.

[awawa-dev]

If it was working and stopped without any software update then it seems reasonable that there is some new factor: ESP/router failure or a neighbor has expanded his Wi-fi network ;-)