Bleak Retry Connector
A connector for Bleak Clients that handles transient connection failures
Installation
Install this via pip (or your favourite package manager):
pip install bleak-retry-connector
Usage
Quick Start
Replace your direct BleakClient.connect() calls with establish_connection() for automatic retry logic and better error handling:
import asyncio
from bleak import BleakScanner
from bleak_retry_connector import establish_connection, BleakClientWithServiceCache
async def connect_to_device():
# Find your device
device = await BleakScanner.find_device_by_address("AA:BB:CC:DD:EE:FF")
if device is None:
print("Device not found!")
return
# Establish connection with automatic retry logic
client = await establish_connection(
BleakClientWithServiceCache, # Use BleakClientWithServiceCache for service caching
device,
device.name or "Unknown Device",
max_attempts=3 # Will retry up to 3 times with backoff
)
try:
# Use the connected client normally
services = client.services
print(f"Connected! Found {len(list(services))} services")
# Read a characteristic
value = await client.read_gatt_char("00002a00-0000-1000-8000-00805f9b34fb")
print(f"Read value: {value}")
finally:
await client.disconnect()
# Run the example
asyncio.run(connect_to_device())
Why Use bleak-retry-connector?
- Automatic Retry Logic: Handles transient connection failures automatically
- Intelligent Backoff: Uses appropriate delays between retry attempts
- Service Caching:
BleakClientWithServiceCachecaches services for faster reconnections - Better Error Messages: Provides clear, actionable error messages
- Platform-Specific Handling: Manages quirks across different operating systems
- Connection Slot Management: Handles limited connection slots on some devices
Common Connection Issues This Solves
- Device not found errors that resolve on retry
- Connection timeouts on first attempt
- "Out of connection slots" errors on ESP32 devices
- Interference from other Bluetooth operations
- Platform-specific connection quirks
For detailed documentation and advanced usage, see the full documentation.
Contributors ✨
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
Credits
This package was created with Cookiecutter and the browniebroke/cookiecutter-pypackage project template.
Release files for bleak-retry-connector 4.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| bleak_retry_connector-4.7.0.tar.gz | 19.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bleak_retry_connector-4.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.4 kB
Release files / bleak_retry_connector-4.7.0.tar.gz
| Download URL | bleak_retry_connector-4.7.0.tar.gz |
|---|---|
| Size | 19.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
beeeb09e88d77ca161fef312fcb4215fce05bd410bb694132fd4d2ce2969e035
|
|
BLAKE2b-256 checksum How to use checksums |
b8b453e2dbf325292d35f4d18a5648d20420d9c0205260f2ed7b0758e73bc796
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.
Transparency logRelease files / bleak_retry_connector-4.7.0-py3-none-any.whl
| Download URL | bleak_retry_connector-4.7.0-py3-none-any.whl |
|---|---|
| Size | 19.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc799c8665acb38bb1066342bc8a6fc6c397eda8c9476c047ffa1e51146723d6
|
|
BLAKE2b-256 checksum How to use checksums |
745fae12f3da24810d94bb437c8fe3079204c704fcfba2c15ec326dbb0c60aaa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.
Transparency log
