Re: Battery1 vs. GATT reporting

[Ed Beroset <beroset@mindspring.com>]

On 3/2/22 10:33, Ed Beroset wrote:
> On 3/1/22 11:01, Ed Beroset wrote:
>> On 3/1/22 10:43, Sonny Sasaka wrote:
>>> Hi Ed,
>>>
>>> What I do is call `gatt.select-attribute` on the characteristic called
>>> "Battery Level", but it is not shown in your case. So maybe this is
>>> the bug that you are encountering. What is the exact version of your
>>> BlueZ (commit sha if possible)? Could you also try tip of tree to see
>>> if this is already fixed?
>>
>> Hi Sonny,
>>
>> I'm sorry, I should have noted that this is with the tip of tree, 
>> commit bf09e1f048.  Thanks for your help with this!
> 
> I am trying this from a different computer today and I find that now the 
> Battery Service and Battery Level characteristic are showing up, even on 
> the same devices I was reading the other day.  Not sure what's going on, 
> but I am investigating further.  At the moment, it seems more likely 
> that the problem is either with my devices or with my software.  I just 
> wanted to report back to avoid having you all waste your time.  When I 
> figure this out, I'll send another update.  Thanks for the help so far.

OK, it's been a while, but the problem was eventually tracked not to 
BlueZ but a Qt component I was using.  Essentially, changes in BlueZ 
were being tracked by changes in Qt, but there was a problem with the Qt 
implementation starting with BlueZ version 5.55.  No change required in 
BlueZ, and already fixed in Qt, but I thought I'd circle back around and 
let you all know the resolution.

https://bugreports.qt.io/browse/QTBUG-70222

Ed