HomeMatic
HomeMatic IP Devices
Other · And More
RequestedVerified plugin
1 report: 1 asks for support.
Reported with 1 Homebridge plugin: FHEM.
What people report
| Plugin | Status | What they said | Connects | Source |
|---|---|---|---|---|
FHEM Verifiedhomebridge-fhem | Requested | Only generic on/off detected; support PR still openSaved copyHMCCUCHN and HMCCUDEV devices are currently only picked up by the generic on/off branch in `FHEMAccessory()`. Every other detection branch keys off CUL_HM specifics that a HMCCU device does not have, `attr subType`, and the `state`/`pct`/`desired-temp` readings, so HomeMatic IP switches, dimmers, blinds and thermostats all end up as switches bound to a `state` reading that never updates, and the sensors are not exposed at all. The only HMCCU-aware code today is `this.model`/`this.serial` in the device info block. Approach Readings are looked up by datapoint name rather than hardcoded, so … Excerpt saved from GitHub on 2026-10-22. | Local | PR #126 · 2026-08 |
Each row is one report from a plugin’s GitHub issues, pull requests, discussions, wiki or docs, or from r/homebridge. Check the date and the linked thread before you buy.
In ReReHome
Once a Homebridge plugin publishes it, this device reaches Apple Home as a HomeKit accessory behind your Homebridge bridge, so ReReHome shows and controls it like any other.
Identifiers
| Brand | HomeMatic |
|---|---|
| Category | Other |
Also reported as
- HomeMatic IP devices via HMCCU