Compatibility Matrix
This matrix tracks tested IDM hardware without publishing private network data. It separates confirmed devices from expected compatibility so users can judge risk before installing.
Status Levels
| Status | Meaning |
|---|---|
confirmed |
Maintainer-tested or backed by a complete diagnostic report with model, firmware and active feature set. |
community-tested |
Reported by users with enough detail to reproduce the setup, but not maintainer-owned hardware. |
expected |
Register map should match, but no complete diagnostic report is available yet. |
unsupported |
Known not to use the Navigator Modbus TCP register model required by this integration. |
Device Matrix
| Heat pump / controller | Status | Firmware | Active capabilities | Verified with | Notes |
|---|---|---|---|---|---|
| IDM 6-15 with Navigator 10 | confirmed | reported by diagnostics | Heating circuit A, PV, Solar, ISC; cascade unavailable sentinel verified | HASS branch tests, API contract tests, repeated read-only Modbus probes | Maintainer test system. Private host, port and network data are intentionally omitted. |
| Navigator 10 / current hardware | community-tested | NAV10_20.23 observed; other versions need evidence | Up to 7 heating circuits, detected zone modules | API register model, diagnostics reports | Heat sink and booster registers are Navigator-10-gated; local web uses the Navigator-10 WebSocket client. |
| Navigator 2.0 | expected | 2.x observed/expected | Heating circuits, optional PV/Solar/ISC/Cascade; zone support not confirmed | API register model, contract tests | A current Terra SWM report still needs a raw model-detection capture; local web uses HTTP/CSRF. |
| Navigator 1.7 | community-tested | n1.x firmware | 1.x sensor map plus the official RW holding block (system/heating-circuit modes, room and flow setpoints, heating curves, limits, bivalence points, solar mode, DHW setpoint); PV supplement (74/76/78/82 writes, 4122 read) when address 74 responds | API register model, contract tests, FHEM capture against a real 1.7 (issue #319) | Separate protocol family; automatic detection via Illegal-Data-Address signature, manual model override available. Holding writes are EEPROM-limited (300 000 cycles per register). Disable the local web supplement; no 1.x web interface is known. |
| Navigator Pro / zone modules | expected | unknown | Detected zone modules, room sensors and room modes | API register model, contract tests | Needs a complete diagnostic report; local web follows the Navigator-10 WebSocket family. |
| Terra SWM with Navigator controller | expected | unknown | Unknown | no complete report yet | Keep as expected until model, firmware and diagnostic export are available. |
| Unknown future Navigator model | expected | unknown | Unknown | no complete report yet | Must be treated as expected until auto-detection and diagnostics prove compatibility. |
| Pre-Navigator controllers | unsupported | any | none | architecture review | Older controllers use different communication/register models. |
Report Requirements
Please include these fields when reporting compatibility:
- Heat pump model and Navigator/controller model.
- Firmware version from diagnostics.
- Integration version and
idm-heatpump-apiversion. - Active heating circuits, zone modules, PV, Solar, ISC and Cascade flags.
- Redacted Home Assistant diagnostics export.
- Whether the report is read-only or includes verified write actions.
Do not publish private IP addresses, hostnames, ports that identify your network, serial numbers or installer/customer data.
Controller generation, heat-pump product name and detected optional capabilities are recorded separately. A family name alone does not prove that PV, Solar, ISC, Cascade or zone hardware is installed.