EVBox BLE
Library extraction for Home Assistant Core consideration. This package is not yet published on PyPI and is not used by the released HACS integration. 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.
Tests use simulated BLE notifications and malformed protocol inputs without hardware. Run python -m unittest discover -s tests; build source and wheel artifacts with python -m build. Before publication, configure a public library repository, issue tracker and public CI publishing workflow with PyPI Trusted Publishing. 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.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 | |
|---|---|---|---|
| evbox_ble-0.1.0.tar.gz | 25.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| evbox_ble-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.9 kB
Release files / evbox_ble-0.1.0.tar.gz
| Download URL | evbox_ble-0.1.0.tar.gz |
|---|---|
| Size | 25.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
82781f1d0429a3ad87e0d71bad8ed54fe119f72939af1db9e5b0afaea7659e99
|
|
BLAKE2b-256 checksum How to use checksums |
839ab5cfcbbd820bd1dd4266cf084e5f5ac82a6e1e84c9e2e549dbaa411096cd
|
| 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 logRelease files / evbox_ble-0.1.0-py3-none-any.whl
| Download URL | evbox_ble-0.1.0-py3-none-any.whl |
|---|---|
| Size | 19.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b9f5554244bb72c55701e604d005213e443b702576bb5c4f2622496fb2e08fea
|
|
BLAKE2b-256 checksum How to use checksums |
0f9120110769296a26c3ccf5e3302a2bd2149e1848108e403c7cda66a2af0475
|
| 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