What was the reason to not use the D-Bus API of BlueZ?

50ButtonsEach / fliclib-linux-hci

Flic SDK for Linux

306 stars 53 forks source link

What was the reason to not use the D-Bus API of BlueZ? #53

Open larsblumberg opened 7 years ago

larsblumberg commented 7 years ago

Hi! We're facing similar issues like you – we want to connect Bluetooth Low Energy peripherals with Linux. One reason you mentioned is that BlueZ has experimental features. I guess you're not talking about the Bluetooth Low Energy capability because its BLE/GATT API is marked as stable as of BlueZ version 5.42, released in September 2016.

Would you mind sharing your reasons against BlueZ for this SDK?

fabianbergmark commented 7 years ago

We tried Bluez last summer. Back then we encountered bug after bug. While the Bluez developers were quick to fix some of them, we realized that the BLE/GATT support wasn't developed to support advanced use-cases like ours. Maybe @Emill can provide more details

larsblumberg commented 7 years ago

Thanks for sharing your insights! We've recently started using BlueZ via its D-Bus API and so far we're quiet happy, connectivity and event processing are very reliable so far. We're developing a Python library on top of BlueZ/D-Bus, maybe it turns out useful and you can contribute to it in the future.

mrquincle commented 4 years ago

I guess it indeed become quite useful. Congrats!