3 Energy Sources for IoT Devices
Batteries, Harvesting, Storage, Derating, and Source-Selection Evidence
3.1 Start With the Source as a Constraint
An IoT power source is not a perfect fuel tank. A coin cell sags under pulses, a rechargeable pack ages, and a harvester delivers power only when the environment cooperates. The source sets the shape of the design as much as the firmware does.
The practical move is to match the load ledger to usable source behavior: capacity, peak current, derating, recharge pattern, buffer storage, and field validation.
3.2 The Source Is A System
An IoT energy source is more than a battery label or a panel rating. It is the complete path that stores, harvests, converts, protects, and delivers energy to the device while the service promise is being met. The design has to support average load, short peak events, sleep leakage, startup, maintenance delay, and the field environment.
The strongest source decision starts from evidence. A measured load budget tells the team how much energy the device needs. The deployment context tells the team which losses, reserves, and failure modes must be included. Only then does it make sense to choose between a primary cell, rechargeable cell, supercapacitor, harvester plus buffer, wired supply, or hybrid design.
For example, a sensor that averages 85 uA for a two-year service interval needs about 0.085 mA x 24 h x 365 x 2 = 1489 mAh before derating. If cutoff voltage, cold operation, self-discharge, pulse support, and reserve leave only 65% usable capacity, the selected source path needs roughly 1489 / 0.65 = 2291 mAh of rated capacity or an equivalent harvested-and-buffered energy plan. The printed label is not enough without the usability assumptions.
Wired sources still need the same review. A mains-powered gateway may not need a multi-year cell, but it may need isolation, surge tolerance, safe shutdown, backup energy for log flushing, and proof that a brownout does not corrupt storage or leave an actuator in an unsafe state.
If you only need the intuition, use this rule: choose the source from measured load and field conditions, not from the largest printed capacity that fits the enclosure.
The Four Source Questions
Load
What average current, peak current, pulse duration, sleep baseline, retry behavior, and maintenance activity must the source support?
Environment
What temperature range, enclosure, vibration, moisture, light access, service access, and storage time change usable energy?
Source Family
Which battery, storage, harvester, regulator, and protection path matches the workload and maintenance model?
Evidence
Which tests prove startup, pulse load, cold behavior, low-energy behavior, autonomy, recharge, and recovery?
Common Source Families
- Primary batteries fit long maintenance intervals when the load is low and replacement is planned.
- Rechargeable batteries fit devices with a reliable charging path, but they require charge control and end-of-life planning.
- Supercapacitors fit frequent charge and discharge cycles or short hold-up intervals, but leakage matters during long idle periods.
- Harvesters plus buffers fit sites where ambient energy is measured, variable, and supported by storage for source gaps.
- Wired or mains sources fit powered installations, but they may still need backup, isolation, surge handling, and safe shutdown behavior.
Overview Knowledge Check
3.3 Build The Source-Selection Ledger
A source-selection ledger makes the decision reviewable. It separates measured demand from source assumptions, then records the validation gates that must pass before the design can claim a maintenance interval or lifetime target.
For battery-powered nodes, the planning estimate often starts with charge: raw capacity need equals average current multiplied by deployment time. That result is not the selected battery size. The selected source must include usable-capacity derating, reserve, pulse-current support, regulator behavior, and low-energy policy.
Source-Selection Workflow
- Measure the load. Capture whole-device current for sleep, wake, sensing, compute, storage, radio transmit, receive, retries, and maintenance states.
- Record the deployment. State temperature range, enclosure, installation date, shelf time, replacement access, source availability, and safety constraints.
- Estimate raw need. Convert average current and deployment time into raw capacity, or convert state power and time into energy.
- Apply source derating. Account for cutoff voltage, temperature, pulse load, aging, self-discharge, converter losses, leakage, and reserve.
- Choose the source path. Select the source family, storage buffer, regulator, protection, connector, and low-energy behavior.
- Validate the path. Test startup, peak pulses, sleep leakage, cold or hot behavior, autonomy, recharge, recovery, and shutdown behavior.
Review Ledger
Practitioner Knowledge Check
3.4 Why Nominal Energy Disappears
The arithmetic behind source sizing looks simple, but the path from stored or harvested energy to useful device work has many losses and limits. A cell may have enough rated capacity while still failing a radio burst. A harvester may provide enough energy on a good day while failing after a low-harvest interval. A regulator may look efficient during transmit but drain the system during long sleep through quiescent current.
Use charge units when the voltage path is stable enough for current budgeting. Use energy units when voltages, converters, harvesters, and storage elements differ. In both cases, the result is a model that must be tied to measurement and retested when hardware, firmware, radio policy, source chemistry, or the environment changes.
Derating should be explicit rather than hidden in a large safety factor. If a node needs 1577 mAh raw charge for a one-year interval, a 70% usable-capacity assumption raises the source requirement to 1577 / 0.70 = 2253 mAh. Adding a 20% service reserve changes the target again to about 2253 / 0.80 = 2816 mAh. Reviewers should be able to see which step came from chemistry, environment, reserve policy, or measurement uncertainty.
Harvested systems need an energy balance, not only a peak harvester rating. If a load needs 20 mW for a six-hour source gap, the buffer must deliver 20 mW x 6 h = 120 mWh. With 75% storage and converter efficiency, the harvested-side buffer must store about 120 / 0.75 = 160 mWh, plus reserve. At a 3.7 V nominal storage voltage, that is roughly 160 mWh / 3.7 V = 43 mAh before aging and low-temperature effects. The same check should be repeated for startup, radio retries, and recovery after depletion.
Equations To Use Carefully
Raw Capacity
Qraw = Iavg x Tdeployment. Use measured average current and the required service duration.
Rated Capacity
Qrated = Qraw / usable_fraction. State what derating and reserve are included.
Energy Path
Eload = Pload x t. Use energy when converter losses, mixed voltages, or harvesting paths matter.
Harvest Balance
Eharvest usable >= Eload + reserve. Check this across poor-source intervals, not only typical days.
Failure Modes To Surface
- Pulse droop: short radio or actuator peaks can collapse voltage even when average current looks low.
- Cutoff mismatch: stored energy below the regulator or device cutoff voltage is not usable by the product.
- Temperature loss: cold or hot conditions can reduce usable capacity, charging acceptance, and pulse performance.
- Idle drains: regulators, sensors, pull-ups, indicators, protection circuits, and supercapacitor leakage can dominate long sleep periods.
- Harvest gaps: solar, vibration, thermal, and RF sources can disappear or weaken, so storage and recovery behavior matter.
- Unsafe recharge: rechargeable systems need chemistry-appropriate limits, fault handling, and temperature-aware charge policy.
Under-the-Hood Knowledge Check
3.5 Summary
- Select IoT energy sources from measured load, deployment conditions, maintenance access, and safety constraints.
- Rated capacity is not the same as usable field capacity; cutoff voltage, temperature, pulse load, aging, self-discharge, converter behavior, leakage, and reserve all matter.
- Harvesting designs need measured site energy, storage autonomy, load-shedding policy, and recovery tests after source gaps.
- Rechargeable and hybrid systems require charge control, protection, low-energy behavior, and end-of-life planning.
- A defensible source decision leaves evidence: load trace, assumptions, source path, validation results, and retest triggers.
Choose the power source from the whole source system: measured demand, usable capacity, storage, conversion, protection, environment, and validation evidence.
3.6 See Also
Energy-Aware Design Basics
Start with the service promise, average-current budget, and measured energy ledger.
Energy Measurement and Profiling
Capture the full-cycle trace that source selection depends on.
Power Consumption Analysis
Turn state current, duration, and duty cycle into average-current evidence.
Energy Harvesting Design
Size ambient-energy systems with site surveys, storage buffers, and recovery checks.
