Entities

Smart feature entities

The optional Smart Energy & Comfort profile adds electrical and thermal energy totals for lifetime, day and month, COP for the same periods, estimated costs, CO₂ and optional PV use, plus compressor-cycle and operating analysis. These are derived values, not additional physical meters. The required power registers must be available.

Health Monitor adds eight problem checks and a report sensor. Heating-curve and weather advisers add read-only recommendations. The optional comfort schedule changes the existing circuit room target; it does not create a second climate controller entity. Automatic DHW charging uses the existing boost controls and state machine.

With device hierarchy enabled, iDM Analytics, iDM Health Monitor, iDM Comfort and Diagnostics separate these features from controller entities. Disabling optional features removes their entity registrations; re-enabling them restores the same IDs. Existing controller IDs are retained.

The integration dynamically generates entities based on your heat pump configuration (heating circuits, zones, optional features).

Entity Platforms

Exact counts depend on the detected model, active heating circuits, zones, rooms and optional features. Adding circuits, zones, cascade, technician codes or web supplement data can add entities.

Entities are grouped by function in Home Assistant where possible. The optional technician code sensors are pinned at the top, followed by configuration entities, switches, writable values, live measurements and diagnostics.

Entity names and languages

Entity names come from the integration's translation files and follow the language configured in Home Assistant: an English installation shows English names, a German one shows the German names the integration has always used. Heating circuits and zone rooms share one name per measurement and fill in their circuit letter or zone/room number, for example Heating circuit A flow temperature and Zone 1 room 2 temperature.

Changing the Home Assistant language changes the displayed names only. Entity IDs and unique IDs stay exactly as they are, so dashboards, automations and long-term statistics keep working. An entity created after a language change derives its entity ID from the name in that language, as with every Home Assistant integration.

Sensors

Runtime diagnostics

This sensor remains available even if heat-pump polling fails, making it useful when collecting information for a bug report. The direct socket runtime is identified by the modbus_connection_version and tmodbus_version attributes.

Technician-level access codes

When enabled in the integration options, two additional sensors expose the current access codes for Fachmann Ebene 1 and Fachmann Ebene 2. They update once per minute, are placed at the top of the IDM device entity list and are not Modbus registers.

The option is disabled by default. Treat the values as sensitive: limit access to their dashboard cards and never publish them in screenshots, logs or support requests. See Configuration for setup and security guidance. The calculation method is deliberately not documented.

System Temperatures & Pressures

Navigator 10 — Heat Sink (Trennwärmetauscher)

Compressors & Pumps

Energy & Power

PV / Energy Management

Battery SOC accepts 0–100; -1 means that no battery value is available. Treating address 86 like the surrounding two-register FLOAT values produces an implausible result.

PV surplus operation (derived diagnostic)

The Navigator controllers do not expose an internal "PV surplus charging active" state register — the whole PV block (74–88) consists of GLT measurement inputs written by an external energy manager. The integration therefore provides the derived diagnostic binary sensor PV-Überschussbetrieb (calculated_pv_surplus_operation, issue #353). It is on when both halves of the state are true:

1. Surplus is currently signalled to the controller: pv_surplus (register
   74. ≥ 0.05 kW or the SG-Ready signal smart_grid_status (register 90) reports Supergreen.
2. The heat pump is actually drawing electrical power: power_consumption_hp (register 4122) ≥ 0.05 kW, falling back to hp_operating_mode (register 1090) ≠ Off on installations without the Nav 10 power measurement.

The entity is only created when at least one source per half exists on the detected installation; thresholds and the currently active sources are exposed as attributes. Note for installations where the surplus is measured behind the heat pump feeder: pv_surplus collapses toward zero while the heat pump absorbs the surplus it is charged with — there the SG-Ready signal (or pv_production) remains the reliable indicator, and the SG-Ready source keeps the diagnostic meaningful.

Solar Thermal

These entities only exist while the solar thermal system option is enabled (default). Plants without collectors can switch the option off in the integration settings: the solar registers leave the poll and the empty Solaranlage device group disappears after a reload. Re-enabling it restores the entities with their previous IDs.

The integration also notices on its own: when every solar register reports "not configured" for a full day, a repair suggestion offers to switch the module off (or keep it, which dismisses that round of the suggestion).

ISC (Intelligent Surface Cooling)

Booster A/B (2nd heat generator)

Cascade (multi-heat pump)

Heating Circuit Sensors (per circuit A–G)

Calculated Sensors

These sensors are derived from register values of the same snapshot. Nothing is estimated: every operand is a decoded register value, and the sensor reports no value rather than a guess when its sources are not meaningful.

Flow deviation per heating circuit compares the measured flow temperature of a circuit (hc_{x}_flow_temp) with the flow setpoint the controller currently requests for that circuit (hc_{x}_setpoint_flow_temp):

• Positive — the circuit runs above the requested setpoint (overshoot, typically a heating curve set too high or a mixer that opens too far).
• Around zero — the circuit follows its heating curve.
• Negative — the circuit does not reach its setpoint (undersized heat source, high load, defrost, or a limiting setting).

The sensor becomes unavailable while the circuit is idle (the controller reports 0.0) and on circuits that are not configured (-1.0). That is intentional: a deviation calculated from a placeholder value would be meaningless. The entity itself is created as soon as both registers exist, so a Home Assistant restart during standby does not make it disappear.

This deliberately compares values within one heating circuit. A deviation at heat-pump level needs an unambiguous register for the flow setpoint the heat pump itself requests and remains an open roadmap item.

Optional Web Supplement Sensors

When Web supplement data is enabled and a local Navigator web PIN is configured, the integration adds read-only diagnostic sensors from the local web API. These sensors are additive; Modbus entities remain the primary data source.

Typical web-only sensors include:

Demand reason from the web interface (Navigator 10 only)

The Navigator controllers expose no internal PV-mode state register over Modbus, but the Navigator 10 web interface renders the display's "Anforderungsgrund" — including PV — from a bitmask in the WebSocket home/detail frame. With the web supplement active on a Navigator 10, the integration evaluates that frame every web poll and exposes:

• Anforderungsgrund (Web) (web_demand_reason): the human-readable demand reason, worded like the controller's own display — for example PV, Heizkreis A, Zeitprogramm, Mehrere Anforderungen, Keine Anforderung or Aus — with the raw operationMode/info values of every contributing widget as attributes.
• PV-Anforderungsgrund (Web) (web_demand_reason_pv): binary sensor that is on while the controller itself reports PV as its demand reason (bit 32), in the heating as well as the domestic-hot-water reason table.

This is the device-reported counterpart of the derived calculated_pv_surplus_operation diagnostic: the web entity reflects what the controller decided, the Modbus entity works without a web PIN. On Navigator 2.0 (different, PHP-based web interface) only the derived Modbus entity is available.

With the device hierarchy enabled, all PV entities — the PV registers (pv_surplus, pv_production, pv_target_value), smart_grid_status, the derived diagnostic and the two web entities — share the dedicated Photovoltaik subdevice instead of the main device. | Info system notifications (Web) | Summary of active Navigator 10 infosystem notifications | | Hot gas temperature (Web) | Web-only diagnostic temperature when available | | Evaporator pressure (Web) | Web-only refrigerant pressure when available | | Board temperature (Web) | Controller board temperature when available | | Current/projected heating / cooling / hot water power (Web) | The controller's current or projected thermal power for that mode |

"Momentane/prognostizierte Leistung" is not a live measurement

The Navigator labels these three values mom./prog. Leistung Heizen, mom./prog. Leistung Kühlen and mom./prog. Leistung Vorrang — momentane bzw. prognostizierte power. They report what the controller currently expects to deliver for that mode, so a non-zero value while heating or cooling is switched off is normal and not a fault. A value that changes while the compressor is idle is the controller re-planning, not the heat pump running.

For actual electrical draw, use Wärmepumpe Aufnahmeleistung / current_electrical_power instead.

If a web value duplicates an existing Modbus entity, the web entity is skipped. This prevents duplicate dashboard values and keeps Modbus as the authoritative source for register-backed data.

Only values returned by the current local web snapshot are available. Optional Navigator 10 infosystem notifications are read independently; if that optional request fails, the other valid web values remain available. See Local Navigator Web Interface for protocol and web-only-mode details.

Internal Message Sensor

The internal_message diagnostic sensor exposes the active IDM internal message as readable text, for example a code plus message description. It also provides the structured attributes message_code and message_text so automations can react either to the numeric code or to the human-readable description.

Binary Sensors

Navigator 1.0/1.7 — demand coils (c3001–c3003)

The 1.x family reports its live demand status through the official coil block (ma_de_812049 Rev.1), read with Modbus function code 01. These entities exist only on a detected Navigator 1.0/1.7:

The acknowledge coil c3000 has no sensor: it backs the Acknowledge errors button (see Services), which sends a single-coil write (function code 05) on the 1.x family and a holding-register write on the shared Navigator 2.0/10 family.

Numbers (Writable)

DHW

Heating Circuit (per circuit)

Entries marked expert shape the heating curve of the whole installation and write to EEPROM registers. They are created disabled on new installations — enable them under Settings -> Devices & Services -> IDM Heatpump -> Entities. Existing installations keep whatever state the entity already had. hc_{x}_setpoint_flow_constant and hc_{x}_setpoint_flow_cooling are expert entities for the same reason.

hc_{x}_ext_room_temp can be controlled manually like any other number entity or filled automatically by optional room temperature forwarding. When forwarding is enabled, selected Home Assistant temperature sensors are written to these external room temperature registers on state changes and periodically with a 300 second default interval.

GLT / External Control

Power Limits

These registers are model-dependent and disabled by default. Do not use them for legal or contractual load control until the behavior is verified for your exact hardware and firmware.

Selects

Switches

Climate

Climate entities combine a mode selector and a temperature target into the standard Home Assistant thermostat card. Two types are created:

Heating Circuit Climate (climate.hc_x)

One per configured heating circuit (A–G). Controls the circuit operating mode and its normal (day) room setpoint temperature.

Zone Room Climate (climate.zm{z}_room{r})

One per configured room in each zone module. Controls the room operating mode and its temperature setpoint.

Writes go through the coordinator's centralized write path with optimistic updates and translated error messages.

Water Heater

A single water heater entity (water_heater.idm_heatpump) provides DHW target temperature control with current temperature readback. Created when the target register (dhw_setpoint) and a DHW tank temperature register exist — the shared family reports dhw_temp_top, the Navigator 1.0/1.7 map offers dhw_temp (tank temperature, address 1012) instead.

Uses the same coordinator write path as climate entities.

Button

A single button (button.idm_heatpump_acknowledge_errors) acknowledges active errors on the heat pump by writing 1 to the error_acknowledge write-only register. Always available so automations can trigger on alarm state changes.

Zone Modules

For each enabled zone module (up to 10), room-level entities are created:

Plus per-zone: zm{z}_mode_heat_cool, zm{z}_dehumidification