Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <f46af838-8b28-79e6-5298-4458b44664ca@mindspring.com>
Date:   Mon, 28 Feb 2022 09:15:34 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.0
To:     linux-bluetooth@vger.kernel.org
Content-Language: en-US
From:   Ed Beroset <beroset@mindspring.com>
Subject: Battery1 vs. GATT reporting
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

In 
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=713f6f09 a 
flag named "external" was added which, if I'm understanding correctly, 
is supposed to mark the Battery1 profile as safe to also share via GATT. 
  However, I was recently working on an application that relies on the 
GATT API for battery power and found that it only seemed to work as 
expected (reporting via both) if I set the flag to false rather than 
true as in the commit.  I looked through the code and it all looks 
correct, but my observation indicates that perhaps the sense of the flag 
is somehow inverted.

Here's the project I was working on, with the relevant bug report.
https://github.com/AsteroidOS/libasteroid/issues/13

So can someone verify that:
1. the interface is intended to be shared via GATT and Battery1
2. that it does not work that way today

Ed