CLI tool to help you care about your devices's battery health.
rusty-battery
?If you aren't able to set start/stop charge threshold
(for example via TLP) but would still like to
make sure that your battery won't exceed your preferred threshold.
rusty-battery
can let you know when your battery reached the threshold by
showing a desktop notification and optionally pinging your
KDE Connect devices.
Notify whenever battery percentage exceeds the given threshold.
USAGE:
rusty-battery notify [FLAGS] [OPTIONS]
FLAGS:
-v, --verbose
Activates verbose mode
OPTIONS:
--kde-connect <kde-connect-names>...
KDE Connect device names
If this value is not present, KDE Connect will not be used.
If this value is empty, all of the KDE Connect devices will be pinged.
-m, --model <model>
Battery model name
If this value is omitted and only battery device is found for the current device, that one will be used.
Otherwise, please use the `batteries` subcommand to get a list of all battery devices to get the model of
the wanted battery device which should be monitored.
--refresh-secs <refresh-secs>
Number of seconds to wait before refreshing battery device data
After every battery device refresh, its data will be checked. Notifications will be sent everytime they
should be, based on the new refreshed battery device data. [default: 30]
-t, --threshold <threshold>
Battery charge threshold
Whenever the chosen battery device reaches this charge threshold and will be charging, notifications will be
sent, alerting that the charger should be unplugged. [default: 80]
List all available batteries of the current device
USAGE:
rusty-battery batteries [FLAGS]
FLAGS:
-v, --verbose Activates verbose mode
List all available KDE Connect devices
USAGE:
rusty-battery kde-connect-devices [FLAGS]
FLAGS:
-v, --verbose Activates verbose mode
cargo install rust-battery
git clone git@github.com:kucera-lukas/rusty-battery.git
cd rusty-battery
cargo install --path .
Download a binary of the
latest release
and move it to a directory which is in your $PATH
.
You may need to change the binary's permissions by running
chmod +x rusty-battery
.
If there are any problems with the pre-compiled binaries, file an issue.
This tool is best used when set up as a background task.
Here is a guide to set it up via cron
:
rusty-battery
executable via which rusty-battery
and get absolute path to itsudo crontab -e
i
to enter vi
insert mode@reboot path/to/rusty-battery notify [OPTIONS]
esc
to exit insert mode and then :wq
to close vi
sudo reboot
You can check that rusty-battery
is running via ps aux | grep -e rusty-battery
.\
To kill the rusty-battery
job use kill $PID
.
If you want logging add this to the end of the cron job: -vv >> /var/log/rusty-battery.log 2>&1
.\
To check all the logs you can use more /var/log/rusty-battery.log
.\
To see the logs live you can use tail -f /var/log/rusty-battery.log
.
Currently, only linux is supported.