i know this is an old thread but i got one of these yesterday, and flashed via web installer (check ethernet). rebooted, connected to wled-ap, under wifi select wt32-eth01. DONT enter wifi info, save, log into your router, check attached devices to find IP, good to go.
it wont show up in the app, for me at least, but i think that might be something related to one ui 5 update on android. app crashes now when searching for lights even after clearing data/cache.
I have the same problem. I flahsed through we and many other flashing tools. Can’t get wled ap to show in the network list.
Any solutions?
Make shure you have a good psu on it. This thing draws amps to boot.
I have a WT32-ETH01 and had no issues flashing it from the WLED website installation tool.
Booting has never been an issue on mine, I use GPIO2 to run the relay and GPIO’s 12, 14, and 15 as LED outputs. My outputs are fed to an RS485 transmitter which sends a differential signal down some cheap Cat5e to a RS485 receiver on the other end of the run. That then sends the binary signal the last 6 feet to the light strings.
The only issue I had with the WT32 (and other ESP32’s) was Home Assistant polling the presets too often causing the module to lock up. Once I removed them from Home Assistant they work great. All I was using HA for was to turn them on and off, so I used the MQTT command in an automation and it works without a hiccup.
I plan on using more of these as I install my other year-round lights on the house.
I use the shown usb to ttl converter and try to flash wled with the install webpage: USB zu TTL-Konverter-Modul mit eingebautem in CP2102: Amazon.de: Computer & Zubehör
I always get errors…
Does anyone know, how to connect this usb board to the WT32-ETH01 correctly?
Thanks for the excellent guide, I flashed 0.14.0-b2 ethernet and it’s working fine! 
I could not get the Windows flasher to work, getting efuse error of some sort. But the command line method I normally use worked perfectly (esptool-master).
Here’s the commands if anyone needs them:
To flash bootloader (first time only):
python esptool.py write_flash 0x0 ./esp32_bootloader_v4.bin
To flash firmware:
python esptool.py write_flash 0x10000 ./firmware.bin
FWIW, I had the same issue, I could flash WLED onto my board using both the Web install portal or even compiling from source using PIO. But afterwards, I couldn’t find the WLED-AP network to set it up.
The issue was that the USB board I was using didn’t have enough power to allow WLED to boot up I think, so disconnected everything and directly connected the board to my main power supply and the WiFi showed up immediately.
HI All
Just in case it helps anyone who want to use these boards for WLED.
I want to use these boards in hard to reach places for wifi for WLED.
I have WT-32-ETH V1.4 - and was experiencing all these issues reported, booting issues, and tried the capacitor hack with no success.
Here is the method i used to get it working flawlessly.
Flashed wled ethernet from install.wled.me
Connected via the AP “WLED-AP”
Changed the LED settings straight away - changed the default GPIO pin from 16 to 2 (for my board) and rebooted - this i think is KEY - as GPIO16 is used for the ETH module?
I then (while connected to the AP) went to Wifi settings and removed the Wifi access point name to connect to (left it BLANK) and at the same time, selected the ethernet type option lower down to WT32-ETH01.
The saved at this point, and the eth interface came up, and was correctly DHCP addressed.
I then carried on and configured as normal for my requirements.
All the above was done on a TTL 3V adapter before being transferred to my WLED board with proper 5V 4A power.
I have tested this board via automation, and had 100 reboots (power has been CUT and then reapplied) with no booting issues, and IP connectivity everytime.
Hope the above helps someone!
Cheers
Mike
Hey I just registered to share my thoughts, first of all:
I tried several times, with several WT32-ETH01 Boards none of these worked by ethernet, just wifi
→ Always just used the install.wled.me page. Flashing was never an issue, also never had these boot issues or something else
I really wanted to make this work to create a very easy and cheap Artnet Node for LED Strips with Ethernet. Worked perfectly with wifi, but the ping is to slow for this. (+ I really like the idea that my controller can do effects on his own without pixel mapping stuff).
The 2 Leds of the ethernet port were NEVER working, just when I connected LINK and GND the LINK-LED switched on. But it did the hole time, even when there was no Ethernet Connection. The ACT-LED also never worked.
In my opinion most of these boards which are available don’t work, I see the “mistake” not on wled-side, I think these boards are just a pain in the *** 
I gave up on these WT32-ETH01 and bought a QuinLED-Dig-Octa and this was “plug and play”. Flashed via install.wled.me, connected to wifi, set up 5 strips, choose the right ethernet mode, made my dmx settings → Started resolume, changed the IP and everything worked since I mapped it already via wifi. Ethermet working perfectly (DHCP). After all this hours I spend on this… I really can recommend that board it’s just nice and works how it should be. 30 Dollars super nice price for what you get (+ shipping from china and taxes…).
Fun fact: Most of the videos you can find about this controller is just showing how to flash and then showing the wifi connection. I never saw on of these boards working with ethernet. I’m still hoping inside of me that it will work one day. atm I don’t see any the difference in a 7€ Wifi Controller and a 20€ WT32-ETH01. The cheaper 7€ controller has more GPIOs which is a point for…
Cheers
Dennis
FWIW I have about 15 of them working just fine with Ethernet. Add the 1uF ceramic cap between EN and GND and make sure to actually enable Ethernet in settings.
