Monitoring & Controlling Ecodan via CN105

Iguaan · 9 February 2026 15:59

Still same:

After few days I’ll try some other slower profile, just to get some data.

Iguaan · 9 February 2026 19:07

Bit offtopic but,

So I can compile/install directly from HA like this:

Just editing conf file by adding following lines with my mqtt broker info?

# Example configuration entry
mqtt:
  broker: x.x.x.x
  username: livingroom
  password: !secret mqtt_password
  discover_ip: True # enable device discovery
some_option:
  topic: domoticz/in  #that's domoticz listening folder

E: so managed to get one strange stop on logs. Room setpoint has been 22,5, room temperature was dropping but it cut off, at around 22.40.

device_logs_2026-02-09T21-52-52.txt (28.8 KB)

gekkekoe · 10 February 2026 08:34

compressor shuts down because with mixing tank the FTC uses this hard stop condition:

actual z1 feed temp (41c) - z1 feed temp setpoint (39.3) >= 1.5

There’s an option to to avoid this, its the predictive cycle prevention

But it seems demand is off after the stop, so probably setpoint reached?

I see you use domoticz, it will die when you feed it with the ecodan feed. You probably want to set it to a lower polling rate esphome-ecodan-hp/ecodan-esphome.yaml at main · gekkekoe/esphome-ecodan-hp · GitHub

As for compiling, I assume users compiling themself are capable, so please consult all docs and howtos.

Iguaan · 10 February 2026 09:41

I have it enabled from the beginning with :

And since the flow setpoint is managed by atom and room temperature isn’t reached, I should decrease detection time to about 2min and increase high delta maybe 2-3C? I know the main issue for increasing flow is the annoying compressor/outdoor temp. frequency policy.

By the logs I see, it detects high delta at 22:36:49 and 22:38:34 adds boost +1C.

Then 22:38:49 recovered from high delta, but 22:40:19 high delta again and 22:42:45 compressor stops because there wasn’t enough time to add boost.

[22:33:34][D][auto_adaptive:312]: Z1 HEATING (Delta T): calculated_flow: 37.80°C (boost: 0.0)
[22:33:34][D][auto_adaptive:092]: CMD: Set Z1 Heat Flow -> 37.8°C (36.8°C)
[22:33:35][W][ecodan.component:352]: Command timed out. Retrying (attempt 2/30)...[1]
[22:36:49][D][short_cycle:074]: Zone: 1: High Delta T detected (1.2°C). Starting timer.
[22:38:33][D][auto_adaptive:431]: [*] Starting auto-adaptive cycle, z2 independent: 1, has_cooling: 1, cold factor: 1.35, min delta T: 3.00, max delta T: 8.00
[22:38:34][D][auto_adaptive:218]: Processing Zone 1: climate source: 0, Room=22.0, Target=22.5, Actual Feedtemp: 39.5, Return temp: 33.0, Outside: -4.0, Bias: 0.0, heating: 1, cooling: 0
[22:38:34][D][auto_adaptive:238]: Effective delta T: 6.28, cold factor: 1.35, dynamic min delta T: 5.71, error factor: 0.25, smart boost: 1.00, linear profile: 1
[22:38:34][D][auto_adaptive:312]: Z1 HEATING (Delta T): calculated_flow: 39.30°C (boost: 0.0)
[22:38:34][D][auto_adaptive:092]: CMD: Set Z1 Heat Flow -> 39.3°C (37.8°C)
[22:38:49][D][short_cycle:098]: Zone: 1: High Delta T has disappeared. Resetting timer.
[22:40:19][D][short_cycle:074]: Zone: 1: High Delta T detected (1.2°C). Starting timer.
[22:42:45][I][short_cycle:244]: Compressor STOP detected
[22:42:45][D][short_cycle:158]: Compressor stop event: stand-alone-cycle prevention: 0, saved z1 flow setpoint: 44.0, saved z2 flow setpoint: nan

Thanks for the tip.

Managed to verify conf file on HAbuilder, I’ll try later to install it.

Robert.Wall · 10 February 2026 13:05

2 posts were merged into an existing topic: Controlling Ecodan Remote Thermostat via CNRF

Iguaan · 11 February 2026 14:02

Some insights, that UFH* profile seems to be best solution for me with 100L buffer on flow limited to 47C, sheet steel radiators and average insulation house. Some runs even got almost to 2h (avg ~1h), setpoint stable 22,5C.

Tried also silent mode lev1 but that still kept compressor topped at 48Hz, amb -7C. Good thing is that this can be set on the run, at least on FTC6. If there would be a way to this remotely, then this could be adapted to ambient temperature and it would get rid of those occasional startup spikes. During DHW times the limit can be scheduled to return normal.

gekkekoe · 13 February 2026 08:00

Preview of upcoming stand alone mode. To be used without HA. Should be able to do all basic actions without HA to support users without HA (or don’t want to use it)

Timbones · 13 February 2026 09:09

Is there also an emoncms mode?

gekkekoe · 13 February 2026 09:38

What does that need to do? I guess most folks will be using HA and export data to emoncms?

Timbones · 13 February 2026 10:08

It could bypass HA for those who don’t use it, and push directly to an EmonCMS instance using the api_key. It’s how I would want it, though I could write my own script that listens to mqtt.

gekkekoe · 13 February 2026 10:09

Ah yeah that should be pretty easy to do, don’t know if there’s demand for it. If there is, I can look into it

gekkekoe · 13 February 2026 21:23

it’s available in pre-release Release Major release (Asgard stand alone mode) · gekkekoe/esphome-ecodan-hp · GitHub

F1p · 13 February 2026 21:53

I have recently added to my project room influence to my widely adopted and successful onboard compensation curve,

Inspired by the likes of ‘Active’ mode in Vaillant’s curve, this bridges the gap to a form of Adaption and addressing challenges like users with temperatures fed in from Heatmiser or other 3rd party thermostats & temperature sensors but keeps that key ability to directly modify the flow temperature

Currently in pre-release, hopefully stable enough shortly for a broader release.

Have a good weekend!

github.com/F1p/Mitsubishi-CN105-Protocol-Decode

documentation/OnboardCompCurve.md

master

# Using the onboard Compensation Curve



### About
The software has the ability to store a custom compensation curve onboard - this overcomes some limitations with the Ecodan and allows advanced features to be input.

* The Ecodan Main Room Controller (MRC) has the ability to design a curve with a maximum of 3 points, there is no limit to the number of points which can be sent to the CN105 Ecodan Bridge device.
* There is also no ability to add an +/- offset to the current curve remotely, only by adjusting on the the controller screen. By moving the curve onto the CN105 Ecodan Bridge, an offset can be adjusted remotely.
* The Ecodan uses the Outside Air Temperature (OAT) sensor located on the back of the outdoor unit, this sensor can be influenced by the likes of direct sunlight. By moving the curve onto the CN105 Ecodan Bridge it's possible to use another temperature source to determine the flow temperature.
* The Ecodan cannot automatically adjust for other influencing factors, such as heat loss due to wind or solar gain. By moving the curve onto the CN105 Ecodan Bridge it's possible to automate the offset when conditions may influence the building.


The device can continue to calculate and input to the curve if the connection is broken.



### How to Design, Modify and Operate

The Ecodan is to be placed in Fixed Flow mode, as the value is calculated by the device it will then adjust the flow temperature setpoint automatically which recreates the method the Ecodan uses.

This file has been truncated. show original

ajdunlop · 18 February 2026 15:11

Hi @F1p I’ve installed v6.6.0 but cannot get the room influence to activate when I send the MQTT message in the documentation.

{
“zone1”: {
“active”: true,
“manual_offset”: 1,
“room_influence_active”: true,
“use_local_tsensor”: true
}
}

It will allow me to change the active and manual_offset but not the other two.

F1p · 18 February 2026 17:41

Apologies, found the scenario for failure to enter - issued a hotfix

ajdunlop · 19 February 2026 08:27

Working now thanks.

F1p · 19 February 2026 11:41

I have a firmware variation of my MQTT based project which can send directly to the emonSD MQTT broker, if you are interested in trying it and help refine

My parameters are already in emon friendly formats and you don’t miss out on the Outdoor unit sensor data when running in parallel with MELCloud
Inside it is automatically converted from emonSD to Emoncms instead of you having to write a custom MQTT listener

gekkekoe · 23 February 2026 15:01

tagged new release for esphome-ecodan-hp

General

Allow per zone (z1/z2) virtual thermostat Hysteresis and AA room temp source
Add Delta T sensor
AA: Fixed the predictive boost indicator incorrectly showing that a boost was applied

Asgard

Reduce refresh rate on 1-wire sensors
Fix energy counter rollover when rebooting
Dashboard: Allow zooming in graphs
Dashboard: store 24h graph history on Asgard instead of browser
Dashboard: Cycle prevention settings
Dashboard: Added remaining climates
Dashboard: Add missing thermostat mode (virtual thermostat)
Dashboard: UI tweaks for mobile/touch devices
Dashboard: Add selection to for virtual thermostat or room thermostat (setting is persisted in NVS)
Dashboard: Fixed history endpoint from rebooting by avoiding using esphome::web_server_idf::AsyncResponseStream::print*
Dashboard: Use snapshots to avoid concurrency issues (http endpoints)

gekkekoe · 4 March 2026 11:31

Some work in progress info on the solver Introducing Odin Solver · gekkekoe/esphome-ecodan-hp · Discussion #297 · GitHub

gekkekoe · 13 March 2026 13:38

Made a lot of progress, currently validating and tuning the optimizer

The optimizer turned out to be a generic endpoint, so it can optimize/solve heating plan for any heatpump brand. Need to see how this will work out