Re: [PATCH v2 1/1] HID: logitech: add Bolt receiver support for Logitech HID++ devices

["Erik Håkansson" <erikhakan@gmail.com>]

On 7/30/26 10:38, Bastien Nocera wrote:
> On Tue, 2026-07-14 at 12:32 +0200, Kateřina Medvědová wrote:
>> Hi,
>>
>> Just tested V1 again with both of the receiver versions I have on
>> hand
>> and the input issues I described happen on both.
>>
>> btw, thank you for pointing out that you can check the FW version in
>> fwupd. This greatly simplified testing.
>>
>> I do have one find -- when a device gets powered off (yanked battery,
>> switch moved to the off position, switching devices), the battery
>> stays
>> in upower. Unifying also does this, disconnected devices stay.
> Unifying definitely didn't use to do this, I don't know whether it's a
> problem in upower or the kernel.
>
> "udevadm monitor -k -p" correctly shows the battery switching between
> POWER_SUPPLY_ONLINE=0 and POWER_SUPPLY_ONLINE=1 when turning the device
> off. Not sure whether that's what it used to do.
>
> If someone has time, please test with older versions of upower (I would
> say go back to 1.90.2 and start bisecting).

I can confirm the behaviour you're describing from "udevadm monitor -k -p". upower changes "state: discharging" to "state: 
unknown" when disconnected while Solaar simply displays the device as 
disconnect but paired. This behaviour is the same for me for both my 
Bolt keyboard and my Lightspeed mouse. The KDE Power widget removes the 
"Discharging" prefix before the battery percentage but otherwise nothing 
changes when disconnecting for either Bolt or Lightspeed device, which I 
guess is because it's based on upower. I could have a look at this and 
try older upower and/or kernel versions, but since it seems to be 
unrelated to this patch I suggest I do it as a separate activity. 
Regards, Erik

>
>>   Either
>> this was intentional or a bug. Either way the behavior is consistent
>> with the existing code and isn't introduced by your changes. I'm just
>> not sure what the correct behavior should be. Sorry if this pollutes
>> the
>> discussion, I'm completely new to the LKML.
>>
>> I'm not sure what else I could try, I'll keep your V2 on my system
>> and
>> let you know if any issues pop up.
>>
>> Regards,
>> Kate
>>
>> On 7/14/26 2:54 AM, Erik Håkansson wrote:
>>> Hi,
>>>
>>> Thank you very much for your help.
>>>
>>> Unfortunately I don't have a Windows system easily accessible, so I
>>> can't check my firmware version in Options+.
>>> fwupdmgr says:
>>>> Current version:    MPR05.03_B0020
>>> so perhaps that means 5.03.20.
>>>
>>> Let me know if anything pops up if you dig some more,
>>> Thanks,
>>> Erik