lighthouse-ble
Async Bluetooth LE control of SteamVR Lighthouse base stations — Valve Index (V2, LHB-…) and
HTC Vive (V1, HTC BS …). Built to back a Home Assistant integration, usable on its own.
| V2 (Valve Index) | V1 (HTC Vive) | |
|---|---|---|
| Power | on / standby / sleep | on / sleep |
| State | passive from advertisements, or GATT read | not readable (optimistic) |
| Identify (blink LED) | yes | — |
| Channel 1–16 | read / write | — |
V2 stations advertise their power state, channel and fault flag, so state updates need no
connection. Waking from sleep takes about 11 s (reported as booting), from standby about 1 s.
Install
uv add lighthouse-ble # as a library dependency
uvx lighthouse-ble scan # run the CLI without installing
Command line
lighthouse-ble scan # list stations with passive state
lighthouse-ble scan --raw # every advertisement with raw bytes and intervals
lighthouse-ble info LHB-1A2B3C4D # device information + GATT state
lighthouse-ble on LHB-1A2B3C4D
lighthouse-ble standby LHB-1A2B3C4D
lighthouse-ble off LHB-1A2B3C4D
lighthouse-ble identify LHB-1A2B3C4D
lighthouse-ble channel LHB-1A2B3C4D 5
lighthouse-ble off "HTC BS 12AB34" --v1-id 1A2B # V1: first 4 hex digits from the back label
Stations can be addressed by name or BLE address. --scan-time changes how long to look
(default 10 s).
Library
import asyncio
from lighthouse_ble import PowerState, create_base_station, discover
async def main() -> None:
for found in await discover(5):
station = create_base_station(found.device, found.advertisement)
print(station.name, station.state)
await station.set_power(PowerState.ON)
asyncio.run(main())
In Home Assistant, feed advertisements from the bluetooth integration instead of scanning:
adv = parse_advertisement(service_info.name, service_info.manufacturer_data)
station.set_ble_device(service_info.device)
station.update_from_advertisement(adv)
unsubscribe = station.register_callback(lambda state: ...)
Every command opens a short connection and disconnects again, so no ESPHome proxy slot stays
taken. Errors are always LighthouseError subclasses.
Development
uv sync
uv run pytest --cov=lighthouse_ble
uv run mypy
uv run ruff check . && uv run ruff format --check .
License
Apache-2.0
Metadata
Release files for lighthouse-ble 0.1.1
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 |
|---|---|---|---|---|
| lighthouse_ble-0.1.1.tar.gz | 67.4 kB | With provenance | Details for lighthouse_ble-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lighthouse_ble-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for lighthouse_ble-0.1.1-py3-none-any.whl |
Total release size: 85.8 kB
Release files / lighthouse_ble-0.1.1.tar.gz
| Download URL | lighthouse_ble-0.1.1.tar.gz |
|---|---|
| Size | 67.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa422658dcd9528faa1ebdfb6e9b7c4cf67bd888d8f2897f86ecd63cf1b67dc0
|
|
BLAKE2b-256 checksum How to use checksums |
f7dca23e610215d9ebb235f474b3d39a7ce4ca749fd355cdefcc79059f0de1c1
|
| 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 / lighthouse_ble-0.1.1-py3-none-any.whl
| Download URL | lighthouse_ble-0.1.1-py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d23f0c72054762534a977d25bacdcbe1a7b6eb22db7aa7fef712948f32b63e3
|
|
BLAKE2b-256 checksum How to use checksums |
693e16705e127b59566abce1ed175cc3150c7cfca5849fc022f17576e17a2766
|
| 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 logSecurity for lighthouse-ble 0.1.1
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
Both files in this release have been uploaded with provenance metadata.
Attestation for lighthouse_ble-0.1.1.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 Sep 28, 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.