---
title: "Discussion on \"Battery-Powered IoT Sensors: Power Budgets, LPWAN Choice and SIM Settings for Underground and Remote Sites\" | Hashnode"
description: "Discussion on \"Battery-Powered IoT Sensors: Power Budgets, LPWAN Choice and SIM Settings for Underground and Remote Sites\". How to size batteries and choose NB-IoT, LTE-M or LoRaWAN for mine, tunnel and remote sensors, and which SIM settings drive battery life."
url: "https://hashnode.com/posts/battery-powered-iot-sensors-power-budgets-lpwan-choice-and-sim-settings-for-underground-and-remote-sites/6ac98d1a25f15888a5677cec"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Battery-Powered IoT Sensors: Power Budgets, LPWAN Choice and SIM Settings for Underground and Remote Sites](https://liotsim.hashnode.dev/battery-powered-iot-sensors-power-budgets-lpwan-choice-and-sim-settings-for-underground-and-remote-sites?utm_source=hashnode&utm_medium=feed)

How to size batteries and choose NB-IoT, LTE-M or LoRaWAN for mine, tunnel and remote sensors, and which SIM settings drive battery life.

Oct 10 · 11 min read · liotsim.hashnode.dev  
Read the article

-   [#iot](https://hashnode.com/tag/iot)
-   [#embedded](https://hashnode.com/tag/embedded)
-   [#lorawan](https://hashnode.com/tag/lorawan)
-   [#hardware](https://hashnode.com/tag/hardware)
-   [#networking](https://hashnode.com/tag/networking)

## Written by

[Jietion](https://hashnode.com/@globaliotsim)

@globaliotsim · Guangzhou, China

  
[View profile](https://hashnode.com/@globaliotsim)

Business Development at Quanqiu IoT

## Responses 2

Markdown supported · ⌘↵ to post

[Yunus Emre Vurgun](https://hashnode.com/@yunusemrevurgun)

[Oct 16](https://hashnode.com/posts/battery-powered-iot-sensors-power-budgets-lpwan-choice-and-sim-settings-for-underground-and-remote-sites/6ac98d1a25f15888a5677cec/comment/6ad208a8da8aaf54c3145f83)

The point about starting from the measured sleep floor rather than the datasheet number matches what I see on small ESP32 builds, where regulator quiescent current and a leaky divider often outweigh the chip itself. Have you found that wake-up retries in weak signal are usually the biggest single drain in the field, or is paging/PSM timer config a bigger factor? A quick tip: logging charge used per report cycle (not just average current) makes those retry spikes easy to spot.

[Jietion](https://hashnode.com/@globaliotsim)

[Oct 23](https://hashnode.com/posts/battery-powered-iot-sensors-power-budgets-lpwan-choice-and-sim-settings-for-underground-and-remote-sites/6ac98d1a25f15888a5677cec/comment/6ad208a8da8aaf54c3145f83#reply-6adb89d5c414037f9634908c)

Thanks, and good tip on logging charge per report cycle. It is the quickest way to separate retry spikes from the baseline.

On your question: in weak-signal sites the retries usually dominate. Each failed attach or resend keeps the radio at its highest current for seconds, while PSM/eDRX timers mostly set the floor between reports. The two interact, though: the network can grant shorter PSM or eDRX timers than the device requested, so the unit wakes more often, and in poor coverage every extra wake brings its own retry series. So we would first check the timers the network actually granted (AT+CEREG=4 shows the granted T3412/T3324), then count retries per cycle. Randomised back-off after failures, as GSMA TS.34 recommends, also stops a whole site from retrying at the same moment.
