| Battery chemistry and capacity | Rechargeable lithium-ion or lithium-polymer battery, approximately 2,000–10,000 mAh at 3.7 V | Several weeks to more than 12 months | Higher usable capacity provides more energy, but battery size, temperature, discharge limits, and self-discharge also affect the result. | Choose the capacity according to the required reporting interval, GNSS workload, enclosure size, and charging method. |
| Position-reporting interval | One location report every 5 minutes, 15 minutes, 1 hour, or 12 hours | About 1–14 days, 2–8 weeks, 3–12 months, or 12–24+ months respectively | Every tracking cycle activates the positioning receiver, microcontroller, sensors, and LoRaWAN radio. | Use longer intervals when continuous real-time tracking is not necessary. Configure motion-triggered reporting where supported. |
| GNSS acquisition time | Typical outdoor fix time of approximately 20–60 seconds; difficult conditions may require several minutes | A 2–5× increase in GNSS operating time can reduce battery life substantially | GNSS commonly consumes more energy than the LoRaWAN transmission itself, especially when satellite signals are weak. | Install the tracker with a clear view of the sky and use assisted or scheduled positioning only when appropriate. |
| LoRaWAN transmission frequency | One uplink per positioning cycle, with payloads generally kept below the regional data-rate limits | Usually a moderate effect; repeated retries can increase consumption by 10–50% or more | Each uplink uses radio energy. Poor coverage can cause additional transmission attempts and longer airtime. | Keep payloads compact, select an appropriate data rate, and avoid unnecessary downlinks and acknowledgements. |
| Network coverage and signal quality | Strong signal with a stable gateway connection versus indoor, underground, rural, or obstructed locations | Battery life may be reduced by approximately 10–50% in difficult coverage conditions | Weak signals can require more airtime, lower data rates, retransmissions, and higher transmit power. | Test the intended installation locations and use confirmed uplinks only when the application genuinely requires them. |
| Sleep-current performance | Low-power sleep current commonly targeted below 20–100 µA, depending on the design and enabled peripherals | A difference of 50 µA can matter significantly in multi-month or multi-year applications | The tracker spends most of its time asleep. Sensors, LEDs, GNSS backup circuits, and voltage regulators may continue drawing current. | Verify the complete device sleep current, not only the microcontroller sleep-current figure. |
| Motion detection settings | Accelerometer-based wake-up with reports triggered only after movement or at selected intervals | Can extend battery life by approximately 2–10× compared with continuous periodic tracking | Motion-triggered operation prevents unnecessary GNSS fixes and uplinks while an asset is stationary. | Use a suitable motion threshold and delay to prevent vibration or minor movement from causing repeated wake-ups. |
| Temperature | Normal operation around 15–25°C versus prolonged exposure below 0°C or above 45°C | Cold conditions can temporarily reduce available capacity by approximately 10–30% or more | Battery internal resistance increases at low temperatures, while high temperatures accelerate ageing and self-discharge. | Select a battery rated for the actual environmental range and avoid placing it next to heat-producing equipment. |
| Firmware and power-management design | Deep sleep, scheduled GNSS activation, efficient data buffering, and limited radio retries | Potential difference of 20–60% between optimized and poorly optimized firmware | Firmware controls how long each subsystem remains active and whether failed operations are repeated unnecessarily. | Request measured current profiles for sleep, GNSS acquisition, transmission, retry, and charging states. |
| Estimated overall battery life | Large battery, one report every 1–12 hours, good outdoor coverage, and motion-aware firmware | Approximately 6–24 months for many practical deployments | This is a broad field estimate rather than a guaranteed value because tracker designs and usage conditions vary widely. | Confirm the estimate with a representative field trial using the final reporting interval and installation position. |