Bug#1021396: ITP: batterylog -- laptop battery logging tool
Package: wnpp
Severity: wishlist
Owner: Antoine Beaupre <anarcat@debian.org>
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name : batterylog
Version : none
Upstream Author : Leonard Lin
* URL : https://github.com/lhl/batterylog
* License : GPLv3
Programming Lang: Python
Description : laptop battery logging tool
A simple Python app with few dependencies that reads your
sysfs-class-power numbers and records them to a local sqlite3 db with
an "event" tag.
It was built to track suspend power usage for Framework laptops, but
is flexible/easily extensible to do all kinds of other stuff.
----
This is similar to the already packaged battery-stats, but is a little
more explicit in its output. While battery-stats keeps a text and CSV
log, batterylog stores its entries in a SQLite database.
battery-stats stores new entries every minute, in cron, while
batterylog does it on systemd triggers (like sleep/resume). It could,
in theory, do exactly the same as battery-stats and run in a cron job,
but those are triggers installed by default upstream.
They both keep different records in each entry. battery-stats keep the
charge status (charging/discharging), manufacturer, battery type and
identifier, while batterylog keeps voltages.
both ship similarly-named binaries, battery-stats ships battery-log,
and batterylog ships... batterylog.
batterylog is a single script, ~130 lines of python, quite readable,
while battery-stats is a mix of shell and python, spread over multiple
files.
batterlog was started a few months ago, and is the work of a single
maintainer. batterystats has been around since 2013 and has seen half
a dozen contributors (including myself).
batterystats can generate graphs, and, really, all batterylog
currently does is this:
$ /opt/batterylog/batterylog
Slept for 8.72 hours
Used 6.10 Wh, an average rate of 0.70 W
For your 53.67 Wh battery this is 1.30%/hr or 31.29%/day
But it's surprisingly useful in trying to tune battery life,
especially during suspend.
Reply to: