Victron BLE HA Parser
Overview
This project exists solely to provide an interface to the excellent
victron-ble project suitable for use with a Home
Assistant integration. Thank you to Keshav Varma for maintaining the victron-ble project.
Installation
This package is available on PyPI:
pip install victron-ble-ha-parser
Installing the Home Assistant custom component
Currently the Home Assistant integration is only available as a custom component, for testing purposes. The goal is to make this part of Home Assistant core.
If you'd like to test this, clone my fork on the HA project and checkout the victron-ble-custom-component branch:
git clone https://github.com/rajlaud/home-assistant.git --branch victron-ble-custom-component
Then, copy or symlink homeassistant/components/victron-ble into your config/custom_components folder.
Details
The parser module has one class, VictronBluetoothDeviceData, which parses Bleak advertisements and
updates itself with the sensor data from the advertisement. Each instance of
VictronBluetoothDeviceData should be fed advertisements from exactly one Victron device (based on
the MAC address) and the instance needs to be initiated with the encryption key of the device that
is going to be sending updates. If the encryption key is set correctly everything else will be
figured out automatically.
There is a handy package from maintainers of the HA project called sensor-state-data to make it
easy to automate ingesting sensor state updates like this. Unfortunately, we need to use a unit
(amp-hours) not supported by the module and my PR to include amp-hours was rejected because they are
not a common unit (https://github.com/Bluetooth-Devices/sensor-state-data/pull/47). For that
reason, we need a custom extension of sensor-state-data, which is contained in the
custom-sensor-state.py file.
1 maintainer
Metadata
1 maintainer
Release files for victron-ble-ha-parser 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 | |
|---|---|---|---|
| victron_ble_ha_parser-0.8.0.tar.gz | 13.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| victron_ble_ha_parser-0.8.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.6 kB
Release files / victron_ble_ha_parser-0.8.0.tar.gz
| Download URL | victron_ble_ha_parser-0.8.0.tar.gz |
|---|---|
| Size | 13.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d03afc8a7bb323b39e320eb1ff16572d092238e74e38976be034f7172d975d16
|
|
BLAKE2b-256 checksum How to use checksums |
bcc8ec625cd519e48da82e6dc15cb8d11d20142b694b93adeb3828b926e185fa
|
| 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 Sep 28, 2026.
Transparency logRelease files / victron_ble_ha_parser-0.8.0-py3-none-any.whl
| Download URL | victron_ble_ha_parser-0.8.0-py3-none-any.whl |
|---|---|
| Size | 11.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5629c3c27139d56947c759d609c291a347f008fbbc4945dc5fd2dc5f702a317e
|
|
BLAKE2b-256 checksum How to use checksums |
4dbe446c105ad80d5ac12267c61412a8b13113c6e60cd9ae766a5bfa48af4571
|
| 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 Sep 28, 2026.
Transparency log
