Okay, I have solved the problem with a workaround: In the code for my development board I added a new line character after every value. Then, in my Qt code I check every time the SLOT is called if the value does have a new line char. Either the value is saved in another variable until it receives a value with a new line character or it is output immediately (if it has a new line character). static QString newValue= ""; void MainWindow::updateData(const QLowEnergyCharacteristic &c,const QByteArray &value) { newValue = newValue + (QString)value; if (newValue.contains("\n") || newValue.contains("\r")){ ui->dataList->addItem(newValue.simplified()); ui->dataList->scrollToBottom(); newValue = ""; } }

Thank you both very much.

Thank you for your reply. I found this in the documentation: In some cases the peripheral generates value updates which the central is interested in receiving. In order for a characteristic to support such notifications it must have the QLowEnergyCharacteristic::Notify or QLowEnergyCharacteristic::Indicate property and a descriptor of type QBluetoothUuid::ClientCharacteristicConfiguration. Provided those conditions are fulfilled notifications can be enabled as shown in the following code segment: QLowEnergyCharacteristic batteryLevel = service->characteristic( QBluetoothUuid::BatteryLevel); if (!batteryLevel.isValid()) return; QLowEnergyDescriptor notification = batteryLevel.descriptor( QBluetoothUuid::ClientCharacteristicConfiguration); if (!notification.isValid()) return; // establish hook into notifications connect(service, SIGNAL(characteristicChanged(QLowEnergyCharacteristic,QByteArray)), this, SLOT(characteristicChanged(QLowEnergyCharacteristic,QByteArray))); // enable notification service->writeDescriptor(notification, QByteArray::fromHex("0100")); So you were right. But what I do not understand: The writeDescriptor function "Writes newValue as value for descriptor." But what "value" is the QByteArray::fromHex("0100") ? Because when i write the same code for my application and when I call value() on the ClientCharacteristicConfiguration Descriptor from my RX characteristic the output is \x00\x00

Ah ok sorry! Indeed last time I worked with BT it was with older Qt version.

@TUStudi AFAIK writing an MS Excel file is not possible with Qt directly. You need some additional stuff. But writing to a file in general (raw textfile, JSON, XML... etc) is quite easy.

@harip said in Bluetooth Low Energy: State 'ServiceDiscovered' is never reached: @SpaceToon Is this issue resolved? We are also facing the same issue in Windows 10. As you mentioned, the BLE scanner example is working perfectly fine. Hey, not it is not fixed yet, but a developer is investigating the issue. You can track the current status of the bug here in Jira.

@sierdzio said in Bluetooth Low Energy Scanner: Discover Service Details: No idea. But notice that the example code specifically does not call characteristics() method when state is DiscoveringServices. Perhaps try doing the same? I made a switch statement in my slot so if state is Discovering i should only print the state and if the state is "ServiceDiscovered" then it shoul call characteristics(). But as I mentioned, the state "ServiceDiscovered" is never reached.

@J-Hilk Thank you for your reply. This could be the reason because when I tried an CS Dongle external Bluetooth Adapter, it worked. Is there an official statement from Microsoft, where you can read something like this in the future or where did you get this information?

Thank you very much for your reply. @sierdzio said in Bluetooth LE performance in different platforms: Is the simulated beacon paired in Windows Bluetooth settings? Without it, Qt will not detect it! (this will be fixed in Qt 5.14 I think)., Unfortunately, Windows does not allow me to pair the simulated iBeacon since it does not appear in the available Bluetooth devices list from the control panel. @sierdzio said in Bluetooth LE performance in different platforms: Also, make sure you're using the newest Windows version with all updates. Unfortunately, Bluetooth support on Windows is quite bad, has memory leaks etc. In early Windows 10 builds it was barely working at all. Sure, it is the latest Windows version with all updates. I was also trying to compile the Qt 5.15 source available in the repo to enable the win32 Bluetooth API to see if it makes any difference but I wasn't able to compile it... But this was just a curiosity. For me it's OK to consider Windows as the least compatible platform for the moment. About Android, I was able to tune the application and now it can properly detect the simulated iBeacon. I was using the Bluetooth LE scanner example but I hadn't checked the manifest file so that was probably the issue.

@SpaceToon said in Dummy backend running. Qt Bluetooth module is non-functional (Bluetooth Low Energy): So is it possible with the MSVC Compiler? No. You will need to build your code for Linux. It is better to do this on a Linux machine as cross compiling from Windows to Linux will be a lot of work. You can have a virtual machine with Linux to build for Linux.

I tested it with Qt 5.11.0, but more deficiency detected. The General Attribute also undetected and characteristic write is not working :(

@NicoFrom13 Hi, Were you able to use this work in progress qtconnectivity? Is it properly working ?

Awesome man. That show me that sometimes ask the question is more usefull than searching for hours.... I didn't know that i could not use Windows SDK with MinGW i understand now. windows SDK needs to be with Visual compiler ... Many thanks have a nice Day.

Hi and welcome to devnet, Glad you found out and thanks for sharing. Since you have ti working now please mark the thread as solved using the "Topic Tools" button so that other forum uses may know a solution has been found :)

Then I'd recommend asking this on the interest mailing list. You'll find there the QtBluetooth module maintainers/developers.

Hi, There might just be not much people on this forum that use the QtBluetooth module. In that case, there's always the interest mailing list where you can find Qt's developers/maintainers.

A bit of a late response, but... Assuming the GATT server on the other end has a characteristic that allows for Indicate, then the only thing that needs to change is the value that you write to the descriptor. Set Bit 1 of the CCC to enable indicates by writing "0200" instead of "0100" (the descriptor is little-endian according to the BLE documentation for the Client Characteristic Configuration descriptor). As far as I know, indications are delivered with the characteristicChanged signal just like notifications.

I know this question is old, but it seems noone is answering BLE related questions here. (I've just posted such a question myself, and fear noone will anwer it either). I developed an app based on the same example, and it worked fine under both android 4.3.2, 5.1.2, and 6.0. However, the customer came with an android 5.01, and sure enough, the app did not work as expected. It seemed to "hang" and tried to connect to two devices at the same time, etc. We did not investigate it further. This was with Qt 5.6, so the issue is not resolved, and may never be, since with newer versions of Android it is working fine.

Hi, There's a WIP branch in the qtbluetooth module for Windows, you can check the state there.

@kuzulis Thanks!

@pbljung said in BLE demos fail on Android: errorReceived these errors can happen see my comments on top of void MyBluetoothDeviceInfo::onControllerError(QLowEnergyController::Error error) in https://github.com/ekke/ekkesBTLEexample/blob/master/cpp/bt/mybluetoothdeviceinfo.cpp not only 133 (reported as unhandled error) also 34 and 8 can happen see also all the discussions at https://bugreports.qt.io/browse/QTBUG-31674 per ex from my comment on 133: while developing new example app for BT LE and Qt 5.8 using QtQuickControls2 for Android, iOS I also run into GATT ERROR 133 googled and found out that this bug iseems not to be a Qt Bug. some more infos here: https://github.com/NordicSemiconductor/Android-nRF-Toolbox/issues/9 https://android.googlesource.com/platform/external/bluetooth/bluedroid/+/android-5.1.1_r13/stack/include/gatt_api.h of course would be great if Qt could handle error 133 my workaround: if getting a QLowEnergyController::ConnectionError I try to reconnect up to 5 times with a delay of 1000ms In most cases 2nd or 3rd retry will connect without the error. BTW: find out more on my new BTLE Example APP: http://bit.ly/ekkeBTLEapp

Maybe you should just do bluetooth turn off/on programmaticaly from your app, before using of an BLE.

A BTLE port towards WinRT is currently going on and we hope to have it supported with Qt 5.8. Please note that this does not include classic / desktop Windows, as the APIset is not available for this platform.

@csanders Bump this. I've got the same issue. Anyone at Qt able to shed some light on why it's so difficult to perform these features on iOS? I'm assuming it's something to do with Apple's MFi?

Thx, i will give it a try

Thank you for answer, I'll look forwad this version !