ESPHome Mitsubishi Ecodan and remote thermostat integrations

gekkekoe · October 10, 2025, 11:11am

sorry no support in proxy for PAC-WF010-E
it does a different handshake, but I don’t have a unit to test and to make it work unfortunately

gekkekoe · October 11, 2025, 6:17pm

Can you test one thing for me, attach proxy with melcloud.
And http://esp_ip, turn on the “uart debug” switch

Can you copy paste a couple of message sequences for me? It might contain enough info to make it work

gekkekoe · October 12, 2025, 6:15pm

New release with some additions for AA

AA: Allow overshoot compensation. Use this setting to compensate for overshooting in your thermostat
AA: Predictive Short-Cycle prevention. Heating offset will be raised by 0.5c when delta between requested and actual feed temp is above 1.0c for the min duration of 4 minutes. This mode is always enabled in Auto Adaptive. In fixed flow heating it can be enabled manually via the switch. the High Delta detection duration is editable [1m-5m, default 4m]
AA: Only enforce saturation prevention when in active heating/cooling
AA: Implement dual heating slope for heating. When it gets cold (< 5c) an additional factor is multiplied with the slope. Setting can now be set in steps of 0.05c
AA: Allow adjustable min flow temp for heating. Override if you are hitting min output capacity during mild weather. [24.0c - 40.0c, default: 25c]
Add floor dry up, cool compensation curve mode (only works for ftc7+)
AA: Widen dead zone for UFH profiles during the night

F1p · October 12, 2025, 7:42pm

@rokic
Would you be willing to test my .merged.bin version - to see if proxy works for you?

gekkekoe · October 12, 2025, 7:45pm

yeah please try @F1p bin. Just to rule out.
I use 9600 baud per default, and that might mess things up.

rokic · October 13, 2025, 5:29am

@gekkekoe, I will try today with UART debug and post what I will get out.

@F1p, I will try. Hopefully already this week

gekkekoe · October 13, 2025, 6:24am

Also try this, with uart. It should support unsupported messages at 9600, or at least should print more with uart logging so i can hopefully fixed it

rokic · October 13, 2025, 4:23pm

OK, I checked a few things and I think that there is an compatibility issue with PAC-WF010-E.

Proxy connection - with Atom s3 and proxy adapter and Melcloud adapter → Melcloud adapter LED2 is constantly blinking, which means “Server communication or access point communication failed, and ecodan unit communication failed”.
Only Melcloud adapter connected to port CN105 → everything is OK. Communication works and also Melcloud app is working fine.
Proxy setup without S3 atom → only proxy adapter between Melcloud adapter and Ecodan CN105. The same error as on 1st point.
Proxy setup with adapter and S3 atom (without Melcloud adapter on EXT port) → esp32s3-proxy2-z1-en-2025-09-03.1 (ESPHome 2025.7.5) and with esp32s3-proxy2-z1-en-2025-10-12.5 (ESPHome 2025.7.5) all data visible, but I can not start the Ecodan (Off mode by Melcloud) as it is in “slave mode”.

So, I can conclude that with PAC-WF010-E and adapter for proxy setup are some compatibility issues. I don’t think it’s worth to continue investigating.

But I still have some issue with “nomal mode” (non proxy setup) temperature settings. If I have “Selected operating mode” in “Heat target temperature” I can normally adjust “Zone 1 Room Temp” and communication works. If I select “Compensation curve” neither Zone 1 Room Temp or Zone 1 Flow Temp are reacting to changes. If I modify the temperature value, it stays there for approx. 1 minute and then returns back to its original setting. It’s ard to show tis via “Uart logging” because there are to many rows of code. If there is a possibility to export the history of 2 minutes it would be great.

Thanks for help.

Below two logs if something help you out. This is with “non-proxy” setup.

Blockquote
18:12:55 [D] [uart_debug:114]
<<< FC 62 02 7A 10 A3 00 07 00 00 00 00 00 00 00 00 00 00 00 00 00 68
18:12:56 [D] [sensor:104]
‘Heap Free’: Sending state 185232.00000 B with 0 decimals of accuracy
18:12:56 [D] [sensor:104]
‘Loop Time’: Sending state 29.00000 ms with 0 decimals of accuracy
18:12:56 [D] [uart_debug:114]

FC 42 02 7A 10 A3 00 07 00 00 00 00 00 00 00 00 00 00 00 00 00 88 FC 42 02 7A 10 A3 00 07 00 00 00 00 00 00 00 00 00 00 00 00 00 88
18:12:56 [D] [sensor:104]
‘Outside Unit Two Phase Pipe Temp’: Sending state 7.00000 °C with 1 decimals of accuracy
18:12:56 [D] [uart_debug:114]
<<< FC 62 02 7A 10 A3 00 07 02 07 00 00 00 00 00 00 00 00 00 00 00 5F
18:12:56 [D] [uart_debug:114]
FC 42 02 7A 10 0F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 23
18:12:57 [D] [uart_debug:114]
FC 42 02 7A 10 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 22
18:12:57 [D] [uart_debug:114]
<<< FC 62 02 7A 10 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02
18:12:57 [D] [uart_debug:114]
FC 42 02 7A 10 13 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1F
18:12:57 [D] [sensor:104]
‘Operating Runtime’: Sending state 21306.00000 h with 0 decimals of accuracy
18:12:57 [D] [uart_debug:114]
<<< FC 62 02 7A 10 13 01 00 06 00 D5 00 00 00 00 00 00 00 00 00 00 23
18:12:57 [D] [text_sensor:069]
‘Operation Mode’: Sending state ‘Space Heating’
18:12:58 [D] [uart_debug:114]
FC 42 02 7A 10 15 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1D
18:12:58 [I] [ecodan.component:040]
Could not publish state of sensor ‘status_three_way_valve_2’ with value: ‘1’
18:12:58 [I] [ecodan.component:040]
Could not publish state of sensor ‘status_water_pump_3’ with value: ‘0’
18:12:58 [I] [ecodan.component:018]
Could not publish state of sensor ‘status_mixing_valve’ with value: ‘4.000000’
18:12:58 [I] [ecodan.component:018]
Could not publish state of sensor ‘mixing_valve_step’ with value: ‘0.000000’
18:12:58 [D] [uart_debug:114]
<<< FC 62 02 7A 10 15 01 00 44 01 00 00 01 00 00 00 04 00 00 00 00 B2
18:12:58 [D] [uart_debug:114]
FC 42 02 7A 10 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1E
18:12:58 [D] [sensor:104]
‘Flow Rate’: Sending state 0.00000 L/min with 0 decimals of accuracy
18:12:58 [D] [sensor:104]
‘Estimated Output Power’: Sending state 0.00000 kW with 3 decimals of accuracy
18:12:58 [D] [sensor:104]
‘Estimated Total Daily Energy Produced’: Sending state 0.00000 kWh with 3 decimals of accuracy
18:12:58 [D] [uart_debug:114]
<<< FC 62 02 7A 10 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE
18:12:59 [D] [uart_debug:114]
FC 42 02 7A 10 26 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0C
18:12:59 [D] [sensor:104]
‘H/C status’: Sending state 2.00000 with 0 decimals of accuracy
18:12:59 [I] [ecodan.component:018]
Could not publish state of sensor ‘status_heating_cooling_z2’ with value: ‘1.000000’
18:12:59 [D] [sensor:104]
‘DHW Setpoint Value’: Sending state 50.00000 °C with 1 decimals of accuracy
18:12:59 [D] [uart_debug:114]
<<< FC 62 02 7A 10 26 00 00 01 02 00 02 01 13 88 0E 10 07 D0 00 00 56
18:12:59 [D] [uart_debug:114]
FC 42 02 7A 10 28 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0A
18:12:59 [D] [text_sensor:069]
‘Dip Switch 2 (8-1)’: Sending state ‘00001100’
18:12:59 [D] [climate:396]
‘Zone 1 Flow Temp’ - Sending state:
18:12:59 [D] [climate:399]
Mode: HEAT
18:12:59 [D] [climate:401]
Action: HEATING
18:12:59 [D] [climate:419]
Current Temperature: 36.00°C
18:12:59 [D] [climate:425]
Target Temperature: 36.00°C
18:12:59 [I] [ecodan.component:040]
Could not publish state of sensor ‘status_prohibit_heating_z2’ with value: ‘0’
18:12:59 [I] [ecodan.component:040]
Could not publish state of sensor ‘status_prohibit_cool_z2’ with value: ‘0’
18:12:59 [I] [ecodan.component:040]
Could not publish state of sensor ‘status_server_control_prohibit_heating_z2’ with value: ‘0’
18:12:59 [I] [ecodan.component:040]
Could not publish state of sensor ‘status_server_control_prohibit_cool_z2’ with value: ‘0’
18:12:59 [D] [uart_debug:114]
<<< FC 62 02 7A 10 28 00 00 00 00 01 00 00 00 00 01 00 00 00 00 00 E8
18:12:59 [D] [sensor:104]
‘WiFi Signal dB’: Sending state -64.00000 dBm with 0 decimals of accuracy
18:12:59 [D] [sensor:104]
‘WiFi Signal %’: Sending state 72.00000 % with 0 decimals of accuracy
18:13:00 [D] [uart_debug:114]
FC 42 02 7A 10 A1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 91
18:13:00 [D] [uart_debug:114]
<<< FC 62 02 7A 10 A1 19 0A
18:13:00 [D] [uart_debug:114]
<<< 0C 00 0B 0A
18:13:00 [D] [sensor:104]
‘Heating Consumed’: Sending state 11.10000 kWh with 2 decimals of accuracy
18:13:00 [D] [sensor:104]
‘Cool Consumed’: Sending state 0.00000 kWh with 2 decimals of accuracy
18:13:00 [D] [sensor:104]
‘DHW Consumed’: Sending state 0.00000 kWh with 2 decimals of accuracy

Blockquote
Time Level Tag Message
18:05:53 [D] [climate:396]
‘Zone 1 Room Temp’ - Sending state:
18:05:53 [D] [climate:399]
Mode: HEAT
18:05:53 [D] [climate:401]
Action: HEATING
18:05:53 [D] [climate:419]
Current Temperature: 17.00°C
18:05:53 [D] [climate:425]
Target Temperature: 28.00°C
18:05:53 [I] [ecodan.component:040]
Could not publish state of sensor ‘status_three_way_valve_2’ with value: ‘1’
18:05:53 [I] [ecodan.component:040]
Could not publish state of sensor ‘status_water_pump_3’ with value: ‘0’
18:05:53 [I] [ecodan.component:018]
Could not publish state of sensor ‘status_mixing_valve’ with value: ‘4.000000’
18:05:53 [I] [ecodan.component:018]
Could not publish state of sensor ‘mixing_valve_step’ with value: ‘0.000000’
18:05:53 [D] [uart_debug:114]
<<< FC 62 02 7A 10 15 01 00 45 01 00 00 01 00 00 00 04 00 00 00 00 B1
18:05:53 [D] [climate:396]
‘Zone 1 Room Temp’ - Sending state:
18:05:54 [D] [climate:399]
Mode: HEAT
18:05:54 [D] [climate:401]
Action: HEATING
18:05:54 [D] [climate:419]
Current Temperature: 17.00°C
18:05:54 [D] [climate:425]
Target Temperature: 28.00°C
18:05:54 [D] [uart_debug:114]

FC 42 02 7A 10 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1E
18:05:54 [D] [climate:396]
‘Zone 1 Room Temp’ - Sending state:
18:05:54 [D] [climate:399]
Mode: HEAT
18:05:54 [D] [climate:401]
Action: HEATING
18:05:54 [D] [climate:419]
Current Temperature: 17.00°C
18:05:54 [D] [climate:425]
Target Temperature: 28.00°C
18:05:54 [D] [sensor:104]
‘Flow Rate’: Sending state 0.00000 L/min with 0 decimals of accuracy
18:05:54 [D] [sensor:104]
‘Estimated Output Power’: Sending state 0.00000 kW with 3 decimals of accuracy
18:05:54 [D] [sensor:104]
‘Estimated Total Daily Energy Produced’: Sending state 0.00000 kWh with 3 decimals of accuracy
18:05:54 [D] [uart_debug:114]
<<< FC 62 02 7A 10 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE
18:05:54 [D] [climate:396]
‘Zone 1 Room Temp’ - Sending state:
18:05:54 [D] [climate:399]
Mode: HEAT
18:05:54 [D] [climate:401]
Action: HEATING
18:05:54 [D] [climate:419]
Current Temperature: 17.00°C
18:05:54 [D] [climate:425]
Target Temperature: 28.00°C
18:05:54 [D] [uart_debug:114]
FC 42 02 7A 10 26 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0C
18:05:54 [D] [text_sensor:069]
‘Operation Mode’: Sending state ‘Space Heating’
18:05:54 [D] [climate:396]
‘Zone 1 Room Temp’ - Sending state:
18:05:54 [D] [climate:399]
Mode: HEAT
18:05:54 [D] [climate:401]
Action: HEATING
18:05:54 [D] [climate:419]
Current Temperature: 17.00°C
18:05:54 [D] [climate:425]
Target Temperature: 28.00°C
18:05:54 [D] [sensor:104]
‘WiFi Signal dB’: Sending state -64.00000 dBm with 0 decimals of accuracy
18:05:54 [D] [sensor:104]
‘WiFi Signal %’: Sending state 72.00000 % with 0 decimals of accuracy
18:05:54 [D] [sensor:104]
‘H/C status’: Sending state 2.00000 with 0 decimals of accuracy
18:05:54 [I] [ecodan.component:018]
Could not publish state of sensor ‘status_heating_cooling_z2’ with value: ‘1.000000’
18:05:54 [D] [sensor:104]
‘DHW Setpoint Value’: Sending state 50.00000 °C with 1 decimals of accuracy
18:05:54 [D] [uart_debug:114]
<<< FC 62 02 7A 10 26 00 00 01 02 00 02 01 13 88 0E 10 07 D0 00 00 56
18:05:54 [D] [climate:396]
‘Zone 1 Room Temp’ - Sending state:
18:05:55 [D] [climate:399]
Mode: HEAT
18:05:55 [D] [climate:401]
Action: HEATING
18:05:55 [D] [climate:419]
Current Temperature: 17.00°C
18:05:55 [D] [climate:425]
Target Temperature: 28.00°C
18:05:55 [D] [uart_debug:114]
FC 42 02 7A 10 28 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0A
18:05:55 [D] [switch:016]
‘UART Logging’ Turning OFF.

gekkekoe · October 13, 2025, 5:31pm

please try this file: https://github.com/gekkekoe/esphome-ecodan-hp/releases/download/2025-10-17.1/esp32s3-proxy2-z1-en-2025-10-17.1.ota.bin
Should match your config. flash it via http://esp_ip, at the bottom of the page

I hope it will fix your proxy issue. Please verify for us, since there are not a lot of users with PAC-WF010-E to test.

non proxy setup works fine no need to test that

gekkekoe · October 17, 2025, 12:53pm

@rokic latest release should support your wifi adapter

rokic · October 19, 2025, 5:02pm

Hi,
just tested, but no success.
As I wrote before. As soon as I connect Melcloud adapter to “proxy adapter” it has no communication anymore. LED2 is constantly blinking, which means “Server communication or access point communication failed, and ecodan unit communication failed”.
No matter if there is ESP installed or not.
Also Melcloud app somehow sees that there is a communication ("Last communication… time/date from few second before), but anything I try to do in Melcloud app does not respond.
Commands from HASS works, but I don’t see any temperature. Basically everything under Sensors and Diagnostic is “unkown” or “0”.

I enabled UART if something helps you:

18:56:31	[D]	[uart_debug:114]	>>> 01_00_40_00_00_06_02_7A_00_00_B5
18:56:31	[D]	[uart_debug:114]	>>> 02 FF FF 00 00 00 00 02
18:56:31	[D]	[uart_debug:114]	<<< 02_FF_FF_00_00_00_00_02
18:56:31	[D]	[uart_debug:114]	<<< 02 FF FF 80 00 00 0A
18:56:31	[D]	[uart_debug:114]	>>> 02_FF_FF_80_00_00_0A
18:56:31	[D]	[sensor:104]	‘WiFi Signal dB’: Sending state -62.00000 dBm with 0 decimals of accuracy
18:56:31	[D]	[sensor:104]	‘WiFi Signal %’: Sending state 76.00000 % with 0 decimals of accuracy
18:56:31	[D]	[uart_debug:114]	<<< 01 00 40 00 00 06 02 7A 00 00 B5
18:56:31	[D]	[uart_debug:114]	>>> 01_00_40_00_00_06_02_7A_00_00_B5
18:56:31	[D]	[uart_debug:114]	>>> 02 FF FF 00 00 00 00 02
18:56:31	[D]	[uart_debug:114]	<<< 02_FF_FF_00_00_00_00_02
18:56:31	[D]	[text_sensor:069]	‘Operation Mode’: Sending state ‘Unknown’
18:56:31	[D]	[sensor:104]	‘ESP Uptime’: Sending state 571.73798 s with 0 decimals of accuracy
18:56:31	[D]	[uart_debug:114]	<<< 02 FF FF 80 00 00 0A
18:56:31	[D]	[uart_debug:114]	>>> 02_FF_FF_80_00_00_0A
18:56:32	[D]	[uart_debug:114]	<<< 01 00 40 00 00 06 02 7A 00 00 B5
18:56:32	[D]	[uart_debug:114]	>>> 01_00_40_00_00_06_02_7A_00_00_B5
18:56:32	[D]	[uart_debug:114]	>>> 6E 02
18:56:32	[D]	[uart_debug:114]	<<< 6E_02
18:56:33	[D]	[uart_debug:114]	>>> 6E 02
18:56:33	[D]	[uart_debug:114]	<<< 6E_02
18:56:33	[D]	[sensor:104]	‘Estimated COP’: Sending state 0.00000 with 2 decimals of accuracy
18:56:33	[D]	[uart_debug:114]	>>> 6E 02
18:56:33	[D]	[uart_debug:114]	<<< 6E_02
18:56:34	[D]	[uart_debug:114]	>>> 02 FF FF 00 00 00 00 02
18:56:34	[D]	[uart_debug:114]	<<< 02_FF_FF_00_00_00_00_02
18:56:34	[D]	[uart_debug:114]	<<< 02 FF FF 80 00 00 0A
18:56:34	[D]	[uart_debug:114]	>>> 02_FF_FF_80_00_00_0A
18:56:34	[D]	[uart_debug:114]	<<< 01 00 40 00 00 06 02 7A 00 00 B5
18:56:35	[D]	[uart_debug:114]	>>> 01_00_40_00_00_06_02_7A_00_00_B5
18:56:35	[D]	[text_sensor:069]	‘Operation Mode’: Sending state ‘Unknown’
18:56:35	[D]	[uart_debug:114]	>>> 02 FF FF 00 00 00 00 02
18:56:35	[D]	[uart_debug:114]	<<< 02_FF_FF_00_00_00_00_02
18:56:35	[D]	[uart_debug:114]	<<< 02 FF FF 80 00 00 0A
18:56:35	[D]	[uart_debug:114]	>>> 02_FF_FF_80_00_00_0A
18:56:35	[D]	[uart_debug:114]	<<< 01 00 40 00 00 06 02 7A 00 00 B5
18:56:35	[D]	[uart_debug:114]	>>> 01_00_40_00_00_06_02_7A_00_00_B5
18:56:35	[D]	[uart_debug:114]	>>> 02 FF FF 00 00 00 00 02
18:56:35	[D]	[uart_debug:114]	<<< 02_FF_FF_00_00_00_00_02
18:56:35	[D]	[light:052]	‘Led’ Setting:
18:56:35	[D]	[light:069]	Brightness: 50%
18:56:35	[D]	[light:076]	Red: 0%, Green: 100%, Blue: 0%
18:56:35	[D]	[light:103]	Transition length: 1.0s
18:56:35	[D]	[uart_debug:114]	<<< 02 FF FF 80 00 00 0A
18:56:35	[D]	[uart_debug:114]	>>> 02_FF_FF_80_00_00_0A
18:56:35	[D]	[uart_debug:114]	<<< 01 00 40 00 00 06 02 7A 00 00 B5
18:56:35	[D]	[uart_debug:114]	>>> 01_00_40_00_00_06_02_7A_00_00_B5
18:56:36	[D]	[sensor:104]	‘Heap Free’: Sending state 183620.00000 B with 0 decimals of accuracy
18:56:36	[D]	[sensor:104]	‘Loop Time’: Sending state 41.00000 ms with 0 decimals of accuracy
18:56:36	[D]	[switch:016]	‘UART Logging’ Turning OFF.

gekkekoe · October 19, 2025, 9:34pm

@rokic
Try Release Minor release (proxy fixes) · gekkekoe/esphome-ecodan-hp · GitHub
I found some timing issues that should have been resolved in this one

gekkekoe · October 23, 2025, 7:15pm

Run serial IO on the spare core for low latency, refactor proxy
Add esp core 0 and 1 monitoring
wifi: Remove fast_connect option
AA: Add efficiency probe during dead zone to find a more efficient offset (probe only active while heating)
Use work around for espidf 5.4.2 UART issues. Upgrading to Esphome 2025.10.2
Adds proper retry and timeout for cmd sent to the heatpump
Throttle get service code results (less spamming)

gekkekoe · October 31, 2025, 11:28am

new release: Release Minor release (AA improvements, Proxy improvements, energy counter improvements) · gekkekoe/esphome-ecodan-hp · GitHub

changelog:

Reverted uart workaround and upgraded to esphome 2025.10.3 (it has been fixed in esphome 2025.10.3)
AA: Fixed enforcing safety cap of heating offset
AA: Allow override of outdoor temp sensor
AA: Allow predictive cycle prevention to be turned off during AA
AA: Temporary allow manual editing of offsets (Don’t depend on this, will be removed when algorithm is working stable)
AA: Increased efficiency probe from 0.01 to 0.02 (speedup decay)
Add 0x0f condensing temp fallback if we encounter stuck 40.57 value
Proxy: handle 0x28 byte 11 clear when in proxy
AA: Use multi zone status to ensure that zones are actually operating (for independent zones)
Adjust timeout settings for heatpump and proxy to ensure there’s no overlapping
Use controller day of the year to avoid double counting in the forever increasing counters
Remove sntp usage in the delta_energy_consumed_increasing sensor (use the controller day of the year instead)
Only handle Off → On and On → Off compressor transitions. Ignore the unknown states
Remember states for reported daily consumption and estimated COP (will not be reset after reboot)
AA: adjust z1 and z2 offset independently when boosting

gekkekoe · November 1, 2025, 9:10am

Found a regression, Estimated Total Daily Energy Produced was not reset properly.

remove sntp requirement and use the time from the heatpump to detect day transitions (all external dependencies have been removed)
fixed issue where daily_computed_output_power sensor was not reset on day transition

gekkekoe · November 4, 2025, 1:14pm

Pre-release: Add alternative auto adaptive based on delta T profile. Should be much easier to work with and almost no parameters needed.

GitHub

Release 2025-11-04.3 · gekkekoe/esphome-ecodan-hp

upgraded to esphome 2025.10.4 AA: Add alternative heating strategy: Delta T control AA: Delta T, handle defrost weather by reducing delta T to minimum of the selected profile

documentation: esphome-ecodan-hp/docs/auto-adaptive-delta-t.md at main · gekkekoe/esphome-ecodan-hp · GitHub

jokercho · November 5, 2025, 7:06am

Hi,
Maybe I missed the information somewhere but I cannot understand whether I need logic level shifters between cn105 and Grove port on Atom S3 Lite. From the instructions I can see that the connection is done directly between the devices. But what I found as information is that cn105 port provides logic level 5V (RX/TX) and Atom S3 Lite Grove port is 3.3V. Is there any logic level shifter embedded in Atom S3 Lite? Is it safe connecting directly both devices without logic level shifter?

gekkekoe · November 5, 2025, 8:07am

not needed you can connect the s3 lite directly as shown in the docs

gekkekoe · November 7, 2025, 8:24am

new release:

upgraded to esphome 2025.10.4
AA: Add alternative heating strategy: Delta T control. Please test/use/migrate to this strategy, it will replace the self learning curve in the next release. It should have superior performance. use the simulator to choose the correct profile
AA: Delta T, handle defrost weather by reducing delta T to minimum of the selected profile
AA: Ensure auto adaptive loop (if enabled) is executed on compressor off → on transition
AA: Use z1/z2 return temp instead of primary when using multi zones
Short cycle: handle lockout restore periodically, fixes lockout state stuck when rebooting during lockout
AA: Derive max error range from floor type, ufh = 1.5, hybrid = 2.0, radiator = 2.5
AA: Handle predictive cycle boost when using Delta T strategy
Add Pump consumption, speed setting

jokercho · November 8, 2025, 8:22pm

For my unit Heating delivered, DHW delivered and Cool delivered are not reported. Is there specific configuration somewhere for this.
Also I have a question about the consumed energy. As I understand at the end of the day the total consumed energy for the day is reported. This means that the value that I have in Heating Consumed entry in fact is the value for the previous day. Is this correct? I’m trying to understand how to build correct history graph with the consumption per day