On Sat, Nov 26, 2022 at 02:39:48PM +0000, Klemens Nanni wrote: > On Sat, Nov 26, 2022 at 07:46:08AM +0100, Anton Lindqvist wrote: > > Hi, > > This diff adds supports for the following to uhidpp: > > > > 1. Bolt receivers, they use a different set of registers for querying > > paired devices. > > > > 2. The Unified Battery feature, this is a more competent feature > > function used to report battery status compared to the Battery > > feature which is already supported by uhidpp. > > > > Makes battery sensors appear for my Logitech Lift mouse and Paul de > > Weerd's MX Anywhere 3 mouse. > > > > If you have a Logitech HID++ device currently lacking sensors under > > sysctl hw.sensors, please give this diff a try. Send me your dmesg and > > output of sysctl hw.sensors after moving the mouse to ensure a connect > > interrupt has fired off. Note that the diff must be applied on top of > > revision 1.37 of sys/dev/usb/uhidpp.c. > > No idea what Bolt or Logitech HID++ is, but my MX Ergo doesn't report > any new sensors with this diff. Should it do so?
Nevermind, it just took a while for the device to send battery reports: hw.sensors.uhidpp0.indicator0=Off (charger) hw.sensors.uhidpp0.raw0=4 (number of battery levels) hw.sensors.uhidpp0.percent0=50.00% (battery level), OK So all working as intended, I just didn't wait long enough after attach to mail out my findings. These lines/values are logged every thirty seconds, I guess those are the actual battery reports? hidpp_send_report: 11 01 08 01 [00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00] uhidpp_intr: 11 01 08 01 [32 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00] Thanks!