The delay is not the cleanest solution, it would be better to check the state of the wifi hardware but I have no idea what to check. Walkthrough The modification in this change introduces a 5-millisecond delay in theWLED::initConnection()method of thewled00/wled.cppfile immediately after ...
the idea is to let power stabilise for a little longer before hardware initialisation, this seems to help with some setups that have issues with wifi not connecting at bootup. On two of my setups that have issues with wifi at boot, this helps. It looks like you picked the wrong branch...
Control WS2812B and many more types of digital RGB LEDs with an ESP8266 or ESP32 over WiFi! MoonModules adds features on top of upstream. - WLED/wled00/wled.cpp at 5e20f94b8e93b9076911e4017f84d96544b4d53b · MoonModules/WLED
userSetup()is called after loading settings but before connecting to WiFi. Use it to start own interfaces if it does not depend on WiFi (IR, Sensors, GPIOs,...). Also you can use it to load custom settings or to specify own server pages with theserver.on()method. userConnected()is ...
I think this would be very useful when connecting with home automations systems to detect and react on button events. My idea would be to connect a motion detection sensor as my WLED button. Depending on the time of the day I would like to run different effects on my WLED controller. So...
DEBUG_PRINT(F("Connecting to ")); DEBUG_PRINT(clientSSID); DEBUG_PRINTLN("..."); // convert the "serverDescription" into a valid DNS hostname (alphanumeric) char hostname[25]; prepareHostname(hostname); #ifdef ESP8266 WiFi.hostname(hostname); #endif if (WLED_WIFI_CONFIGURED) { DEB...