I am having the same issue today. Completed my installation of lights two days ago. WLED ran fine then but was only accessing directly to its web page. Started testing via HA yesterday. Was fine when I quit for the day. Today, no access at all.
I notice that HA diagnostics log says the minimum version is 0.14. I am running .13.3 and thought that was the latest.
Before all access was via my laptop. Yesterday I was switching between accessing via my desktop, laptop, and phone
Before I quit yesterday I was doing a lot of work on segments.
What router brand do you have ? It seems that there is something very pecular with ASUS (possibly ASUS mesh that I am using) and the ESPxxxx wifi binary (closed source)
I have the symptoms on both an ESP8266 running WLED 0.13.3 as well as an ESP32 running ESPHome ble_gateway.
My router is supplied by Xfinity. My QuinLed-Uno is connected via ethernet to a TP-Link switch. The Switch connects to the Xfinity router (Wifi Access point, Modem, router and all that package of stuff). At this point WLED seems to come on line for a few seconds after powering up. Then goes off line. Router show it not on the network, but as device it know about that is not accessible.
Not sure if you have such setings but I have now disabled “IGMP snooping” after seeing an ASUS thread on the matter where they had success and it indeed seems to have brought stability to my ESP8266 and ESP32 modules - No more disconnects !
Similar issue with two different brand WLED modules (both ESP32). After some period of time WLED stops responding (even to ping). Access point shows it as inactive (disconnected). All Unifi networking equipment. I have multiple Tasmota devices, none of which have issues. Also, one of the ESP32 modules I’m using I’ve used previously for my own application and it never dropped off the network, so this appears to be something specific to WLED or its libraries.
I do use HomeAssistant, but I disabled the WLED integration and it didn’t seem to make a difference.
I guess I’ll use this as an opportunity to learn how to attach a debug probe to an ESP32 and debug it.
New addition:
I now have some evidence that the problem only occurs (or is made worse) if I have more than one WLED device on the wireless network at once. If this is the case, it would likely be a problem with the ability of WLED devices to find each other on the network, and may be influenced by mDNS and broadcast settings on the wireless network. A workaround is to find mDNS and broadcast settings for the wireless network that allow device discovery to work or to turn off mDNS and everything to do with Sync groups on the WLED devices.
I consider this to be a workaround because even if the network does not allow device discovery, the WLED devices should continue to work, simply without this ability.
After making some changes to my network to enable mDNS and make sure UDP broadcasts would get through to the WLED devices, everything is now working reliably. The devices have also been re-integrated into HomeAssistant and that works properly as well.
@keck9939 this is interesting, I have quite a few devices, around 8 or 9, and all was well… until it wasn’t. All are running beta… but suddenly none of them are available on the network. I was playing with router settings, but if you could give a bit more context around what enabling mDNS entails, I’d appreciate any help in debugging.
What is involved in enabling mDNS and UDP broadcasts (over WiFi) will depend on your networking equipment. I suspect that on most consumer grade equipment these are enabled by default. The Unifi equipment I use disables them by default. You will need to refer to the documentation for your equipment to see if they are default enabled or not and how to enable them if not.
I checked my router )TPLink Archer A6) settings and UPnP was checked on. I turned it off then on again and I can now access the “visit” setting in WLED integration; but no dice on the phone app - weird. I anticipate failure again though. I had been able to power off and on the ESP8266 (MCU) and a little while later both seemed to work (from memory). May actually be a coincidence but I checked maybe 2 minutes before cycling UPnp in router and it wasn’t able to access the chip. If it happens again - and no doubt it will - I’ll go directly to the router if possible. I had an automation to turn the plug feeding the ESP board off and on but don’t think that will work anymore. I will have it notify me as soon as it becomes unavailable next time. after it cycles chip power.
I wish that could be my problem but my Archer A6 (consumer grade?) router doesn’t seem to have a mDNS setting. I’m thinking about changineg to OpenWRT firmware so maybe that will have it. Thanks anyway though
Update: I did find a setting in WLED configuration saying
“mDNS address (leave empty for no mDNS):
http:// wled-e2e91d .local
Client IP:192.168.1.225”
and I also noticed that while my router has the WLED chip setup for static IP the setting for that in WLED config was blank. Hoping that putting in the staic IP and gateway IP (router) helps. If not I’ll try removing the mDNS address that WLED must’ve filled in by itself