bat: issue: Battery percentage setting doesn't persist; systemctl does not indicate that bat@.service is running.

Ah. I see. Then it might better to do in the unit file template since the setup logic already resolves the actual value.

after I commanded sudo bat persist, the contents of the bat@.service reverted back to the previous version. When I try to enable the service with systemctl, this is what it said:

Failed to get properties: Unit name bat@.service is neither a valid invocation ID nor unit name.

That line doesn’t work because sh doesn’t expand the question mark in echo 60 >/sys/class/power_supply/BAT?/charge_control_end_threshold. You have to do: b=$(echo /sys/class/power_supply/BAT?/charge_control_end_threshold); echo 80 >"$b" (or you have to substitute the actual value into the unit files, so BAT0 or BAT1 or whatever).

Of course NixOS allows you to do basic operations like this. Their focus is on package & configuration management. They use systemd, they have bash.

@cloudmadeofcandy, please let me know if the following works.

This works perfectly. Thank you so much 💯

Yes, but being immutable and all, does it allow changing the threshold manually or otherwise?

replacing %s with /bin/bash does though.

I just use /bin/sh as I assume that to be universally available on Linux.

I’m not sure that’s the case on NixOS but that could be a good default.

@cloudmadeofcandy are you sure you’re running the correct version? bat@multi-user shouldn’t be there anymore. There should be 5 different services for each event after the change.

I haven’t merged the changes yet. They’re in this PR if you want to checkout the code.

Yes I left the %s in there so that the application doesn’t have to contain logic to find the shell. systemd can take care of that. Does it not work for you?

@tshakalekholoane It is also good to include RemainAfterExit=true in the unit files under [Service], because then the service shows as Active when doing systemctl status.

That confirms there is something wrong that @tshakalekholoane needs to fix.

@pepa65 you are correct.

After I turned the laptop on, the battery indicator turned red again, but when the ubuntu shell appeared, the battery indicator turned white again. This is a most peculiar turn of event.

The bat@.service is still indirect enabled, tho. What is happening and how do I fix it? The glob should work, right?

Should I close the issue when it is not fully solved?

Alright, I’ll try that.

systemctl list-unit-files I see my bat with enabled enabled both in green

Mine’s indirect enabled

On your system, what is the output of cat /etc/systemd/system/bat*

It is identical to the source file.

[Unit]
Description=Persist the battery charging threshold after %i
After=%i.target
StartLimitBurst=0

[Service]
Type=oneshot
Restart=on-failure
ExecStart=%s -c 'echo 60 > /sys/class/power_supply/BAT?/charge_control_end_threshold'

[Install]
WantedBy=%i.target

There really is no difference.

Looking at the %i and the description in the picture, %i seems to be equal to “multi-user”

I also notice that the battery limiter also works after shutting down, however when I turn it on, the threshold immediately resets to 100