For some (unknown) reason, redrawing while in the update loop breaks the
update (this probably warrants a closer look).
As a quickfix to restore functionality, remove the unnecessary redraw
call and move it into the async codepath, where it is actually needed.
fixes#1001
A previous change accidentially changed the "pretty" device name mapping
to be required to be in lowercase (rather than the exact name of the
devices. Restore previous functionality.
fixes#989
mousewheel up and down events were initially not working on my bumblebee status bar. After verifying on the command line, it seems that wpctl set-volume command requires sink ID first and percentage change as the second arg.
steps to verify, assuming wireplumber is installed and sink ID is 32
```sh
wpctl set-volume 32 50%
```
will set the volume to 50%
```sh
wpctl set-volume 50% 32
```
will result in `Object '52' not found
Based on cpu2 module, but use `sensors -j` and some json path walking to
better parse CPU temp and fan speeds. The output of `sensors -u` can
contain many duplicates of the same sensor name, but from different
sensor device paths.
Signed-off-by: SuperQ <superq@gmail.com>
* with newer versions of pi-hole, it is not possible
anymore to use the password hash for the API authentication.
Instead, one needs to use the dedicated API token for that.
In order to stay backwards compatible, and not break existing
bumblebee_status setups, the 'pwhash' parameter is still supported
(in case someone runs an outdated pi-hole version).
* the new pi-hole API endpoints do not allow to access the summary
endpoint without an API token. So, therefore '&auth=<api token>' was
added.
no devices lead to an exception that completely stopped bumblebee-status
from processing data.
handle this case more gracefully by defaulting to a volume of 0%. if
this proves to be an issue, we can still add error indicators later.
see #940
Fixed publicip bug arising from last PR review
Simplified ip change detection code
Added pause after location.reset() call to allow completion before query
util.location - change order of information providers as default was not returning geo coords
The logic for the critical/warning handling on the battery modules was
applied BEFORE the discharging-<pct> logic. This made it possible for
those discharging states to get applied over a critical/warning and
allow a theme to override the critical/warning colors with a state of
"discharging-10", for example.
This change moves that logic after the discharging state, so that it
will always "win" if critical or warning states are set.
This also adds the "discharging" battery state to the critical/warning
check so the state will apply if the battery is not on AC power, but
would return normal otherwise. Meaning, if the battery is "critical"
from a percentage check, but is plugged into power, the critical state
is removed.
