blesession
One BLE session, instrumented — for Home Assistant BLE integrations built on bleak.
Connect, subscribe to notifications, exchange frames with per-step timeouts, disconnect — and come out the other side with where the time went, where it failed, which radio it went over, and one sentence on what that most likely means, ready to publish as sensor attributes so a failed session at 3 am can be read off the entity without debug logging.
Status
Verified on device over a Bluetooth proxy. The library is tested without
Home Assistant (pytest).
Where to start
| you want to | read |
|---|---|
| integrate a device | docs/adopting.md: a whole integration end to end, what the library writes for you, how to test it without bleak or Home Assistant |
| know exactly what a call guarantees | docs/contract.md: every public name, error, report key, cause key and callback shape, and the versioning rule |
| understand why it is shaped this way | docs/design.md: what belongs here, what deliberately does not, how a Bluetooth-proxy route works without importing Home Assistant |
| see what changed | CHANGELOG.md |
Adopting needs only this repository: the guide and the contract are written so you can integrate a device without reading the source.
The design is extracted from integrations that already carry this instrumentation (and had drifted apart), and is meant to be adopted by others that today each hand-roll the same notification wait and have no failure attribution at all.
Install
pip install blesession
Requires Python 3.13+. The core depends only on bleak / bleak-retry-connector;
blesession.hass imports Home Assistant lazily and is not needed outside HA.
What it provides
| piece | one line |
|---|---|
ble_session() |
connect inside the block (or reuse a link left up), watch the link, bounded disconnect in finally |
Notifications |
queued replies from one characteristic; every wait names its step and ends the moment the link drops; request() is write-then-reply |
write_chunks() / guarded_write() |
a payload as consecutive writes; every write is bounded and a dropped link ends it as SessionDropped |
characteristic_or_raise() |
the service/characteristic lookup with required properties and write size, or GattMismatch |
SessionTrace |
nested stage timings; the innermost stage an exception escaped from |
| stage vocabulary | unreachable · connect · session · auth · transfer · finish · disconnect, plus a device detail |
run_attempts() |
the lock-per-attempt / fresh-handle-per-attempt contract; policy stays yours |
blesession.hass.ble_device_or_raise() |
the handle, resolved fresh inside the attempt, or Unreachable |
blesession.hass.radio_facts() |
via, via_type, rssi, paths, advertised_via as scanner names, and via_unconfirmed (a flag) |
link.py |
the one place that probes bleak / habluetooth internals for the radio a link took |
blesession.testing |
FakeClient / fake_connect() so every integration's tests fake bleak the same way |
build_report() |
fixed attribute key order; generic likely-cause sentences with a translatable key, your device sentences first |
SessionReports |
the last session and the last failure, so a success does not erase the evidence |
| errors | ConnectionError subclasses so an off device never becomes a traceback; retryable says whether another attempt can help; DeviceError is yours to raise for a device-reported fault |
Failure |
what your cause callback receives: the stage, the error, the radio facts |
What it does not provide
Retry counts, backoff, packet pacing, lock scope, bonding and pairing, cooldowns, advertisement parsing, protocol frames. Those are the parts each integration learned from its own device and keeps.
Layout
src/blesession/ pure Python + bleak, tested without Home Assistant
src/blesession/hass.py imports homeassistant lazily; only used inside HA
docs/adopting.md how to use it, with a whole integration
docs/contract.md what every name guarantees; versioning and deprecation
docs/design.md why it is shaped this way
from blesession import Notifications, SessionTrace, ble_session, build_report, stages
trace = SessionTrace(stage_map={"start": stages.AUTH})
try:
async with ble_session(ble_device, trace=trace) as client:
async with Notifications(client, NOTIFY_UUID, settle=0.5) as replies:
with trace.timed("start"):
await client.write_gatt_char(WRITE_UUID, START, response=False)
await replies.next(timeout=5, step="start")
with trace.timed("transfer"):
...
except ConnectionError as exc: # every session error is one
report = build_report(operation="write", trace=trace, exc=exc,
facts=radio_facts(hass, address, trace.link), noun="device")
# {'operation': 'write', 'success': False, 'error': ..., 'failed_stage': 'auth',
# 'failed_detail': 'start', 'likely_cause': ..., 'via': ..., 'connect_s': ..., ...}
Development & testing
pip install -e ".[dev]"
pytest # unit tests; FakeClient fakes bleak the same way for adopters
ruff check . && ruff format --check .
mypy # type-check src/ (the package ships py.typed)
python -m build
CI runs on every push/PR (.github/workflows/ci.yml): ruff lint+format, mypy,
the test suite on Python 3.13/3.14 (plus a lowest-pinned-dependencies job), and
a build that asserts py.typed and the licence are in the wheel.
Releasing: add a version section to CHANGELOG.md
(behaviour changes go under Changed with before/after), bump version in
src/blesession/__init__.py, and merge. Then create a GitHub Release whose
title and tag use the version name (for example, v0.5.0). Publishing the
release triggers .github/workflows/release.yml to build and publish to PyPI
with trusted publishing.
License
MIT
Metadata
Release files for blesession 0.8.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 | |
|---|---|---|---|
| blesession-0.8.0.tar.gz | 88.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| blesession-0.8.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 130.3 kB
Release files / blesession-0.8.0.tar.gz
| Download URL | blesession-0.8.0.tar.gz |
|---|---|
| Size | 88.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ebbeba75d842ea7836c89f4063ef18c56dd6e4b85582b2c810bd39e5c6dac8c
|
|
BLAKE2b-256 checksum How to use checksums |
dc61b1eb4efe689c1bdfea9e7e11a91bd07a5ddab3c1855b42d20450d464ff92
|
| 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 Oct 4, 2026.
Transparency logRelease files / blesession-0.8.0-py3-none-any.whl
| Download URL | blesession-0.8.0-py3-none-any.whl |
|---|---|
| Size | 42.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
baccbe7afe7b9e46511ccdd4cf1e260213733d249fa1b1ba5cdc7751886ea149
|
|
BLAKE2b-256 checksum How to use checksums |
1e0e66bdffa63b8b701b4ae69bc0932027d5bed1780ee71ea355111c419c7bf6
|
| 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 Oct 4, 2026.
Transparency log