QBluetoothLocalDevice reports connected although connection fails when QLowEnergyController throws Unknown Error

Hi,

Use case:

2 QLowEnergyController objects each connecting to a different BLE peripheral.

When the member function connectToDevice is called too fast on both objects, one of the  connections will fail as QLowEnergyController traps an Unknow error and the state of this object is reported as connectingState.

QBluetoothLocalDevice will catch 2 a connected signals despite one of the connection has failed.

So as "temporary" workaround I no longer depend on the connected signal from the QBluetoothLocalDevice for counting the number of connected ble peripherals in my QBluetoothLocalDevice object. I will just rely on the connected signal of the QLowEnergyControl object.  AS my QBluetoothLocalDevice object contains the QLowEnergyController objects I can keep track of the actually correct number of connected BLE peripherals.

Best regards,

Frank