ESP32 dev boards draw 5-20 mA in deep sleep because the USB-serial chip, power LED, and voltage regulator stay powered, making battery-operated IoT prototypes die in hours instead of months

Every ESP32 development board — the DevKitC, NodeMCU-32S, WROOM modules on breakout boards — includes a CP2102 or CH340 USB-to-serial converter, a power LED, and a linear voltage regulator that remain powered even when the ESP32 chip enters deep sleep mode. Espressif's datasheet claims 10 uA deep sleep current, but real measurements on stock dev boards show 5-20 mA, which is 500-2000x higher than advertised. A CR2032 coin cell or pair of AA batteries that should last 2-3 years on paper drains in 8-20 hours. This matters because the entire promise of ESP32 for hobbyist IoT — wireless sensor nodes, weather stations, mailbox notifiers, soil moisture monitors — depends on running for months on a single battery charge. When a maker prototypes on a dev board and gets 12-hour battery life instead of the expected 6 months, they face a brutal choice: desolder the CP2102 and LED (voiding any ability to reprogram over USB), design a custom PCB (which requires weeks of learning KiCad and $30-50 for a fab run), or buy a specialized low-power board from a third party that may lack community support and documentation. Most hobbyists abandon the project at this stage because the gap between 'blink an LED on a dev board' and 'deploy a battery-powered sensor' is a cliff, not a slope. The problem persists because Espressif designs dev boards for ease of development and debugging, not for deployment. The USB-serial chip is essential during development for flashing and serial monitoring. Removing it would make the board harder to use for beginners. But Espressif provides no official low-power dev board variant, and the third-party ecosystem (TinyPICO, Unexpected Maker boards, FireBeetle) is fragmented with different pinouts, libraries, and documentation quality. There is no standard 'dev mode with full debugging' to 'deploy mode with minimal power' switch on any mainstream board, so every battery-powered ESP32 project requires custom hardware knowledge that most makers don't have.