Coin Cell vs LiPo vs AA: How to Choose a Battery Chemistry for Your BLE Device

Most BLE products don’t die because of bad firmware or a weak antenna. They die because someone picked the wrong battery six months earlier and designed everything else around it.

Here’s what typically happens: you prototype on a dev kit powered by USB, grab a CR2032 coin cell because the reference design uses one, stuff it into your first enclosure, and ship beta units. Three weeks later, devices in the field start browning out during TX bursts. Or your logistics partner calls to say they can’t ship your LiPo-powered units to the EU without dangerous goods paperwork you never filed. Or your “2-year battery life” claim turns into 9 months because you sized capacity using datasheet numbers that assume conditions your product never operates under.

The battery isn’t an accessory. It’s an architecture decision that constrains your PCB layout, enclosure dimensions, BOM cost, certifications, user experience, and retail packaging. Choose well, and every downstream decision gets easier. Choose poorly, and you’re redesigning your enclosure at the worst possible time.

This guide gives you a concrete framework for choosing between the three batteries that power the vast majority of BLE products: CR2032 coin cells, LiPo rechargeable packs, and AA/AAA primary cells. Every recommendation is anchored to real BLE current profiles, not theoretical chemistry.

What BLE Actually Demands from a Battery

BLE doesn’t draw steady current. It operates in short, sharp bursts, and that pattern matters enormously for battery selection.

Current
(mA)
  8 |    __          __          __
    |   |  |        |  |        |  |
    |   |  |        |  |        |  |
  0 |___|  |________|  |________|  |____
    0   2ms  1000ms  1002ms      2002ms
                  Time -->

    [sleep: ~5µA]  [TX burst: ~8mA for 2ms]

A typical BLE SoC like the nRF52832 draws around 5µA sleeping and 6–10mA during a transmit burst lasting 1–3ms. At a 1-second advertising interval, that averages out to roughly 10–15µA. Seems tiny. But those peaks are what kill you.

Three electrical parameters decide whether your battery can handle the job: peak current (can the battery deliver 8–15mA without its voltage collapsing?), average current (this determines total runtime), and operating voltage range (most BLE SoCs brown out below 1.8–2.1V).

Average current alone is misleading. A battery with plenty of capacity but high internal resistance, meaning it resists current flow during sudden demand, will voltage-sag under pulse loads and reset your SoC. This is the single most common battery-related failure mode in BLE products.

The Three Contenders at a Glance

*Derated significantly at cold temperatures and over discharge life.

One critical note: the 220–240mAh capacity on a CR2032 datasheet is measured at a continuous 0.2mA drain. Your BLE device, with its pulsed load, won’t extract the full rated capacity. Real-world usable capacity is typically 50–70% of the number on the package.

CR2032 Coin Cells for BLE: The Default Choice (and Its Hidden Limits)

Everyone reaches for the CR2032 first, and often that’s the right call. It’s tiny (20mm × 3.2mm), costs under $0.40, outputs 3.0V that neatly matches most BLE SoC voltage ranges, and enables ultra-slim enclosures. If you’re building a BLE beacon, just use a CR2032. Don’t overthink it.

But here’s where developers get burned: the pulse current ceiling.

CR2032 cells have internal resistance of roughly 15–40Ω, and it increases as the cell ages and as temperature drops. When your BLE SoC demands a 10mA TX burst, that internal resistance causes voltage sag:

Voltage (V)
 3.0 |━━━━━━━━━━━━━━━━━━━  Fresh, no load
     |
 2.7 |─ ─ ─ ─ ─ ─ ─ ─ ─   Under 5mA pulse (OK)
     |
 2.2 |. . . . . . . . . .  Under 15mA pulse (danger zone)
     |
 1.8 |╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌  BLE SoC brownout threshold
     +━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
       Fresh            50%           End of life

A fresh CR2032 at room temperature handles 10mA pulses fine. A half-depleted cell at 0°C? That same 10mA pulse can drop voltage below the brownout threshold and reset your device. This is especially treacherous because it works perfectly on your desk during development.

Best for: BLE beacons, asset tags, simple temperature/humidity sensors advertising every 1–10 seconds, Bluetooth buttons with infrequent presses.

Concrete runtime examples: A BLE beacon advertising at 1-second intervals (~12µA average) gets 18–24 months. A BLE sensor establishing a connection every 30 seconds to transfer 20 bytes gets roughly 8–14 months.

Watch out for: Any profile requiring sustained connections, OTA firmware updates (those prolonged high-current transfers are risky on a coin cell), and cold environments below 0°C.

LiPo Batteries for BLE Devices: Power and Complexity

When your BLE product needs more data throughput, a screen, GPS, or sensor fusion, LiPo is the answer. Capacities from 100mAh to 10,000mAh+, excellent pulse current delivery (easily 1A+), and rechargeability make LiPo the only realistic option for demanding BLE applications.

What LiPo unlocks: Connected BLE profiles like HID (keyboards, mice), audio streaming, GPS + BLE combinations, and frequent OTA device firmware updates without worrying about brownout.

The complexity tax is real. A LiPo doesn’t just snap into a holder. You need a charge management IC (something like the MCP73831, ~$0.50), fuel gauging for battery level reporting, protection circuitry against over-discharge and over-charge, and a USB or wireless charging interface. That’s additional PCB area, BOM cost ($1.50–3.00 in added components), and design validation.

Then there’s the production surprise nobody warns you about: LiPo batteries are classified as UN3481 dangerous goods. Shipping finished products containing lithium polymer cells internationally requires specific packaging, carrier-approved labeling, and in many cases, UN38.3 testing certification. This adds $2,000–5,000+ in compliance costs and real lead time. Startups doing their first production run routinely get blindsided by this.

Best for: Wearables, BLE-connected devices with displays, high-throughput sensors, any device needing regular OTA DFU.

Concrete runtime examples: A BLE fitness band with a 150mAh LiPo, connected profile active 8 hours/day at ~500µA average, lasts 5–7 days between charges. A 400mAh LiPo environmental sensor connecting every 5 minutes gets 6–12 months.

Watch out for: Cell swelling over time, calendar aging (LiPo cells degrade even sitting on a shelf), poor performance below 0°C, and user expectations that “rechargeable” means infinite life. Most LiPo cells deliver 300–500 full cycles before meaningful capacity loss. Also factor in EU WEEE e-waste regulations for products with embedded rechargeable batteries.

AA/AAA Batteries for IoT: The Boring Powerhouse

Nobody puts AA batteries on their pitch deck. They’re not sleek. But they are the dominant power source in deployed IoT sensors for excellent reasons.

Raw capacity wins: Two AA Energizer Lithium L91 cells deliver 3,000mAh at 3.0V nominal. That’s more than 12x the usable capacity of a CR2032, with peak current capability exceeding 500mA. You’ll never brownout a BLE SoC on AA lithium primaries.

Users understand them. No charging cables, no USB ports, no “is it dead or just not charged?” support tickets. The battery dies, the user opens a door, swaps two AAs, and moves on. Your customer support cost for battery-related issues drops to near zero.

Pay attention to the distinction between lithium primary AAs (e.g., Energizer L91) and alkaline AAs. Lithium primaries have a flat discharge curve (steady voltage until nearly empty), work down to -40°C, and have shelf life exceeding 20 years. Alkaline cells are cheaper but their voltage sags progressively under load, and they can leak corrosive electrolyte that destroys your PCB contacts over multi-year deployments. For any product targeting 2+ year battery life, specify lithium primaries.

Best for: Home sensors (door/window, motion, environmental), industrial asset trackers, agricultural monitors, anything where multi-year battery life matters and slim form factor doesn’t.

Concrete runtime example: A BLE door sensor that advertises on events plus a 1/minute heartbeat, drawing ~15µA average, will last 4–5+ years on two AA lithium primaries.

Watch out for: Size. A 2xAA battery holder measures roughly 58mm × 30mm × 15mm, and that instantly eliminates any wearable or ultra-compact design. Alkaline cells in humid environments will eventually leak.

Matching Your BLE Profile to the Right Battery

Start with your device’s current demands, then layer in constraints:

What is your BLE duty cycle?
│
├── Advertising only, <30µA average
│   ├── Ultra-compact form factor required?
│   │   YES → CR2032
│   │   NO  → 2x AA lithium primary (longer life)
│
├── Periodic connections, 30–200µA average
│   ├── Rechargeable model acceptable?
│   │   YES → Small LiPo (100–500mAh)
│   │   NO  → 2x AA lithium primary
│
├── Sustained connections / high throughput, >200µA average
│   └── LiPo (size capacity to runtime requirement)
│
└── Includes GPS, display, or audio
    └── LiPo (no other realistic option)

Once you have a candidate chemistry, run a second validation pass:

• Sourcing: Can you procure this cell reliably at production volume? CR2032s are commodity. LiPo cells require qualifying a battery vendor, and lead times vary wildly.
• Shipping and compliance: Selling internationally? LiPo adds dangerous goods handling costs per shipment. Budget for UN38.3 testing.
• Mechanical fit: Measure the battery holder or pouch dimensions, not just the bare cell. A CR2032 holder adds 2–4mm height. A LiPo pouch needs mechanical retention and swelling clearance.
• End-of-life: Products with embedded rechargeable batteries face WEEE and EU Battery Regulation requirements. Primary cells avoid this.

Mistakes That Cost a Redesign

• Trusting datasheet capacity on coin cells. Size your runtime estimate at 50–70% of rated mAh for pulsed BLE loads.
• Choosing LiPo “because rechargeable sounds better” without costing the charge circuit, protection, and dangerous goods shipping overhead. For a low-duty sensor, you may spend $4+ in added BOM and compliance for a feature nobody asked for.
• Ignoring temperature. CR2032 and alkaline cells degrade badly below 0°C. If your device operates outdoors in winter, lithium primary AAs or LiPo (with heating considerations) are your only real options.
• Designing for average current without validating peak headroom. Use a power profiler (Nordic’s PPK2 is $90 and worth every cent) to capture actual TX burst current, then verify your battery handles it with margin.
• Forgetting the battery holder in mechanical design. It’s the first thing that doesn’t fit in the enclosure. Model it in CAD on day one.

Building This Into Your Hardware Requirements

Before you lock your battery choice, write down three numbers: your measured average current (from a power profiler, not a calculation), your measured peak current, and your target field life. Run those against the table above. If your average current is under 30µA and you don’t need recharging, you’re choosing between CR2032 and AA based purely on form factor and target lifespan. If you’re above 200µA average or need features like displays and GPS, you’re in LiPo territory. Start budgeting for the charging circuit and shipping compliance now.

The right battery isn’t the one with the best specs. It’s the one that fits your product’s current demands, form factor, supply chain, and user expectations simultaneously. Get that match right, and every decision downstream, from enclosure to BOM to certifications to retail packaging, gets dramatically simpler.

Hubble Network connects BLE devices directly to satellites, enabling years of battery life from a single coin cell—no gateways, no cellular modems, no power budget compromises. Learn more →