HyperHDR Wont Connect to any WLED instence

[MrPresident2]

Bug report, debug log and your config file (FULL LOGS ARE MANDATORY)

Steps to reproduce

What is expected?

What is actually happening?

System

I'm having an issue and I cant find any info about it online,
while trying to connect to any WLED instance, I'm getting an error:

2025-02-06T16:39:21.302Z [LEDDEVICE1_WLED] (LedDevice.cpp:63) Switch on
2025-02-06T16:39:21.303Z [LEDDEVICE1_WLED] (DriverNetWled.cpp:126) 
2025-02-06T16:39:21.303Z [LEDDEVICE] (ProviderRestApi.cpp:174) GET begin: [http://192.168.1.41:80/json] []
2025-02-06T16:39:21.805Z [LEDDEVICE] (ProviderRestApi.cpp:198) GET end (502 ms): [http://192.168.1.41:80/json] []
2025-02-06T16:39:21.805Z [LEDDEVICE] Reply error. Reason: [408 Timeout] - Check the status of your network and whether the destination IP address is correct
2025-02-06T16:39:21.805Z [LEDDEVICE1_WLED] Device 'wled' is disabled due to an error: 'Empty WLED config'

the WLED interface is working at that address, and while trying to see the /json I do see it. so I'm not sure why Hyper cant connect to them.

and ideas how to solve it?

full logs added as a text file

full logs.txt

[awawa-dev]

Hi
This is just a network timeout... nothing more to see or diagnose on HyperHDR side ;) Either the device is unavailable or it takes a very long time for it to response.

[MrPresident2]

Hi This is just a network timeout... nothing more to see or diagnose on HyperHDR side ;) Either the device is unavailable or it takes a very long time for it to respond.

I understand it's a network timeout, but how do we solve it? all the 25 devices I tested are unavailable? no, they're all up and running and available. but for some reason, Hyper can access them.

[awawa-dev]

HyperHDR waits for the answer for 500ms but it receives no answer in that period. So either they are unavailable or respond too late due to an inefficient network, or the WLED itself is busy with something at the same time and is slow to respond, which can especially happen on weak esp8266s.

[awawa-dev]

curl this address on the HyperHDR unit (or inside the container it runs on): http://192.168.1.41:80/json

[MrPresident2]

curl this address on the HyperHDR unit (or inside the container it runs on): http://192.168.1.41:80/json

as I said before, it happens with all of them, I can't even see any ip's when I'm pressing the scan network under wled setting in the hyper UI. it seems weird, all of the wled instances are esp32s, all working, all connected to HA they're up and running, but it seems like the Pi can't see them. curl also gives a connecting timeout. could it be a WLED setting?

[awawa-dev]

curl timeout is longer than 500ms I think so we can assume they are not available from that unit. Something like 'wifi isolation' on router blocks them, it must be some specific settings in your network configuration or router.