bleak VS SimpleBLE

I've used Bleak in Python https://github.com/hbldh/bleak to connect to BLE devices from my laptop using the built-in card. I can iterate over services/characteristics, transmit stuff, use indicates, etc.

On the Raspberry Pi I recommend the Python library Bleak. It has some examples, such as the sensortag.py example that shows how to read characteristics, and the enable_notifications.py example that shows how to subscribe to notifications to read data from a characteristic.

We’ve automated testing on our BLE device. Our rig is based on a Raspberry pi configured with a Gitlab-runner that runs a test suite written in Python. We use a library called Bleak: https://github.com/hbldh/bleak

There are quite a few good BLE helper libraries out there that can make my job easier. But not all are created equal, some may be perfect for building peripheral BLE applications but may not be the best for central BLE applications. As I am going to make the Raspberry Pi the client, Bleak is a great one to use. Bleak is a GATT client software, capable of connecting to BLE devices acting as GATT servers. It is designed to provide a asynchronous, cross-platform Python API to connect and communicate with other BLE devices e.g. sensors.

There is a workaround in here although they claim this is fixed in most recent update: https://github.com/hbldh/bleak/issues/720

If your Python script on your computer should work as the GATT client and your code on the ESP32 as the GATT server, Bleak is an easy-to-use Python library. Have a look at the code examples.

BLE library for python without asyncio

For those who don't know about the project, SimplePyBLE contains the Python bindings for SimpleBLE, a cross-platform Bluetooth library specifically designed for use in desktop environments with a very simple API, allowing developers to easily integrate it into their projects without much effort.

It's been 5 months since the last SimpleBLE release, so I'm here to share what's new on SimpleBLE v0.6.0!

Hey all! I'm currently implementing Rust bindings for a C++ library and I need some feedback on what are proper architectures for exposing callbacks on the Rust side of the API. You can find the code I'm currently working on here: https://github.com/OpenBluetoothToolbox/SimpleBLE/blob/feature/rust/simplersble/src/lib.rs

I've received this request multiple times, so I think it's important enough to make sure it's part of the v0.6 release. I've made an issue to track this, feel free to follow: https://github.com/OpenBluetoothToolbox/SimpleBLE

Fixed the incorrect URLs. My bad on the usage docs, when I wrote this I was referring to the examples folder in the repo. I made it slightly better with some more specific guidance: https://github.com/OpenBluetoothToolbox/SimpleBLE/blob/main/docs/usage.rst