Technische Alternative C.M.I.
DeerMaximum/Technische-Alternative-CMI · vv1.13.1
Custom Home Assistant integration to read data from a C.M.I.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) |
What people report
C.M.I. works over local JSON API with DL-Bus and CAN-Logging; firmware API quirks and old CAN-IO nodes cause setup failures.
- Works2
- Not working2
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Technische Alternative C.M.I. CAN-Logging | Works Local | CAN-Logging support addedSaved copyAdd support for CAN-Logging. Fix #10 Excerpt saved from GitHub on 2026-10-23. | PR #11 · 2022-10 | |
| Technische Alternative UVR610 (DL-Bus) | Works Local | DL-Bus support addedSaved copyFixes #24 Excerpt saved from GitHub on 2026-10-23. | PR #29 · 2023-01 | |
| Technische Alternative CAN-IO module (node 32) | Not working Local | C.M.I. returns DEVICE NOT SUPPORTED, config flow hangs; owner could not reproduceSaved copyDescription When I try to set up the "Technische Alternative C.M.I." integration, the config flow never finishes (spinner runs forever). In the logs I see: > Invalid device: 32 I have an older CAN-IO module on the CAN bus (node 32). As soon as this device is connected, the integration fails during setup. If I access the CMI JSON API directly, it works fine: `http:// /INCLUDE/api.cgi?jsonnode=1&jsonparam=I` This returns valid JSON with `Status: "OK"`. ## Environment - Home Assistant: Home Assistant Core 2025.11.2 - Technische Alternative C.M.I. integration version: V1.9.14 - Installation … Excerpt saved from GitHub on 2026-10-23. | Issue #149 · 2025-11 | |
| Technische Alternative UVR65 with CMI firmware 1.46.1 | Not working Local | CMI API v8 returns invalid JSON for empty outputs; config flow failsSaved copySetup - Integration version: 1.13.1 - Home Assistant version: 2026.8.x - CMI firmware: 1.46.1 (JSON API Version 8) - Device: UVR65, CAN node 13 ## Problem Since CMI firmware 1.46.1 (API Version 8, released October 2025), the JSON API returns invalid JSON for output slots that are not configured on the device: GET /INCLUDE/api.cgi?jsonnode=13&jsonparam=O Response contains: "Outputs":[ { "Number":27, } { "Number":28, } ... ] These entries have a trailing comma and no "Value" field, both are invalid JSON. Python's json parser raises a JSONDecodeError, which causes the config flow to show: … Excerpt saved from GitHub on 2026-10-23. | Issue #208 · 2026-09 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local polling
Talks to the device on your network, asking it for updates every so often.
Details
| Installs (analytics) | 359 (0.05%) |
|---|---|
| GitHub stars | 64 |
| Latest version | v1.13.1 (2026-09-08) |
| Set up in the UI | Yes |
| Maintainers | @DeerMaximum |
| License | MIT |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
