aio-rfcomm
Talk to Bluetooth Classic serial devices from asyncio — the same way on Linux, macOS and Windows.
async with (
aio_rfcomm.open_bluetooth() as bluetooth,
bluetooth.open_service(DEVICE, MY_SERVICE) as channel,
):
await channel.send(b"hello\n")
while True: # until the connection ends, raising ChannelClosedError
print((await channel.receive()).decode(), end="")
That is the whole idea. RFCOMM is how many Bluetooth gadgets that predate BLE still talk — printers, GPS units, robots, serial adapters, a great many embedded boards — and reaching one from Python has meant a different library, a different API and a different set of surprises on every platform.
This is one API for all three, running in your own event loop, with every
connection owned by an async with block that cleans up after itself.
Install
$ uv add aio-rfcomm
It needs Python 3.11 or newer. The documentation is at https://dlech.github.io/aio-rfcomm/.
Serving, too
Publish a service and let devices connect to you:
async with bluetooth.serve(MY_SERVICE, name="my thing") as service:
async for request in service.connection_requests():
... # accept it, in a task of your own
Metadata
Release files for aio-rfcomm 1.0.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 | Provenance | Actions |
|---|---|---|---|---|
| aio_rfcomm-1.0.0.tar.gz | 108.9 kB | With provenance | Details for aio_rfcomm-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aio_rfcomm-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for aio_rfcomm-1.0.0-py3-none-any.whl |
Total release size: 247.3 kB
Release files / aio_rfcomm-1.0.0.tar.gz
| Download URL | aio_rfcomm-1.0.0.tar.gz |
|---|---|
| Size | 108.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d4458519ecbe437967623b6ad72815294bbff7213a6d18152087cb98f233651
|
|
BLAKE2b-256 checksum How to use checksums |
fff9d0123d34731da8b544376ff29bef60842ef0c587223b240ff11fc276ad68
|
| 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 18, 2026.
Transparency logRelease files / aio_rfcomm-1.0.0-py3-none-any.whl
| Download URL | aio_rfcomm-1.0.0-py3-none-any.whl |
|---|---|
| Size | 138.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
88e6a12f3023cc6e46b74a306d0b501185f6eefc6faa53844a2d62acac5f7f95
|
|
BLAKE2b-256 checksum How to use checksums |
6a2885ff0a652fa0609f894c9afbbe17f02a168e40e9e403ac574b3ab3bcd565
|
| 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 18, 2026.
Transparency logSecurity for aio-rfcomm 1.0.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for aio_rfcomm-1.0.0.tar.gz
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 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.