Entities¶

This page lists the entity types exposed by the Dimplex Hub integration.

Entity names use Home Assistant’s has_entity_name pattern: the device is the appliance (or hub), and each entity has a short name such as “Room temperature” or “EcoStart”.

Climate¶

One climate entity per appliance.

Name	Entity ID pattern	Description
(device name)	`climate.<appliance>`	Thermostat: current room temperature, target setpoint, HVAC heat/off, presets. HVAC off follows timer frost protection / off (app “off”); heat is user-timer / manual modes.

Presets¶

Preset	Behaviour
`comfort`	Clears boost/away and turns EcoStart off when active.
`boost`	Enables boost (default ~60 minutes, boost temperature when known).
`away`	Enables away mode at the appliance away temperature when known.
`eco`	Enables EcoStart.

Services¶

climate.set_temperature — writes the target via the cloud timer schedule.
climate.set_preset_mode — boost / away / eco / comfort.
climate.turn_on / climate.turn_off — heat restores user-timer mode; off sets frost protection and clears boost/away.

Climate (and most status entities) are unavailable when the cloud returns an empty appliance overview (common when heaters have not telemetered recently).

Sensors¶

Name	Unit	Device class	Description
Room temperature	°C	temperature	Current room temperature.
Target temperature	°C	temperature	Active setpoint.
Boost temperature	°C	temperature	Boost mode target.
Away temperature	°C	temperature	Away mode target.
Setback temperature	°C	temperature	Setback target.
Energy lifetime	kWh	energy	Sum of daily cloud points for register T1 only (off-peak / cheaper rate).
Energy today	kWh	energy	T1 (off-peak) kWh for the current local calendar day.
Energy T2 lifetime	kWh	energy	Register T2 only (peak / more expensive; disabled by default).
Energy T2 today	kWh	energy	T2 (peak) kWh for the current local calendar day (disabled by default).
Rated power	kW	power	Static nameplate power from product provisioning (disabled by default).
Estimated power	kW	power	Heuristic `rated_power` when comfort/boost looks active, else `0` (diagnostic, disabled by default; not a live meter).
Charge capacity	kWh	energy	Static storage capacity from provisioning (disabled by default).
Error code	—	—	Appliance error code (disabled by default).
Warning code	—	—	Appliance warning code (disabled by default).
Last telemetry	timestamp	timestamp	Last cloud telemetry time (disabled by default).

Energy attributes¶

Attribute	Description
`mode`	`lifetime` or `daily`.
`register`	`t1` or `t2` (always separate).
`window_start` / `window_end`	Bounds of points used in the total.
`telemetry_points`	Number of points included.

Energy data is daily kWh history from the cloud, not live watts. Sensors are unavailable (not 0) when there are no points.

T1 and T2 are never combined. They are separate dual-rate registers:

Register	Sensors	Tariff (observed)
T1	Energy today / Energy lifetime	Off-peak (cheaper)
T2	Energy T2 today / Energy T2 lifetime	Peak (more expensive)

Confirm against your tariff and the official app if unsure. Do not sum T1+T2 into one helper — add Energy today and Energy T2 today as separate series (or map each to the matching tariff) in the Energy Dashboard.

When energy history is empty for several successful polls (common in summer), the integration backs off the energy poll interval (default up to 3 hours) and restores the configured interval when points return or heating activity is detected.

Binary sensors¶

Name	Device class	Description
Comfort	—	Comfort status from overview.
Open window	window	Open-window detection status (enabled flag from cloud).
Setback	—	Setback mode active.
Connected	connectivity	Hub connection (one per hub).

Switches¶

Name	Description
EcoStart	Toggle EcoStart energy-saving mode.
Open window detection	Enable/disable open-window detection (control; pairs with the binary sensor).

Schedule (read-only)¶

Diagnostic Schedule sensor per appliance: native value is timer mode (manual, user_timer, frost_protection, off). Attributes include periods (day/start/end/temperature). Write path is deferred (library schedule helpers).

Zones¶

Zone devices appear in the device registry (via hub; appliances via zone when zone id is known). A disabled diagnostic zone sensor anchors each zone device.

Unique IDs¶

Unique IDs are derived from the config entry id and the cloud appliance (or hub) id, plus a stable suffix (_climate, _energy, _ecostart, …). They remain stable across renames in the UI.

Templates and automations¶

Alert if room is too cold¶

alias: Living room is too cold
trigger:
  - platform: numeric_state
    entity_id: sensor.living_room_room_temperature
    below: 18
action:
  - service: notify.notify
    data:
      message: "Living room is {{ states('sensor.living_room_room_temperature') }} °C"

Boost via climate preset¶

alias: Boost living room
trigger:
  - platform: state
    entity_id: input_boolean.boost_living_room
    to: "on"
action:
  - service: climate.set_preset_mode
    target:
      entity_id: climate.living_room
    data:
      preset_mode: boost

EcoStart when away¶

alias: Enable EcoStart when away
trigger:
  - platform: state
    entity_id: person.yourself
    to: "not_home"
action:
  - service: switch.turn_on
    target:
      entity_id: switch.living_room_ecostart

Entity IDs depend on your appliance names; adjust to match Settings → Devices & services → Entities.