Casambi Classic BLE Library
An asynchronous Python library for controlling Casambi lighting devices running Classic firmware via Bluetooth Low Energy (BLE).
Classic vs. Evolution Firmware
Casambi networks operate under one of two major radio profiles: Evolution or Classic.
How to check your network profile
Open the official Casambi App → Select your network → More (...) → Network setup → Network configuration → Look at Radio profile:
- Classic: Use
casambi-classic-ble(this library). - Evolution: Use upstream
casambi-bt.
Why this specialized fork exists
Classic networks rely on different GATT services (0xFE3D, 0xFE4D), different challenge-handshakes, and passive manufacturer advertisement beacons (0x03C3 / 963). This library provides native, standalone support for Classic devices without cloud lock-in.
Which API Should I Use?
casambi-classic-ble provides two client interfaces depending on your integration needs:
| Capability / Requirement | CasambiDevice |
Casambi |
|---|---|---|
| Primary Use Case | Direct BLE GATT control for single nodes or mesh gateway | Full network topology discovery, scene switching, group control |
| Downstream Consumer | casambi-classic-bt-hass (Home Assistant) |
Standalone network automation & scripting tools |
| Cloud / Topology Dependency | Zero. Connects directly via Bluetooth address. | Requires network configuration via Casambi Cloud or local cache. |
| Authentication | Optional network password write (0x07 MD5 hash). |
Challenge-response authentication with CMAC-signed packets & KeyStore. |
| Unit Targeting | Target any unit ID directly (unit_id=1). |
High-level Unit and Group model instances. |
| Scene Support | Not supported directly. | Native switch_to_scene() support. |
| State Feedback | Passive BLE manufacturer advertisement beacons (0x03C3). |
BLE GATT notification stream or Cloud WebSocket bridge. |
| Verified Hardware | Vadsbo LD220WCM, LD220WCM_onoff, CBU-PWM4, AIMOTION GLOW | Classic firmware networks (protocol versions 1–9). |
Features
- 🎯 Classic-First Architecture: Tailored specifically for Casambi Classic firmware devices.
- 🔍 BLE Discovery & Scanner: Discover Classic Casambi nodes and decode passive manufacturer advertisement data.
- 📡 Passive State Tracking: Read on/off and dimming levels directly from BLE advertisements with duplicate frame suppression.
- 🔌 Direct BLE Control: Connect directly over Bluetooth Low Energy without mandatory cloud intermediaries.
- 💡 Lighting Controls: Turn lights on/off, set brightness dim levels, color temperature (Kelvin), and RGB colors.
- 🛡️ Robust Concurrency: Serialized GATT writes via
asyncio.Lockand domain exception raising. - ☁️ Cloud Sync (Optional): Optional Casambi Cloud API and WebSocket bridge for topology sync.
Installation
pip install casambi-classic-ble
Or from source:
git clone https://github.com/hellqvio86/casambi-classic-ble.git
cd casambi-classic-ble
pip install -e .
Quick Start
1. Controlling a Device by Address
import asyncio
from casambi_classic_ble import CasambiConnectionError, CasambiDevice
async def main():
# Target your node by Bluetooth address (or pass a Bleak BLEDevice from Home Assistant)
light = CasambiDevice(address="AA:BB:CC:DD:EE:FF")
try:
await light.connect()
except CasambiConnectionError as err:
print(f"Could not connect to {light.address}: {err}")
return
try:
# Optional: Authenticate if your network requires a password
# (Only needed if the network is password-protected and unauthenticated writes are rejected)
# await light.authenticate(password="your_network_password")
# Control a specific unit (e.g. Unit 1)
await light.turn_on(unit_id=1)
await light.set_level(unit_id=1, level=0.75)
await light.set_color_temperature(unit_id=1, temp_kelvin=3000)
await light.set_rgb(unit_id=1, r=255, g=200, b=100)
# Or control all units across the mesh (omit unit_id or use broadcast)
# await light.turn_on()
# await light.turn_off()
finally:
await light.disconnect()
asyncio.run(main())
2. Discovery & Bring-Your-Own-Scanner (Home Assistant)
import asyncio
from casambi_classic_ble import CasambiConnectionError, CasambiDevice, CasambiScanner
async def main():
scanner = CasambiScanner()
devices = await scanner.scan(duration=5.0)
# Filter for your specific device by Bluetooth address rather than connecting blindly
target = next((d for d in devices if d.address.upper() == "AA:BB:CC:DD:EE:FF"), None)
if target:
try:
await target.connect()
await target.turn_on(unit_id=1)
except CasambiConnectionError as err:
print(f"Failed to connect to {target.address}: {err}")
finally:
await target.disconnect()
asyncio.run(main())
3. Passive State Tracking & Subscriptions
from casambi_classic_ble import CasambiDevice
device = CasambiDevice(address="AA:BB:CC:DD:EE:FF")
def on_state_change(state: dict):
# Decoded passive broadcast state dictionary containing verified status
print(f"State updated: {'ON' if state['on'] else 'OFF'} ({state['level_percent']}%)")
# Register subscription callback (automatically deduplicates identical frames)
unsubscribe = device.register_state_callback(callback=on_state_change)
# Feed raw manufacturer data (0x03C3) received from Bleak or Home Assistant
def on_advertisement(mfr_data: bytes):
device.update_from_advertisement(mfr_data=mfr_data)
4. Optional Cloud API Bridge
Install with cloud extras: pip install casambi-classic-ble[cloud]
import asyncio
from casambi_classic_ble import CasambiCloud
async def main():
# Required credentials:
# - api_key: Casambi developer API key
# - email & user_password: User account credentials
# - network_password: Password of the specific lighting network
async with CasambiCloud(
api_key="your_api_key",
email="user@example.com",
user_password="password",
network_password="network_password",
) as cloud:
await cloud.create_user_session()
await cloud.create_network_session()
net_info = await cloud.get_network_information()
print("Discovered cloud network information:", net_info)
asyncio.run(main())
Hardware Compatibility & Limitations
- Supported Hardware (Verified in Production):
- Vadsbo LD220WCM (Trailing-edge phase-cut dimmer)
- Vadsbo LD220WCM_onoff (On/off relay module)
- Casambi CBU-PWM4 RGBW (4-channel PWM dimmer)
- AIMOTION GLOW (Pendant luminaire)
- All running Casambi Classic firmware (v26.x or earlier).
- Command Variants & Hardware Evidence: See the Command Variant & Hardware Compatibility Matrix in
docs/protocol.mdfor exact opcode payloads (1-byte vs 2-byte unit IDs), verified models, and capture provenance. - Concurrent Connections: Casambi mesh nodes typically allow only one active BLE connection at a time. If the official Casambi mobile app is actively connected to a node, connection attempts from other clients will be rejected until the app disconnects.
- Protocol Details: See docs/protocol.md for characteristic UUIDs, opcodes, signed session packets, and Wireshark capture guides.
Troubleshooting
Connection Times Out While Casambi App Is Open
Casambi mesh nodes strictly allow only one active Bluetooth Low Energy GATT connection at a time. If the official Casambi mobile app (iOS or Android) is open in the foreground or background on a smartphone or tablet in range, it will hold the GATT connection to the node. Any connection attempt from casambi-classic-ble or Home Assistant will time out with a CasambiConnectionError.
Solution: Force-close or background-disconnect the official Casambi mobile app before connecting with casambi-classic-ble.
Troubleshooting
- Linux / BlueZ Permissions: Non-root users may need permission to access Bluetooth adapters via D-Bus:
sudo usermod -a -G bluetooth $USER
- BlueZ Version: BlueZ
>= 5.64is strongly recommended for reliable BLE GATT operation and connection stability. - Connection Drops / Timeouts: If connecting directly, ensure the target node is within adequate RF range and no mobile app has an active session open. Using
casambi-classic-bt-hassleverages Home Assistant's proxying Bluetooth architecture automatically.
Contributing & Security
- Contributing: See CONTRIBUTING.md and AGENTS.md for development setup, coding standards, and pull request guidelines.
- Security Policy: See SECURITY.md for vulnerability disclosure procedures and private reporting channels.
- Protocol Documentation: See docs/protocol.md for packet formats, opcode tables, and Wireshark capture guides.
Acknowledgements & Attribution
This library is a specialized fork of casambi-bt, originally created by Lukas Kempf (@lkempf). We are immensely grateful to Lukas Kempf and the upstream contributors for their pioneering reverse-engineering and BLE protocol architecture.
See ATTRIBUTION.md for detailed attribution and fork history.
Authors & Maintainers
- Lukas Kempf (@lkempf) — Original author and creator of
casambi-bt - Olof Hellqvist (@hellqvio86, olof.hellqvist@gmail.com) — Maintainer of the
casambi-classic-blefork
License
This project is licensed under the Apache License, Version 2.0 — see the LICENSE file for the full text.
Metadata
Release files for casambi-classic-ble 0.8.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 |
|---|---|---|---|---|
| casambi_classic_ble-0.8.1.tar.gz | 66.0 kB | With provenance | Details for casambi_classic_ble-0.8.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| casambi_classic_ble-0.8.1-py3-none-any.whl | Python 3 | none | any | Details for casambi_classic_ble-0.8.1-py3-none-any.whl |
Total release size: 137.2 kB
Release files / casambi_classic_ble-0.8.1.tar.gz
| Download URL | casambi_classic_ble-0.8.1.tar.gz |
|---|---|
| Size | 66.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47c36af69f78e307cb2e4bb11b87931a32c7aca40fac581f6eb142f8a2f7daf5
|
|
BLAKE2b-256 checksum How to use checksums |
511cdf1486abf8632ec9c3896d6f1c4edb620a3c6eb725f7f28154dd0415723b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 1, 2026.
Transparency logRelease files / casambi_classic_ble-0.8.1-py3-none-any.whl
| Download URL | casambi_classic_ble-0.8.1-py3-none-any.whl |
|---|---|
| Size | 71.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
73c2e7d6e6ba539df94bf546b1656bf569b8a0b7d25bfb11e3f63aad75f78ca3
|
|
BLAKE2b-256 checksum How to use checksums |
290d1f733b2ec4b2c7720112e04313c4744606ea7f783d32d793dda937780d14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 1, 2026.
Transparency logSecurity for casambi-classic-ble 0.8.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for casambi_classic_ble-0.8.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 Nov 1, 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.