I currently use 2 subnets for home automation. Lights are on their own subnet separate from home assistant. When I put the IP of WLED it is unable to connect on this other subnet. Now I know I can reach that subnet from home assistant as I have many other lights on it and have it integrated but not WLED. Any suggestions or maybe I’m doing something wrong.
i’m using separate subnets for my devices, too.
they are routed, but restricted by firewall to one-way (internal -> IoT) for initial connections.
this works well with the web-UI. not using home assistant, though.
1 Like
I’m not a specialist in networking, but there is often a NAT or similar subnet separation in place, so that devices in one subnet cannot be accessed by devices in the other one. This doesn’t seem to be the issue here though as you can access other devices in your lights subnet.
If you connect a testing device to the light’s subnet, can it reach the WLED device? (just making sure that it actually connects)
1 Like
Yes I can. That’s why I found it strange. I have a ton of ESPHome devices on that subnet as well and can get to them from home assistant so mDNS is working as well across them. I’ve got a degree in networking and have been a sysadmin for a long time just have no skill to jump in to the code and see anything that may or may not be wrong.
There is no blocking firewall rules between the two subnets. Only thing blocked on that subnet is internet access. Data routes properly between them without anything in the way.
Are you using a smart phone / tablet to access WLED via the app, or using a web browser (either on a smartphone / tablet, or PC)?
If you are not using a smartphone, try it. If you are not using a browser, try it.
Are you able to ping the device, and does it show up on your router? I know you did all these things, but answering the questions may help others understand the problem better.
1 Like
So I accessed it via my desktop (same subnet as homeassistant but different than WLED). I can ping the device just fine. It does show up in the router and I set it to use a reserved IP which it did successfully. I was also able to access it on my smart phone as well.
Does the ability to connect to your wled device from multiple devices resolve your problem? Or is it just the wled app that cannot find it? I think the wled discover protocol isn’t routable across subnets.
1 Like
So the home assistant integration is the only thing not working for me. I guess I didn’t think of it being discovery of devices when you have to give it an actual IP address of the device for each instance of WLED you have on your network. That actually may be the issue if it’s indeed doing that. The next question is can it be resolved since it is accessible by home assistant it should be accessible by the integration I would think.
edit: BTW I’m really happy with the community here and their willingness to try and help.
If your subnets are configured so all you need is a simple subnet mask change to ping across subnets without “routing”, like 192.168.200.n and 192.168.201.n, if adjusting the mask on home assistant network adapter allows the integration to work, there’s kind of your answer. Maybe?
1 Like
Also, for the full HA integration, I believe that includes automated discovery (from what I’ve read / heard). I do not use HA so do not know first-hand.
1 Like
I have a similiar issue, I cannot get to the wled web page or by using the app from my phone, which is wifi to wifi, but i can get to the webpage from any ethernet (copper link) connected device. I am running unifi hardware. I dont understand why my phone cannot access the wled interface even on the same wifi network. Any ideas what I did wrong? I think this got broken after an update, but I did try the special version .10 with the 2.5.2 arduino core, and still no luck.