Harman EasyTouch Resolver

A Home Assistant integration that works out what a Harman pellet stove is doing by watching how much power it draws.

The stove does not report its own state, but each stage of operation (lighting, burning at each heat level, cooling down, idle) has a distinctive power draw. This integration takes a power sensor (in watts), smooths it with a 20 second moving average, maps that average to a state using a profile, and then settles on a final state using per-state timing rules, so brief blips don't cause flapping.

It does not talk to the stove. It only reads an existing Home Assistant power sensor (for example from a smart plug or an energy monitor), so there is no cloud service, no account and nothing to poll.

Tested hardware

This integration was developed and tested on a Harman Allure 50 (120V) running EasyTouch firmware 24.04.15.

Other stoves may work, but have not been tested. We would love to hear from you with custom profiles for other stoves. It is possible that stoves that are not EasyTouch could work with the right timings, but this has not been confirmed.

Note: Because this integration infers state from power draw, failing or non-standard components (for example a worn igniter, a different fan or auger motor, or a replacement control board) can change the power levels and cause a profile to behave incorrectly.

Entities

Each stove you add creates one device with:

Entity	Description
State (sensor)	The resolved state: sensor_fault, idle, extinguish, post_ignite, fault_extinguish, cool_down, burn_1 to burn_6, ignite.
Moving average (sensor, diagnostic, disabled by default)	The 20 second average of the power sensor, in watts. This is the number the profile's thresholds are compared with.
Raw state (sensor, diagnostic, disabled by default)	What the power level says right now, before the per-state delays are applied. Compare it with State to see which delay held a change back, which makes tuning a profile much easier.
General state (sensor)	A simplified view: faulted, lighting, burning, cooldown, idle. Shown translated in your language.
Active (binary sensor)	On while the general state is lighting, burning or cooldown, so it stays on until the stove has finished cooling down.

Upgrading to 0.3.1

The State sensor no longer has raw_state and moving_average attributes. They are now two separate diagnostic sensors, Raw state and Moving average, and both are disabled by default (see the table above for how to enable them). If a template, automation or dashboard card reads state_attr('sensor.<stove>_state', 'moving_average') or 'raw_state', point it at the new sensor instead.

Upgrading to 0.3.0 (breaking change)

The General state sensor's values changed from Faulted, Lighting, Burning, Cooldown, Idle to the lowercase faulted, lighting, burning, cooldown, idle, so Home Assistant can translate them. Update anything that compares against the old values: automations, templates, scripts, dashboards and conditional cards. Look for the old capitalised words.

History from before the upgrade keeps the old values, so a history graph shows both. The State sensor is unchanged. The Active binary sensor now also stays on during cooldown (the extinguish and cool_down states), where it used to turn off as soon as the stove stopped burning.

Use cases

• Show on a dashboard whether the stove is lighting, burning, cooling down or idle, without any wiring to the stove.
• Get a notification when the stove faults, or has been burning for many hours.
• Turn on a fan or adjust the heating when the stove starts burning, and back again when it goes idle.
• Keep a history of when the stove ran and at which heat level.

Installation

Prerequisites

• A Home Assistant power sensor (device_class: power, in watts) that measures the stove's electrical draw. A smart plug with energy monitoring works well.

With HACS (recommended)

1. In HACS, open the three-dot menu and choose Custom repositories.
2. Add https://github.com/drsassafras/Harman-EASY-Touch-Resolver with the category Integration.
3. Find Harman EasyTouch Resolver in HACS, download it, and restart Home Assistant.

Manually

1. Copy custom_components/harman_easytouch_resolver into the custom_components folder of your Home Assistant configuration.
2. Restart Home Assistant.

Add the stove

Go to Settings → Devices & services → Add integration, search for Harman EasyTouch Resolver and fill in:

Field	Description
Stove name	A name for the stove, for example "Living room stove". It becomes the device name and must be unique.
Power monitoring for pellet stove (watts)	The power sensor described above. A sensor can only be used by one stove.
Profile	A built-in or saved profile, or Import / design a new profile… to open the JSON editor.

Changing settings

Select Configure on the integration. The first page has these fields:

Field	Description
Power monitoring for pellet stove (watts)	The power sensor. A sensor can only be used by one stove.
Stove profile	The profile used to work out the state.
Keep last state when the sensor drops out (seconds)	How long the entities keep showing the last state after the power sensor becomes unavailable, including while it starts up after a Home Assistant restart. 60 by default, 0 to 600. 0 shows the stove as unavailable immediately.
Edit profile JSON	Tick and select Submit to open the JSON editor, pre-filled with the selected profile.

To point a stove at a different power sensor you can also use Reconfigure from the integration's three-dot menu. It only asks for the sensor.

Built-in profiles can't be overwritten, so editing one saves a copy under the new name you give it. Editing one of your own profiles under the same name updates it, and every stove using it reloads.

Actions

This integration does not provide any actions.

Removing the integration

1. Go to Settings → Devices & services, open Harman EasyTouch Resolver.
2. Open the three-dot menu on the stove and choose Delete. Repeat for each stove.
3. If you installed with HACS, remove it there too, or delete custom_components/harman_easytouch_resolver and restart.

Saved custom profiles are kept in .storage/harman_easytouch_resolver.profiles. Delete that file after removing the last stove if you no longer want them.

Automation examples

Notify when the stove faults:

triggers:
  - trigger: state
    entity_id: sensor.living_room_stove_general_state
    to: "faulted"
actions:
  - action: notify.notify
    data:
      message: "The pellet stove has a fault."

Run a fan while the stove is active:

triggers:
  - trigger: state
    entity_id: binary_sensor.living_room_stove_active
    to: "on"
actions:
  - action: switch.turn_on
    target:
      entity_id: switch.living_room_fan

Entity ids follow your stove name, so replace living_room_stove with yours.

Finding the right power levels for your stove

Every stove is a little different. To tune a profile:

1. Enable the two diagnostic sensors, Moving average and Raw state. They are off by default: open the stove's device page, click the "entities not shown" link, open each one, then Settings (the cog) and turn on Enabled. Then watch Moving average (on the device page, or in Developer Tools → States).
2. Watch the value as the stove goes through a normal cycle: lighting, each burn level, cooldown and off.
3. Note the watts at each stage and use them to adjust the thresholds in a custom profile.
4. Adjust the timings if states change too slowly or flap.

Profiles

Profiles are JSON with a name, thresholds and optional timings.

Thresholds and timings both refer to the Moving average sensor, and all five timing keys are optional.

Thresholds

Each value is the lower limit of a state, in watts. A state applies when the Moving average is above that state's threshold and not above the next state's threshold up. Values must strictly decrease from ignite down to idle. At or below the idle value the state is sensor_fault.

Timings

A state change only becomes final after the new state has held for a set number of seconds. Each state's timings apply when moving into that state. The states have a fixed order: sensor_fault, idle, extinguish, post_ignite, fault_extinguish, cool_down, burn_1 to burn_6, ignite. All keys are optional.

Key	Seconds to wait when...	If missing
sequp	moving up one step into this state	0
seqdown	moving down one step into this state	0
nonseq	jumping more than one step (for example burn_1 to burn_3)	0
cascadeup	moving up one step after an unfinished change	uses sequp
cascadedown	moving down one step after an unfinished change	uses seqdown

A change is "unfinished" when the state changes again before the previous change became final. Example: the stove is at burn_1 and moves to burn_2, but before the wait ends it moves to burn_3. The wait for burn_3 then uses cascadeup instead of sequp. A new change always cancels the one still waiting.

A state that has no entry in timings at all waits 3 seconds for every kind of move.

Example

{
  "name": "My stove",
  "thresholds": {
    "ignite": 155, "burn_6": 140, "burn_5": 127, "burn_4": 115,
    "burn_3": 101, "burn_2": 86, "burn_1": 71, "cool_down": 60,
    "fault_extinguish": 32, "post_ignite": 19, "extinguish": 5, "idle": 1
  },
  "timings": {
    "burn_3": { "sequp": 75, "seqdown": 75, "cascadeup": 20, "cascadedown": 20, "nonseq": 10 },
    "idle": { "sequp": 0, "seqdown": 0, "nonseq": 0 }
  }
}

How it behaves

• The 20 second moving average is fixed because of the stove's 10 second power cycle.
• After a restart, or when the power sensor comes back from unavailable, the integration waits for a full 20 seconds of data before resolving a state. The previous resolved state is remembered, and the first reading that disagrees with it is applied after 30 seconds.
• When the power sensor becomes unavailable or not a number, all three entities keep showing the last state for the Keep last state when the sensor drops out time (60 seconds by default, 0 to 600 in the options). Only if the sensor is still bad after that do they show as unavailable. Set it to 0 for the old behaviour. A short outage therefore leaves no gap in the history.
• The same time covers a Home Assistant restart: the last state is restored and shown while the power sensor comes online. If your power sensor takes longer than that to start (for example a Zigbee or MQTT device), raise the value. Time while Home Assistant itself is not running cannot be recorded.
• If readings were missing for more than 20 seconds, the integration waits for a fresh 20 second window before changing the state.
• Updates are event driven: the integration reacts to the power sensor's state changes and never polls. Readings that repeat the same value count as samples too.
• If the power sensor stays unavailable longer than the keep-last-state time, one warning is logged and one message when it reports again. Nothing is logged while it is flapping inside the time.

Known limitations

• It works out the state from power draw only, so it cannot tell a fault apart from a different stove component drawing unusual power.
• A stove needs its own power sensor, and one sensor cannot serve two stoves.
• The 20 second averaging window is fixed because of the stove's 10 second power cycle.
• A state is only known after the first full 20 seconds of readings.
• The history has a gap while Home Assistant itself is not running. The keep-last-state time only covers the power sensor coming back late.
• Entity names and the states of both sensors are translated, but the underlying state values (for example burn_2 or burning) are fixed, so automations keep working in every language.

Diagnostics and repairs

• Diagnostics: on the integration page, open the three-dot menu of a stove and choose Download diagnostics. It includes the options, the profile and the current averaging state. Attach it when reporting an issue.
• Repairs: if a stove refers to a profile that no longer exists, a repair item appears under Settings → System → Repairs and the built-in Allure 50 profile is used meanwhile. Choose or import a profile in the integration's options to clear it.

Troubleshooting

Symptom	Likely cause
Entities are unavailable	The power sensor has been unavailable, unknown or not numeric for longer than the keep-last-state time.
State is unknown	Waiting for the first 20 seconds of readings.
State flaps between two levels	Thresholds sit too close to the stove's real power at that level. Check the Moving average sensor and move the threshold. Increase the timings for that state.
State is stuck on sensor_fault	Moving average is at or below the profile's idle value. Check the sensor's units are watts.
"Profile not found" in the log, or a repair item	A stove refers to a profile that no longer exists. It falls back to Allure 50 until you choose another in the options.

Translations

English, Canadian French, Irish and Welsh. The Irish and Welsh have not been reviewed by native speakers; corrections are welcome.

Translated: entity names, every state of both sensors, the setup, options and reconfigure forms (including the profile dropdown entry and every profile error message), and repair messages.

Not translated: log messages, diagnostics and this README, because Home Assistant does not translate those, and the keys of the profile JSON (name, thresholds, timings and the state names inside them), which are fixed.

Development

pip install -r requirements_test.txt
pytest

tests/test_profile.py, tests/test_engine.py and tests/test_translations.py need nothing but Python. The others use the Home Assistant test harness. See docs/quality_scale.md for how the integration lines up with Home Assistant's quality scale.

Contributing

Custom profiles for other stoves are very welcome. Please open an issue with your stove model, firmware version, and the profile JSON.