Quick follow-up question on this - did you do any tinkering with battery status? I realized there's a /sys/devices/pci0000:00/0000:00:08.1/0000:07:00.4/usb6/6-2/6-2:1.1/0003:17EF:60EE.001F/power_supply/hid-0003:17EF:60EE.001F-battery in my system, which knows about model_name, but things like "capacity" and "status" return a "No data available".Hello, no, I didn't do anything. It works for me just fine, it shows battery status in KDE applet.Note: I'm using the keyboard over Bluetooth.Hm, over bluetooth, there's a `/sys/devices/virtual/misc/uhid/0005:17EF:60E1.0030/power_supply/hid-*-battery` directory with the same files, and they also have the same "No data available" thing. For now I'll just assume it's due to the controller internally still calibrating and not exposing anything - the keyboard is fairly new. Thanks for confirming it should work in theory :-)
Alright, I now also see battery levels (that also go down after continued use) - needed to enable upower on my system. Works like a charm! Florian
Attachment:
signature.asc
Description: PGP signature
