Low-Power ESP32 Battery Projects: Deep Sleep and Solar

A battery ESP32 project lives or dies on one number: average current. Get it right and a single 3000 mAh cell runs a field sensor for months. Get it wrong and the same cell is dead before dinner.

This guide covers the five power modes, every wake source, board-level sleep drain, battery sizing, solar sizing, and the mistakes that drain a pack in days. The sensor node build is covered in ESP32 Battery Sensor Node: Deep Sleep and Power Budget, and LiPo wiring in How to Power ESP32 and Arduino Projects on LiPo Power.

How long can an ESP32 really run on battery?

Battery life in hours equals usable battery capacity divided by average current. Average current is the awake share times the awake current, plus the sleep share times the sleep current. Source: ProjectECH; DroneBot Workshop; Hubble.

Take a node that wakes for 20 seconds at 180 mA and sleeps at 15 microamps, on one 18650 cell with a realistic usable capacity of 2400 mAh. Source: ProjectECH.

Report interval Average current Battery life from 2400 mAh
Every 10 minutes (180 x 20 + 0.015 x 580) / 600 = about 6.0 mA About 400 hours, about 16 days
Every 60 minutes (180 x 20 + 0.015 x 3580) / 3600 = about 1.01 mA About 2376 hours, about 99 days

Three lessons fall out of that table. First, the interval dominates: 60-minute reports give roughly 6 times the battery life of 10-minute reports. Second, sleep current matters: with a 5 mA sleep the 60-minute column collapses to about 17 days. Third, awake time is the other lever: Wi-Fi can spend 3 to 8 seconds just joining the network, so cut the awake window to 5 seconds. Source: ProjectECH.

Radios differ too: Wi-Fi transmit runs about 160 to 260 mA, BLE about 95 to 130 mA, and LoRa about 20 to 120 mA transmit with about 0.2 microamps in sleep. Source: ProjectECH; Hubble.

Which sleep mode does your project need?

The ESP32 has five power states. The figures below are chip-level typicals; your board will draw more. Source: DroneBot Workshop; Espressif sleep modes documentation.

Mode CPU and peripherals Radio Typical chip current What survives
Active On On or off 240 mA Wi-Fi transmit peak Everything
Modem sleep On Off between checks About 3 to 20 mA Everything, Wi-Fi association kept
Light sleep Paused Off About 0.8 mA RAM and registers, resumes where it stopped
Deep sleep Off Off About 10 to 25 microamps RTC memory only, 8 KB slow memory
Hibernation Off Off About 2.5 microamps Nothing guaranteed, not even RTC memory

Active is the normal running state; the only saving is lowering the CPU clock. Modem sleep turns the radios off between transmissions while the CPU keeps running, staying associated with the router by waking the radio on the DTIM interval. Light sleep pauses the CPU clock but preserves RAM and registers. Deep sleep powers down almost everything; only the RTC domain and optionally the ULP coprocessor stay alive. Hibernation is the deepest state: even the 8 MHz RTC oscillator and the ULP coprocessor are off, and RTC memory is not guaranteed. The only wake source is an EXT0 GPIO interrupt. Source: DroneBot Workshop.

What wakes the ESP32 from deep sleep?

The wake source defines the whole power profile. Source: ProjectECH; DroneBot Workshop; Hubble.

Wake source How it works Best for
Timer wake RTC timer fires after N microseconds Periodic sensing: wake, read, send, sleep
EXT0 wake One RTC GPIO goes high or low One event: a PIR motion sensor, a float switch, a door switch
EXT1 wake Any of several RTC GPIOs changes Several events at once
Touch pad wake A configured touch pad crosses its threshold A manual “report now” button on a sealed enclosure
ULP coprocessor Runs while the main CPUs sleep, about 150 microamps typical Wake the main CPU only on a threshold

Timer wake is the workhorse: call esp_sleep_enable_timer_wakeup(), then esp_deep_sleep_start(). EXT0 and EXT1 wake on a pin: EXT0 watches one RTC GPIO at one level, ideal for a PIR sensor, and EXT1 watches several. On the standard ESP32, RTC-capable GPIOs are 0, 2, 4, 12 to 15, 25 to 27, and 32 to 39. Touch wake uses the capacitive touch pins. The ULP coprocessor can poll an ADC channel or a GPIO while the main CPUs sleep and wake the main CPU only on a threshold. Source: ProjectECH; DroneBot Workshop; Hubble.

Always configure a wake source first, or the chip sleeps forever. Source: ProjectECH.

State survives deep sleep through RTC slow memory: variables declared with RTC_DATA_ATTR survive deep sleep, but not a power loss or a hard reset. Source: ProjectECH; TheLinuxCode; post 23387.

Why does your dev board never reach the datasheet sleep current?

The datasheet deep sleep figure is the bare chip. A dev board adds parts that draw current around the clock, and those parts dominate the sleep budget. Source: ProjectECH; DroneBot Workshop; post 23387.

A typical 30-pin DevKit board carries an AMS1117-3.3 linear regulator with a quiescent current of about 5 mA typical. With the USB chip, power LED, and pull-ups added, a “sleeping” dev board typically draws 5 to 15 mA. At 10 mA, a 3000 mAh cell lasts 300 hours, under two weeks. Source: ProjectECH; DroneBot Workshop.

Fix it in one of three ways: power the board through the 3V3 pin from an efficient external regulator; use a bare ESP32 module on a minimal breakout; or use a board designed for battery use. Measure the sleep current yourself first. Source: ProjectECH.

The XIAO boards stocked at QRC are the battery-friendly end of this scale, and the figures conflict across sources, so they are stated here as a sourced range, never as a single bench-tested number. Seeed’s wiki lists the plain XIAO ESP32S3 at 14 microamps in deep sleep, 2 mA in light sleep, and 27 mA in modem sleep. The XIAO ESP32S3 Sense with its expansion board attached is listed at 3 mA in deep sleep: the expansion board costs roughly 200 times the plain board’s sleep current, so detach it for a battery build and use the detachable camera only when the project needs it. The XIAO ESP32S3 Plus is listed at 33.51 microamps in deep sleep, and the XIAO ESP32C3 at 44 microamps. CircuitDigest measured a plain XIAO ESP32S3 board at 130 microamps in deep sleep, against a bare ESP32-S3 chip rating of 7 to 8 microamps. Plan with the worst figure in the range. Source: Seeed Studio XIAO ESP32S3 wiki; CircuitDigest; Embedded Nerd.

How do you size the battery?

Measure the build that will actually run from the battery. Source: UMA Technology; Hubble.

Step 1: measure each operating state. Record current in each state with a USB power meter, and use a multimeter in series with the battery lead for sleep. Source: UMA Technology; Hubble.

Step 2: calculate the average current. For each state, multiply current by time in that state, then sum and divide by the cycle time. Example: wake every 15 minutes, transmit for 5 seconds at 150 mA, sleep the other 895 seconds at 15 microamps. Average equals (5 x 150 + 895 x 0.015) / 900, which is 0.85 mA. Source: Hubble.

Step 3: divide capacity by average current, then derate. A 3000 mAh battery at 0.85 mA average gives about 3,500 hours, about 146 days. Now derate: usable capacity is about 70 to 80 percent of the label after aging, temperature, and self-discharge, so plan on about 2400 mAh usable from a 3000 mAh cell. Source: ProjectECH; Hubble; e-fm.tech.

Step 4: pick the chemistry. A standard LiPo at 3.7 V is workable for 6 to 12 month projects. A LiFePO4 cell at 3.2 V has low self-discharge around 3 percent per year, so it suits solar recharging. A CR2032 at 220 mAh suits only the lowest-power applications. Source: Hubble.

The biggest lever is the awake time: every second of Wi-Fi connect time at 150 mA costs as much as 150 seconds of sleep at 1 mA. Source: post 23387.

How do you size a solar panel for an ESP32 project?

A solar panel only has to replace what the board uses, plus the charging losses. Size it from the worst month, not the average: a panel sized for summer sun dies by mid-December. Source: Hubble solar sizing guide; e-fm.tech.

Step 1: daily energy. Daily energy equals average current times supply voltage times 24 hours. The 0.85 mA node at 3.7 V uses about 76 mWh per day. Source: Hubble solar sizing guide.

Step 2: battery autonomy. Size for three cloudy days: three days at 76 mWh per day is 228 mWh, or about 62 mAh at 3.7 V. Source: e-fm.tech; post 23188; post 15185.

Step 3: worst-month peak sun hours. Peak sun hours are the hours per day of full sunlight that would deliver the same energy as the real day. Look it up for your coordinates with PVGIS or NASA POWER, and use the worst month. Source: e-fm.tech.

Step 4: panel watts. Panel watts are about equal to daily energy divided by (charging efficiency times peak sun hours times a derating factor). The worked example comes out to about 0.021 to 0.11 W. In practice, fit a panel several times larger than the paper minimum. Source: e-fm.tech; Hubble solar sizing guide.

Step 5: charge controller. A small panel charging a single lithium cell needs a charger that terminates at 4.2 V and a protection circuit. The TP4056 module below charges a single cell from USB or a solar panel at up to 1 A. Standard lithium-ion and LiPo cells should not be charged below about 0 degrees C. Source: ProjectECH; e-fm.tech.

No solar panel is stocked at QRC as of 2026-11-21, so no panel is linked in this guide. The BirdBox build in Run a BirdBox Camera for Months on Solar Power shows the same pattern: panel in full sun, short cable, battery sized for three cloudy days.

How do you charge and protect the pack?

Charging, protection, and regulation are three separate jobs, and one module does not always do all three. The full wiring chain is covered in How to Power ESP32 and Arduino Projects on LiPo Power. Source: post 19087.

The TP4056 load-sharing trap. The TP4056 has no load sharing: it cannot tell current going into the battery from current drawn by your circuit. With the load on the battery terminals, the charger sees the load current as charge current, never detects the proper termination taper, and can keep pushing current into an already-full cell. Wire battery to B+ and B-, supply to IN+ and IN-, and take system power from OUT+ and OUT-. The proper fix is a load-sharing power-path circuit. Source: ProjectECH; post 19087.

The cutoff voltage has no single agreed number. Sources disagree on the per-cell cutoff, with figures from 3.0 V to 3.5 V per cell. This guide states that range and does not pick one number. Read the cutoff from the docs for the protection module and the battery you own, and wire the protection so it disconnects the pack from everything. The stocked 3000 mAh pack below has a built-in protection board. Source: post 19087.

What mistakes drain a battery pack in days?

  • Trusting the chip sleep figure for the whole board. The chip sleeps at 10 to 25 microamps; the board sleeps at milliamps. Measure the whole board.
  • Leaving Wi-Fi on between readings. A board that idles with Wi-Fi connected draws 35 mA or more. Sleep between readings.
  • Letting Wi-Fi join slowly, every cycle. Every awake second at 150 mA costs as much as 150 seconds of sleep at 1 mA. Use a static IP and cap retries at three.
  • Sizing the solar panel for summer. The panel must cover the worst month, not the average. Size from worst-month peak sun hours, and test through a cloudy week.
  • Never measuring the sleep current. Every battery estimate in this guide is arithmetic from stated inputs. Measure your own board’s sleep current and redo the math.

How do you fix a low-power project that dies too soon?

The board draws milliamps in deep sleep. Measure the board alone, then the regulator or converter alone. The likely causes are the power LED, the USB-to-serial chip, or a regulator with high standby draw. Power the 3V3 pin directly from a regulated 3.3 V supply, or remove the power LED where the board allows it. Source: DroneBot Workshop; post 23387.

The node boot-loops when the battery gets low. A nearly empty cell sags under a Wi-Fi transmit burst, and if the sag crosses the brownout threshold the chip resets mid-transmission. Treat 3.2 to 3.3 V under load as the effective empty point. The brownout fix is covered in ESP32-CAM Troubleshooting: Brownout and Camera Init Failed. Source: ProjectECH.

The battery voltage falls every week even with solar. The panel is too small for the worst month, the panel is shaded or flat, or the charge current never tapers. Check the battery voltage after the first week, and add panel size if it keeps falling. Source: post 23188; ProjectECH.

Which low-power setup fits your project?

Project Wake source Sleep mode Battery Solar
Temperature sensor, hourly reports Timer Deep sleep 3000 mAh 1S LiPo pack Not needed
PIR wildlife or BirdBox camera EXT0 on the PIR output Deep sleep 3000 mAh pack or larger Yes, worst-month panel
Always-on display or dashboard None, it must stay awake Modem sleep between updates USB power bank or mains No, the radio stays too busy
BLE beacon Timer, duty-cycled BLE scan Deep sleep between scans XIAO board with on-board charging Optional

Parts used in this guide

Prices and stock verified live on 2026-11-21. All four items below are in stock and purchasable.

Also verified live in stock: XIAO ESP32C6 1-Pack (ID 17835) $15.99 sale; XIAO ESP32-C5 1-Pack (ID 18380) $17.99 sale; XIAO ESP32S3 Sense 1-Pack (ID 17842) $32.49 sale, detachable camera; ESP32 DevKit V1, $9.99 sale; USB-C LiPo Module 1200mAh (ID 18959) $14.99 sale; HC-SR501 PIR (ID 14636) $5.99 sale; CellMeter8 (ID 3485) $19.99. No solar panel is stocked at QRC, so none is linked.

Shipped fast and securely from our secure facility in Queensbury, NY. QRC ships within the USA only.

Related guides

FAQ

How long will an ESP32 run on a battery? It depends on the average current, not the pack size alone. A node that wakes 5 seconds at 150 mA every 15 minutes and sleeps at 15 microamps averages about 0.85 mA, so a 3000 mAh battery gives about 146 days. Source: Hubble.

Why does my ESP32 use milliamps in deep sleep? The datasheet figure is the bare chip. The dev board adds a linear regulator with about 5 mA quiescent current, a USB-to-serial chip, and a power LED. Source: ProjectECH; DroneBot Workshop.

What wakes an ESP32 from deep sleep? The RTC timer for periodic work, EXT0 for one pin event such as a PIR sensor, EXT1 for any of several pins, a touch pad for a button, and the ULP coprocessor at about 150 microamps. Source: ProjectECH; Hubble.

How big a battery do I need for an ESP32 sensor? Work out the average current first, then divide capacity by average current, then derate to about 70 to 80 percent usable. Source: ProjectECH; Hubble.

Can I run an ESP32 on solar power? Yes. Work out the daily energy, size the battery for three cloudy days, look up the worst-month peak sun hours, and divide daily energy by charging efficiency times peak sun hours times a derating factor. Source: Hubble; e-fm.tech.

What is a safe cutoff voltage for a LiPo on an ESP32 project? No single cutoff voltage is universal: sources disagree, with figures from 3.0 V to 3.5 V per cell. Use a protected pack or a protection module, read the cutoff from its docs, and wire it so it disconnects the pack from all loads. Source: post 19087.

Sources

Last updated: 2026-11-21