🔥 Pellet stove 'Duepi-evo'

[aceindy]

Found someone on Jeedom who partially reverse engineered the serial line.
Now I reverse engineered it some more and adapted it for HA.

Since it relies on a serial2lan solution, I use ESP-Link.
There is also a ESPhome solution available (which I don’t find that stable), as well as an ESPEasy solution. Both are confirmed working, but for now I’ll stick to ESP-Link.
The easiest way to install ESP-Link is to use this page from my GitHub site ESP-Link You should use a supported browser and an usb2serial port must be available on your machine.
Note that I have re-compiled the firmware to host on ports 23 and 2000, which enables the use of the newer myDPRemote app too (as it has port 2000 hardcoded; on the older app it was configurable).

The HA Integration can be found on HACS
and is configured like this example:

# Example configuration.yaml entry
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:

• name (optional): The name of your climate entity. Defaults to “Duepi Evo”.
• host (required): The IP address used for the serial@tcp device.
• port (optional): The port being used. Defaults to 2000. (when using my ESPLink version, you can also use the default telnet port 23)
• scan_interval (required): The scan interval being used in seconds.
• min/max_temperature (optional): The available setpoint range within HA. Default is 16-30 degs celsius.
• auto_reset (optional): Auto reset the stove when “Ignition failed” or “Out of pellets” defaults to False.
• unique_id (optional): A unique name for the device. Defaults to “duepi_unique”. Change when using multiple stoves
• temp_nofeedback (optional): The default setpoint temperature for stoves that do not store the current setpoint. Defauls to 16.
• init_command (optional): Some stoves require a additional init_command before it accepts a command. Use this when you receive time-outs on new commands (see log).

PS: The advice is to set the scan_interval at least at 10s, you don’t want to send a new request before the unit finished replying to the previous request

and my LoveLace card yaml:

      - type: vertical-stack
        cards:
          - type: thermostat
            entity: climate.pellet_stove
            features:
              - type: climate-hvac-modes
                hvac_modes:
                  - heat
                  - 'off'
          - type: history-graph
            entities:
              - entity: climate.pellet_stove
            hours_to_show: 4
      - type: entities
        entities:
          - entity: climate.pellet_stove
            type: attribute
            name: Burner Status
            attribute: burner_status
          - entity: climate.pellet_stove
            type: attribute
            name: Error code
            attribute: error_code
          - entity: climate.pellet_stove
            type: attribute
            name: Exhaust fan speed
            attribute: exh_fan_speed
          - entity: climate.pellet_stove
            type: attribute
            name: Flu gas temperature
            attribute: flu_gas_temp
          - entity: climate.pellet_stove
            type: attribute
            name: Pellet speed
            attribute: pellet_speed
          - entity: climate.pellet_stove
            type: attribute
            name: Power level
            attribute: power_level

Confirmed working on:

• Amesti 7100/8100 plus2
• ALP srl Guisy
• AMG
• Artel
• Casatelli Leonardo 8/9
• Centrometal
• Duroflame Carré
• Duroflame Pelle
• Duroflame Rembrand
• FireShop Dinamica 6
• Foco
• Interstove
• Italia mod 8 el
• Julia Next
• Kalor
• Qlima Viola 85 S-Line
• Wamsler Westminster Quatro 6

All info and more is available on GitHub

How to physically connect:

If you like to help out, join us on Telegram

Big thanks go to Pascal Bornat (who initially started reverse engineering for Jeedom).

PS: it seems @mvroosmalen1970 managed to convert this into an ESPHome solution

Pellet stove 'Duepi-evo'

I would suggest to use the new ESPHome solution created: let me know if that’s works for you Mark

[fif10]

Hi
I am trying to use the great work you have done on this, but still have some issue for the harware setup :

Hardware setup issue

Would be very happy if @aceindy or anyone could unblock me.

Thanks

[aceindy]

Hi @fif10,

Welcome at the community

I’ve tried to answer all questions on GitHub

[Marcel_de_Jong]

Hi, I have that module, how can I assist?

[aceindy]

Hi Marcel,

Too late (already bought the module and took the data i needed)
So it is now for sale

For the project, we make progress with it, only we all have a time issue, so it goes slow…

[Marcel_de_Jong]

OK, do you think it is possible to control the stove from ha using the Duepi Module instead of an ESP?
I once tried to capture the UDP connection to port 2000, but could not really understand what was going on

[aceindy]

Hello Marcel,

Since the duepi-wifi module is nothing more then a serial2wifi module (+ some extra software to support their cloud), yeah it should work…

• install the repository from here
• find out the ip number from your dhcp-server(router) and make a reservation for it (so it will always get the same ip)
• use port 2000 (the default port 23 is only used when using the esplink)

Keep in mind the code is still work in progress…but basic functionality is there.
Let me know if it works with the duepi evo!!

Btw, the module uses tcp, not udp…
we are still finding and reversing all found commands
If you’re interested you can join the devs group on telegram here

ps: the opposite also works;the dpremote app works fine with the esplink serial wifi

[Whatsek]

Really nice to see this project! I have an Artel Julia Pellet Stove with an official Wifi module.
I installed the repository, but it cant connect:

> 2021-03-12 13:29:29 ERROR (MainThread) [homeassistant.components.climate] duepi_evo: Error on device update!
> Traceback (most recent call last):
>   File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 360, in _async_add_entity
>     await entity.async_device_update(warning=False)
>   File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 465, in async_device_update
>     await task
>   File "/config/custom_components/duepi_evo/climate.py", line 174, in async_update
>     data = await self.get_data(self)
>   File "/config/custom_components/duepi_evo/climate.py", line 124, in get_data
>     sock.connect((self._host, self._port))
> ConnectionRefusedError: [Errno 111] Connection refused

My configuration.yml settings are:

climate:
  - platform: duepi_evo
    name: "Pellet Kachel"
    host: 192.168.8.89
    port: 2000
    scan_interval: 60

Would be nice to get it working! Anything I can do to help?

[aceindy]

This application is for pellet stoves using the Duepi Evo board.

https://www.duepigroup.com/en/prodotti-duepi/electronic-control-evo/

Are you using the DPRemote application or another ??
If so, on which port is it registered ??

Next step…
Can you ping 192.168.8.89 ?
If so,
Can you telnet 192.168.8.89 2000 (or the port used found in the app), while using the app?
(you only see the replies from the stove)

PS: Just an idea, it might be required to configure the app for local usage (not cloud); maybe these settings are saved within the stove preventing it to communicate on LAN ???

[Whatsek]

I Have this model: (And I am using dpremote with it)

https://www.klimakalor.it/shop/evoremote-m1/

The IP is correct, and I can ping it, but I cant reacht it with telnet on ports: 23/2000/3000
And I also cant setup dpremote with a local connection. I lookup up in the manual how to switch from remote to a local connection, but the documentation is none existent

[aceindy]

Tap the cogwheel in the upper right corner and select ‘local’

Quick-start-M1-REV-00002-ENG.pdf

[Whatsek]

I tried that, but it wont connect. Probably thats also the reason that a local putty cant connect.
But I will reset it tommorow, I assume that it then looses the cloud connection. And try to set it up but only local. (I tried that when first installed it, I prefer a local connection, but it wouldnt connect.

Thats why I am very pleased with this module! Thanks for your support!
(And otherwise I will order an ESP board)

[aceindy]

esp board is cheap; including converter board approx 5€

but wifi module should also work; i’ve one here which i used for testing. However, i never set it up for cloud usage, as i want to sell it again

[aceindy]

ps, i am using the esplink now on HA, but i can still use the duepi app (in local mode)

[Whatsek]

Ok, thanks for the feedback, will reset it, and try again if I can setup an local connection. Then try HA again!

[aceindy]

@Whatsek

Probably thats also the reason that a local putty cant connect

the wifi module won’t send anything by itself, but you can monitor, provided you use the app (or HA, or python scripts) to send commands.

[Whatsek]

Unfortunately no success. It seems that local access is disabled after connecting it to the duepi cloud. Even after a reset of the Wifi module (I think it only resets the wifi settings, and reconnects to the duepi-server after getting internet access) I can’t get an open telnet connection on whatever port I check, it is closed immediately. A port scanner could not find any open ports, I scanned 1-5000.

I will contact Duepi how to enable local access, and will order an ESP board. (Always wanted to play with these controller boards, so now I have an excuse )

I will keep you posted if I make any progress!

[aceindy]

@Whatsek

(I think it only resets the wifi settings, and reconnects to the duepi-server after getting internet access)

Hmmm… if it can’t connect to a wifi-router, it should set up it’s own hotspot, called DPRemote-XXXX

Try to connect you’re mobile there and use http://192.168.4.1
username/password = user/user

Then on the next screen there is on an option ’ factory reset’

Because there must be some way to disconnect from the cloud; what if I sold my stove ??

[Whatsek]

Its get more weird: I enabled the hotspot, did a factory reset. It rebooted but was still connected to my wifi and the cloud connection still worked. Surely I did something wrong, so I did it all again, and after another reset I saw that the box rebooted itself and came up with a still working wifi connection and a working cloud connection.

Then I started the old Internet Explorer just to test if it was a browser problem, but it came up fully working again.

I see that I have firmware 1.33 instead of your? 1.17 or maybe you took it from elsewhere.

[aceindy]

@Whatsek

I see that I have firmware 1.33 instead of your? 1.17 or maybe you took it from elsewhere

oh, that was a screenshot from the manual