Devices can be connected outside of the Bluetooth interface for example through the system's settings. We need to expose a function to allow clients to retrieve all connected devices including those connected to outside the Bluetooth interface.

Current status:

BlueZ[1]: As opposed to other platform APIs BlueZ exposes all known devices to all its clients so we implemented RetrieveGattConnectedDevicesWithDiscoveryFilter by iterating over known devices and returning the ones that are connected.

Android: Exposes BluetoothManager#getConnectedDevices. WIP patch that uses that function https://codereview.chromium.org/2499913002

macOS: Exposes retrieveConnectedPeripheralsWithServices. RetrieveGattConnectedDevicesWithDiscoveryFilter is currently implemented but it doesn't work correctly for standard UUIDs because a bug in retrieveConnectedPeripheralsWithServices: 

Calling retrieveConnectedPeripheralsWithServices with "0000180f-0000-1000-8000-00805f9b34fb" wouldn't find any devices but calling it with "180f" would find them.

Windows: RetrieveGattConnectedDevices is not implemented on windows yet but its functionality is included in scanning procedure. Note that retrieving this devices is done asynchronously.


To resolve this issue we would need to:

1. Change RetrieveGattConnectedDevicesWithDiscoveryFilter to be async because of Windows.
2. Finish Android implementation
3. Change BluetoothUUID to return a short UUID and use it when calling retrieveConnectedPeripheralsWithServices.
4. Uncouple RetrieveGattConnectedDevices from Windows scanning.
 

Devices can be connected outside of the Bluetooth interface for example through the system's settings. We need to expose a function to allow clients to retrieve all connected devices including those connected to outside the Bluetooth interface.

Current status:

BlueZ[1]: As opposed to other platform APIs BlueZ exposes all known devices to all its clients so we implemented RetrieveGattConnectedDevicesWithDiscoveryFilter by iterating over known devices and returning the ones that are connected.

Android: Exposes BluetoothManager#getConnectedDevices. WIP patch that uses that function https://codereview.chromium.org/2499913002

macOS: Exposes retrieveConnectedPeripheralsWithServices. RetrieveGattConnectedDevicesWithDiscoveryFilter is currently implemented but it doesn't work correctly for standard UUIDs because a bug in retrieveConnectedPeripheralsWithServices: 

Calling retrieveConnectedPeripheralsWithServices with "0000180f-0000-1000-8000-00805f9b34fb" wouldn't find any devices but calling it with "180f" would find them.

Windows: RetrieveGattConnectedDevices is not implemented on windows yet but its functionality is included in scanning procedure. Note that retrieving these devices is done asynchronously.


To resolve this issue we would need to:

1. Change RetrieveGattConnectedDevicesWithDiscoveryFilter to be async because of Windows.
2. Finish Android implementation
3. Change BluetoothUUID to return a short UUID and use it when calling retrieveConnectedPeripheralsWithServices.
4. Uncouple RetrieveGattConnectedDevices from Windows scanning.
 

Devices can be connected outside of the Bluetooth interface for example through the system's settings. We need to expose a function to allow clients to retrieve all connected devices including those connected to outside the Bluetooth interface.

A use case for Web Bluetooth is configuring devices that are already connected e.g. a mouse. Because we currently can't retrieve devices connected outside of the Chrome this use case is impossible at the moment. The best Web Bluetooth can do is iterator over all known devices and find the ones connected; this misses devices connected outside Chrome but at least it returns some connected devices.

Current status:

BlueZ[1]: As opposed to other platform APIs BlueZ exposes all known devices to all its clients so we implemented RetrieveGattConnectedDevicesWithDiscoveryFilter by iterating over known devices and returning the ones that are connected.

Android: Exposes BluetoothManager#getConnectedDevices. WIP patch that uses that function https://codereview.chromium.org/2499913002

macOS: Exposes retrieveConnectedPeripheralsWithServices. RetrieveGattConnectedDevicesWithDiscoveryFilter is currently implemented but it doesn't work correctly for standard UUIDs because a bug in retrieveConnectedPeripheralsWithServices: 

Calling retrieveConnectedPeripheralsWithServices with "0000180f-0000-1000-8000-00805f9b34fb" wouldn't find any devices but calling it with "180f" would find them.

Windows: RetrieveGattConnectedDevices is not implemented on windows yet but its functionality is included in scanning procedure. Note that retrieving these devices is done asynchronously.


To resolve this issue we would need to:

1. Change RetrieveGattConnectedDevicesWithDiscoveryFilter to be async because of Windows.
2. Finish Android implementation
3. Change BluetoothUUID to return a short UUID and use it when calling retrieveConnectedPeripheralsWithServices.
4. Uncouple RetrieveGattConnectedDevices from Windows scanning.