[Interest] Bluetooth low energy on Windows 10

Glenn Ramsey gr at componic.co.nz
Fri Jul 27 02:19:47 CEST 2018

Thanks Olli,

I didn't realise that Windows requires the device to be manually paired as the
other OSes I'm developing for don't seem to require this for BLE.

It turns out that when paired using the Windows 10 Settings app, the device I'm
using gets disconnected a few seconds after pairing and it then can be seen, but
not connected to, by other apps but if paired using the dialog that a UWP app
shows (or the 'Pair' function in Microsoft's Bluetooth LE explorer app) then it
stays connected and win32 apps can see it and connect to it. This gives me a
temporary workaround until the connection issues for my target device are fixed.

I've reported this to the device manufacturer but also reporting it here in case
there are other devices that have a similar problem.


On 25/07/18 17:51, Oliver Wolff wrote:
> Hi Glenn,
> I am not sure I understand your situation. The Windows BT implementation needs a
> paired device in order to work. You said, that you paired the device in the
> beginning. Have you paired the device and it does not work for you? If this is
> the case please create a bug report which also states your Windows version and
> the device you are trying to connect to. You can assign the bug report to me.
> Olli
> On 25/07/2018 05:37, Glenn Ramsey wrote:
>> Hi,
>> I'm trying to get Qt(5.11.1) communicating with a BLE device on Windows 10 using
>> the win32/WinRT backend.
>> Using the lowenergyscanner example it can 'see' the device, only after it has
>> been manually paired,  but hangs when querying the services. The Microsoft BLE
>> Explorer app from the Microsoft Store is able to 'see' all of the services and
>> characteristics of the device and the UWP version of lowenergyscanner also seems
>> to work correctly. Also the same version (in 5.11.1) works correctly on OSX.
>> In the debugger I can see that the hang occurs somewhere in
>> QLowEnergyControllerPrivateWinRT::connectToDevice().
>> This bug [1] suggests this might be because windows needs to pair with the
>> device, although I'm not seeing any indication of this in the UI when I run
>> lowenergyscanner but I don't see the the device listed until I manually pair it.
>> Is there some step that I have missed, or should I file a bug report about this?
>> Glenn
>> [1] https://bugreports.qt.io/browse/QTBUG-58660

More information about the Interest mailing list