WLED integration does not find HOST

Dominicd · January 4, 2023, 10:13am

First post on the Community… so hi everyone !

I am struggling getting WLED integrated onto HA.
Here is my configuration:
HA installed on a RPi through ethernet on my main network: 192.168.1.46:8123.
WLED installed after a WIFI router and gets its DHCP address 10.0.4.33
WLED accessible from my Phone, no issue here.

if I make a ping to WLED from anywhere from any laptop connected on the WIFI router network, WLED responds positively (normal)
if I make a ping to WLED from anywhere from the main network, WLED responds positively

But when I try to add the WLED integration on HA and enter HOST, I get an error “failed to connect”

Any help will be appreciated.

PS: my router does not support mDNS.

nickrout · January 4, 2023, 10:33am

From your ha instance can you ping the wled device?

What does traceroute say?

Dominicd · January 4, 2023, 10:40am

Thanks Nick, will investigate Traceroute: I first need to learn how to use such tool from my Rpi !

nickrout · January 4, 2023, 11:26am

Same as ping.

Dominicd · January 4, 2023, 1:45pm

This is ok, but problem is that HA installed is installed on a standalone Rpi device connected on Ethernet to my network with no keyboard, no mouse, nor display. If I hook up a keyboard+mouse+screen, can I interrupt current functionning to get access to the UI interface to launch traceroute somehow ? Sorry, I think I need some Linux training…

tom_l · January 4, 2023, 1:53pm

Install the web terminal and ssh addon.

Dominicd · January 4, 2023, 5:26pm

Thanks Tom ! indeed, now I get it to work. Using traceroute suggestion from Nick, it looks like instead of staying inside my network, the wled host address traceroute goes out of somewhere !..

nickrout · January 4, 2023, 8:53pm

Looks like your fritz router needs a route set to the 10. network.

Dominicd · January 5, 2023, 2:53pm

Thank you Nick. Following your advice, I created a static route that seems to work now.
I made good progress as traceroute does not show error anymore, but WLED integration still fails to connect:

If you have any idea, let me know. Thanks again.

nickrout · January 6, 2023, 5:11am

Improvement maybe, but the traceroute does not make it as far as 10.0.4.33, it ends at 192.168.1.32.

Dominicd · January 6, 2023, 11:32am

Thank you Nick, I changed the location of the WLED with a different subnet and it works now: looks like my wifi router (EERO) is blocking the comm for the HA at one point because making a traceroute from another PC on the same subnet than where the RPi is located was working fine. Anyway: get my access to WLED now. Thanks again !

JohnW1 · October 10, 2024, 10:15am

I compared my other working wLED strips to my “bad” one not being discovered in HA. I had to change the “bad” wLED node from fixed IP to 0.0.0.0 as well as the same for the gateway (this now matches how the other good nodes are setup in wLED). Went back to HA after that, opened wLED integration, and the “bad” node was automatically discovered.

I am running formerly “bad” node on wLED v0.15.0-b5 and HA OS core 2024.10.1 on a RPi 4.

HAnewbie555 · January 31, 2025, 4:11pm

I have the exact same issue.

HA can traceroute and ping the IP of my WLED, but fails to add it, nor discover it automatically. Web GUI works fine.

I have tried to flash ESP8266 modules with WLED in the past and they showed up automatically in HA without issues, so this is strange.

I tried to update it to 0.15 OTA, but without any success. Tried every binary available on Releases · Aircoookie/WLED · GitHub.

Tried to update and restart HA but no difference.

WLED reports the followng:
v0.14.0-b1 “Hoshi”

Build	2212222
BuildTime	2023-05-26 12:57:31
Restart Reason	Software/System restart
Signal strength	74% (-63 dBm)
Uptime	5 min, 22 sec
Free heap	18.2 kB
Flash Size	2048 kB
Estimated current	Not calculated
Average FPS	3
MAC address	D8BC388CF64C
Filesystem	32/499 kB (6%)
Environment	esp8266 2_7_4_7 (1)

What other steps can I test?

nickrout · January 31, 2025, 8:20pm

Try running (on a linux machine)

avahi-browse -rt _wled._tcp.local

HAnewbie555 · February 1, 2025, 7:37pm

Only Linux machine I have is HA.

apk add avahi did install avahi and avahi-libs, but not able to run avahi-browse, “not found”. Do I need to be root?

Running ‎Discovery - DNS-SD Browser on the App Store on my iPhone finds it

wled-8CF64C._wled._tcp.local.

wled-8CF64C.local:80
192.168.1.175:80

mac = D8BC388CF64C

nickrout · February 1, 2025, 8:22pm

Seems like ha should find it

github.com

home-assistant/core/blob/f5fd49d8cb710c95cde30fc5071c20af351760b4/homeassistant/components/wled/manifest.json

{
  "domain": "wled",
  "name": "WLED",
  "codeowners": ["@frenck"],
  "config_flow": true,
  "documentation": "https://www.home-assistant.io/integrations/wled",
  "integration_type": "device",
  "iot_class": "local_push",
  "requirements": ["wled==0.21.0"],
  "zeroconf": ["_wled._tcp.local."]
}

HAnewbie555 · February 1, 2025, 8:58pm

Indeed, and it has in the past.

Can I somehow uninstall the integration, flush some cache, manually add it to list of discovered devices?

nickrout · February 1, 2025, 9:10pm

Make sure you didn’t accidentally ignore or disable it first.

HAnewbie555 · February 1, 2025, 9:19pm

Ignored
No ignored integrations

Disabled
No disabled integrations

Unsolder the ESP module and replace with another flashed with 0.15?

nickrout · February 1, 2025, 9:24pm

I don’t think you need to unsolder it to flash it.