Skip to main content

EVBox BLE

Library extraction for Home Assistant Core consideration. Releases are published on PyPI. The released HACS integration does not yet use this package. Source and CI are maintained at CReimer/evbox-ble; report library defects in its issue tracker.

Asynchronous local BLE sessions for EVBox Gen4 chargers, including authentication, configuration and the legacy EVBox/OCPP framing protocol. The protocol and client originate in the Apache-2.0 project CReimer/evbox-g4-ble, revision 5fbeec3dddbc107deac87a46f12b670b4ca3f264. No vendor applications or firmware are included.

Supply a synchronous device provider so the latest connectable adapter or Bluetooth proxy can be selected for each new session. The library has no dependency on Home Assistant. For a direct Bleak application:

from bleak import BleakScanner
from evbox_ble import EVBoxClient

device = await BleakScanner.find_device_by_address(address)
client = EVBoxClient(address, security_code, ble_device_callback=lambda: device)
config = await client.get_configuration(["evb_BootInfo"])

For Home Assistant, the integration adapter supplies lambda: bluetooth.async_ble_device_from_address(hass, address, connectable=True). A missing device raises EVBoxConnectionError; rejected authentication raises EVBoxAuthError.

Transactions serialize complete operations. A snapshot reuses one authenticated BLE session. Legacy and ESP32 characteristic layouts are supported. Optional unavailable commands are distinguished from required command failures.

See the API guide for installation, parameters, command results, authentication and transport errors, cancellation, limitations, troubleshooting, and removal.

The 75 tests use simulated BLE notifications and malformed protocol inputs without hardware. CI requires 100% line and branch coverage, strict type checking, linting, formatting, and isolated tests of the wheel and a wheel rebuilt from the source distribution. See quality requirements and the changelog. Run python -m unittest discover -s tests; build source and wheel artifacts with python -m build. The public GitHub Actions workflow tests Python 3.11 and 3.14, builds both source and wheel distributions, and publishes version tags using PyPI Trusted Publishing. PyPI provenance identifies the repository, workflow and publishing environment. Initial library extraction does not include the Home Assistant firmware/FTP orchestration; any later Core firmware platform must move device communication into the library as well.

Metadata

Release files for evbox-ble 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for evbox-ble 0.1.2
File Size Uploaded
evbox_ble-0.1.2.tar.gz 34.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for evbox-ble 0.1.2
File Interpreter ABI Platform
evbox_ble-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 53.9 kB

Release files / evbox_ble-0.1.2.tar.gz

Download URL evbox_ble-0.1.2.tar.gz
Size 34.2 kB
Tags Source
SHA-256 checksum
How to use checksums
97d92a05018b156bbc602dc4e896543b15ee50bdff9ef8ab5a326ce856cb78a1
BLAKE2b-256 checksum
How to use checksums
4d12e983d2647df0b0e4ea41f95824f9543a6418b939f252710aaa8d2985647b
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 8, 2026.

Transparency log

Release files / evbox_ble-0.1.2-py3-none-any.whl

Download URL evbox_ble-0.1.2-py3-none-any.whl
Size 19.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e5e7b07a0a2d9160f1fe27b4a4c1099d899c216484d5f8283eda1a29f94a9267
BLAKE2b-256 checksum
How to use checksums
a657691e213dbd76021ac0691894c14fe2af4a337b2e12436ea0eba9d0d0e674
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 8, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page