Briefly an LED control program that can be installed on the 2 mentioned chips. Covered in many articles and YouTube videos. This is just a brief overview and mention of some specific problems encountered not otherwise well documented.
The most common method of installation is to use the WLED web site while the chip is connected to the computer via USB port. For the most part, this goes smoothly and the prompts will guide you to serial port drivers if any are needed and then configure wireless network connections.
For ESP32 chips, hold down the EN button before you connect and release it once the installation starts. I’ve seen posts and videos stating use the boot button. That also works but you have to be sure to hold it until it says erasing, not just installing.
Specific to the NodeMCU ESP8266, it may require you to download and install the CH340 driver before it can connect over the serial port. A reboot was not needed. There are other sources on line of the same driver but some don’t work. Other chips may require a different port driver or not need a driver. To get to the drivers, just select “No device found” on item 2. Apple laptop security won’t permit this file to install but, so far, it hasn’t been necessary to add it, the Apple laptop natively supported the chip connection. Twice I’ve had a Windows computer require the driver to be reinstalled after an update and reboot.
Once WLED is installed, you can set up a local wi-fi access point under config>wifi setup > scroll down to “configure access point”. For the access point to be available, select “Always” in the “AP opens” box. It shows as WLED-AP as default name in the list of wireless connection points. From here it gets a little confusing. Select it as your wi-fi service. If you are using an Android phone and the chip is connected via USB to a computer, when you select sign-in, no password is needed even if you set one. The sign-in dumps you directly into the control page. If the chip is not connected to a computer, a sign-in with password is needed. The default password is “wled1234”
Some cases I prefer to use only the WLED-AP for unit control. There is no encryption on passwords saved on the chip. If the unit is outside, it’s possible for someone to get the users home wi-fi password and SSID if the unit is stolen.
The WLED app works to connect to the chip on the same subnet. I have not had success in connecting across subnets. Even on the same subnet, the discover process may not work. Easiest to just enter the IP address taken from the “wifi setup” on the configuration page when you initially set up the access point.
There are other installers which can be used to install the binary and configure the wireless network later. I’ve used this when I want to have only the user’s wireless network configured on the chip since the password is stored unencrypted in the EEPROM or I want a different program installed. ESPEasyFlasher is specific for the ESP8266. Download the WLED binary and flash the chip. Exspressif has others for the ESP32 WLED. There is also ESPhome-flasher. Deprecated on Jul 3, 2023 but still good for this. Advantage of no fiddling with buttons and it will install any binary file, not limited to WLED.
Jerry's blog 