This release is a pre-release and may not be stable for production use.
solem-blip-ble
Python library for the Solem BL-IP Bluetooth irrigation controller.
Protocol sources
| Layer | Source |
|---|---|
| Commands (turn on/off, sprinkle, stop, commit) | pcman75/solem-blip-reverse-engineering — GATT write 108b0002-..., frame 3105 … + 3b00 |
Status polling (notify, seq 0x02, active station, remaining time, battery) |
Live BL-IP V5 hardware validation and capture-backed regression tests; see docs/ble_protocol.md |
Turn-off-for-N-days is capped at 15 days per the pcman75 documentation.
Install
pip install solem-blip-ble
# or from GitHub:
pip install "solem-blip-ble @ git+https://github.com/beelzetron/solem-blip-ble.git@main"
# or editable for development (prefer uv; deps are hash-locked via uv.lock):
uv sync --frozen
CI/CD
- CI: GitHub Actions runs tests (Python 3.11–3.13) and verifies the package builds on every push/PR to
main. - CD: Creating a GitHub Release publishes the package to PyPI via trusted publishing.
Configure PyPI trusted publishing for this repository: PyPI project → Publishing → Add GitHub Actions publisher (beelzetron/solem-blip-ble, workflow publish.yml, environment pypi).
Usage
from solem_blip_ble import SolemClient, SolemConnectionError
client = SolemClient("AA:BB:CC:DD:EE:FF", bluetooth_timeout=30)
await client.connect()
status = await client.get_status()
await client.sprinkle_station_x_for_y_minutes(1, 5)
await client.stop_manual_sprinkle()
await client.disconnect()
Documentation
Full BLE protocol notes: docs/ble_protocol.md
Validation CLI
The packaged debug tool is the single supported raw capture path:
validate-solem-blip AA:BB:CC:DD:EE:FF --capture --verbose
validate-solem-blip AA:BB:CC:DD:EE:FF --capture --only status
validate-solem-blip AA:BB:CC:DD:EE:FF --capture-off-days 3 --verbose
validate-solem-blip AA:BB:CC:DD:EE:FF --replay btsnoop/captures/capture.jsonl
Regression tests also replay public capture-backed fixtures for V5 firmware, station names, status, and persisted irrigation schedule parsing.
Home Assistant
Used by the Solem BL-IP for Home Assistant integration (HACS).
Credits
Thanks to pcman75 for the original Solem BL-IP command reverse engineering.
1 maintainer
Release files for solem-blip-ble 0.2.2b1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| solem_blip_ble-0.2.2b1.tar.gz | 62.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| solem_blip_ble-0.2.2b1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 109.0 kB
Release files / solem_blip_ble-0.2.2b1.tar.gz
| Download URL | solem_blip_ble-0.2.2b1.tar.gz |
|---|---|
| Size | 62.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
48caeaa9888ede1d25df1fffe9ac26956720b5d0b16a109e6f4280e93d7d35bc
|
|
BLAKE2b-256 checksum How to use checksums |
a489fe930de42111c05d5aadc341515797fd4709e1f82db903f7d4f6ed28d374
|
| 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 12, 2026.
Transparency logRelease files / solem_blip_ble-0.2.2b1-py3-none-any.whl
| Download URL | solem_blip_ble-0.2.2b1-py3-none-any.whl |
|---|---|
| Size | 47.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
958fd2bbc7ac191f2d7b2d7720619e226293ef1f809b7bc0aa55999e06b79fa8
|
|
BLAKE2b-256 checksum How to use checksums |
8f73744f7834124d1ee4112fd4bda94397d7328a1fe160bf938c96e2a20c0ce0
|
| 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 12, 2026.
Transparency log
