Best Practices: Tracking Battery Life
Two of the most important IoT reliability metrics are the expected and the actual battery life for devices. Understanding and predicting trends for battery life and detecting regressions with thousands to millions of devices in the field is a challenging problem that Memfault recently published advice and product improvements for.
The combination of metric charts, device timeline, and the recently added documentation with code samples help with understanding battery life of MCU, Linux or Android devices.
- Added: Documentation of best practices for battery life tracking
- Added: Timezone picker for selecting custom timezones
- Improved: UI glitches and improvements (More readable timestamps under Device Details → Log Files, error prompt to prevent misconfigured Issue Charts)
- Fixed: Introduction pages linking to themselves on Memfault Docs
- Fixed: Timeouts when loading the Received Traces charts on the Dashboard
- Fixed: Pending software version of a device was not updated after configuring a new deployment
- Fixed: Empty metric charts when a formerly non-timeseries metric is used in the chart
- SDK version 0.33.5 was released. Some highlights:
- Added: Creation of kernel oops traces from
- Improved: OTA link expiry window increased to 6hr (previously 1hr) for more reliable downloads on slow internet connections
- SDK version 4.3.0 was released. Some highlights:
Documentation of when reads and writes happen to Linux SDK
- We did not publish a new version of the Memfault Linux SDK in October.