Duepi_EVO

hacs_badge ko-fi

Duepi-EVO

The Duepi EVO climate platform is a reverse engineered implementation of the app which is controlling Pellet stove heaters using a Duepi Evo Wifi module. With this module it is possible to control your pellet stove with HomeAssistant.

This is in no way associated with the company Duepi and comes with no guarantees or warranty. Use at your own risk.

image

Prerequisites

Hardware

This uses an ESP01 board with 5/3.3v adapter with ser2net software.

I recently found a config for ESPHome (which has my preference, but I switched back, as it wasn’t very stable. You will find a configureation example here https://github.com/aceindy/Duepi_EVO/blob/main/ESPHome/duepi-pelletstove.yaml

You must have the ESP01 Module installed and flash it with https://github.com/jeelabs/esp-link. Baudrate 115200, 8N1. Pin layout is mentioned in the pdf (pcb, J8)

Easiest way to install ESP-Link is to use this Online installer page on my GitHub site ESP-Link Note that I have re-compiled the firmware to host on ports 23 and 2000, which allows to use the newer myDPRemote app too (as it has port 2000 hardcoded).

As well as Espeasy (info from a Duroflame Rembrand user):

Optionally one can use the Wemos D1 flashed with ESPeasy. This device has a 5V input and integrated CH340 for easy flashing. The only tweak needed was to add 5ms timeout delay in the serial device settings of espeasy to get robust data from the pellet stove. In Esp_easy flashed device select the Device: Communication - Serial Server and fill in the appropiate fields (harware serial GPIO-3 and -1, port 1234 (or any) baud rate 115200, serial config 8N1,RX receive 5ms, 256 buffer).

Functionality

Configuration

  1. Go to Settings -> Devices & Services -> Add Integration.
  2. Search for Duepi EVO.
  3. Enter:
    • host
    • port
    • name
    • unique_id
  4. After creation, edit options to configure:
    • scan_interval
    • min_temp
    • max_temp
    • auto_reset
    • temp_nofeedback
    • init_command

Legacy YAML configuration (deprecated)

YAML is still supported temporarily and will be auto-imported into Config Entries when possible.

climate:
  - platform: duepi_evo
    name: <your heaters name here>
    host: 192.168.1.123
    port: 2000
    scan_interval: 60
    min_temp: 20
    max_temp: 30
    auto_reset: true
    unique_id: <unique_name>
    temp_nofeedback: 16
    init_command: false

Configuration variables:

Troubleshooting

Please set your logging for the custom_component to debug:

logger:
  default: warn
  logs:
    custom_components.duepi_evo: debug

Development (devcontainer/local helper scripts)

The helper scripts auto-detect the repository root from their own path. For local runs, use Python 3.13.2 or newer. If needed, you can override the workspace location explicitly:

WORKSPACE=/absolute/path/to/Duepi_EVO bash scripts/setup.sh
WORKSPACE=/absolute/path/to/Duepi_EVO bash scripts/ha.sh start
WORKSPACE=/absolute/path/to/Duepi_EVO bash scripts/smoke_migration.sh
WORKSPACE=/absolute/path/to/Duepi_EVO bash scripts/smoke_migration.sh --skip-migration

Example Lovelace entities card (new dedicated sensors):

type: entities
entities:
  - entity: climate.pellet_stove
  - entity: sensor.pellet_stove_burner_status
  - entity: sensor.pellet_stove_error_code
  - entity: sensor.pellet_stove_exh_fan_speed
  - entity: sensor.pellet_stove_flu_gas_temp
  - entity: sensor.pellet_stove_pellet_speed
  - entity: sensor.pellet_stove_power_level
  - entity: sensor.pellet_stove_pcb_temperature
  - entity: sensor.pellet_stove_total_burn_time
  - entity: sensor.pellet_stove_burn_time_since_reset
  - entity: binary_sensor.pellet_stove_pressure_switch

Legacy climate attributes

Legacy climate.* attributes are still exposed for compatibility and are planned to be removed after two releases.

Confirmed working on:

Big thanks go to Pascal Bornat (who initially started reverse engineering for Jeedom) and Oxan van Leeuwen (for the Stream server for ESPHomeproject)

Buy Me A Coffee! :coffee:

Star History

Star History Chart