Repository navigation
Replies: 16 comments 15 replies
|
I would prefer if you could move to the new espaltherma v2 which has more features than esphome and daikin cycle ml supports more daikin model than esphome. Installing is very easy |
|
Some help needed. Espaltherma2 beta publishes the names of the sensors as sensors.espalthermasensors hence ML cannot find them. Is there a way to get ML looking for those sensornames? |
|
usually v2 is also publishing 1 main sensor with all the attributes please check it you have this? |
|
Hi @fransh47, Thanks for the screenshots. This reveals an important detail about the new ESPAltherma v2 (beta). Depending on how your MQTT broker is configured, v2 might publish telemetry in two different ways:
Daikin Cycle ML requires a single source entity to read all telemetry from. Let's figure out exactly what your setup is providing. Path A: Check the Main Sensor (Attributes)If your setup uses the monolithic entity, go to Developer Tools -> Template and run this: {{ states('sensor.althermasensors') }}
{{ state_attr('sensor.althermasensors', 'I/U operation mode') }}
{{ state_attr('sensor.althermasensors', 'Flow sensor (l/min)') }}
{{ state_attr('sensor.althermasensors', 'Discharge pipe temp.') }}
{{ state_attr('sensor.althermasensors', 'I/U Thermostat ON/OFF') }}Path B: Smart Jinja for Individual EntitiesIf your setup creates individual entities (like your second screenshot suggests), run this to list everything ESPAltherma has created: {% for state in states.sensor | selectattr('entity_id', 'match', 'sensor.espaltherma_') %}
{{ state.entity_id }}: {{ state.state }}
{% endfor %}And this to check the critical ML attributes: Operation Mode: {{ states('sensor.espaltherma_operation_mode') }}
Flow Sensor: {{ states('sensor.espaltherma_flow_sensor') }}
Outdoor Temp: {{ states('sensor.espaltherma_r1t_outdoor_air_temp') }}
INV Frequency: {{ states('sensor.espaltherma_inv_frequency') }}
Defrost: {{ states('sensor.espaltherma_defrost_operation') }}3. Point Daikin Cycle ML to the Correct SourceOnce we identify the correct entity or structure:
Next Step: |
|
Hello elRadix,
The screen shots.
Path A:

Path B part 1:

Path B part 2:

Path B path 2 repeated with name change, for example INV frequency where “frequency” is replaced by “rps”

So the differences are in the naming.
Regards,
Frans
… Op 6 nov 2026, om 09:45 heeft elRadix ***@***.***> het volgende geschreven:
Hi @fransh47 <https://github.com/fransh47>,
Thanks for the screenshots. This reveals an important detail about the new ESPAltherma v2 (beta). Depending on how your MQTT broker is configured, v2 might publish telemetry in two different ways:
As attributes under a single main entity (sensor.althermasensors).
As individual entities (e.g., sensor.espaltherma_operation_mode).
Daikin Cycle ML requires a single source entity to read all telemetry from. Let's figure out exactly what your setup is providing.
Path A: Check the Main Sensor (Attributes)
If your setup uses the monolithic entity, go to Developer Tools -> Template and run this:
{{ states('sensor.althermasensors') }}
{{ state_attr('sensor.althermasensors', 'I/U operation mode') }}
{{ state_attr('sensor.althermasensors', 'Flow sensor (l/min)') }}
{{ state_attr('sensor.althermasensors', 'Discharge pipe temp.') }}
{{ state_attr('sensor.althermasensors', 'I/U Thermostat ON/OFF') }}
Path B: Smart Jinja for Individual Entities
If your setup creates individual entities (like your second screenshot suggests), run this to list everything ESPAltherma has created:
{% for state in states.sensor | selectattr('entity_id', 'match', 'sensor.espaltherma_') %}
{{ state.entity_id }}: {{ state.state }}
{% endfor %}
And this to check the critical ML attributes:
Operation Mode: {{ states('sensor.espaltherma_operation_mode') }}
Flow Sensor: {{ states('sensor.espaltherma_flow_sensor') }}
Outdoor Temp: {{ states('sensor.espaltherma_r1t_outdoor_air_temp') }}
INV Frequency: {{ states('sensor.espaltherma_inv_frequency') }}
Defrost: {{ states('sensor.espaltherma_defrost_operation') }}
3. Point Daikin Cycle ML to the Correct Source
Once we identify the correct entity or structure:
Go to Settings -> Devices & Services -> Daikin Cycle ML.
Click Configure (the gear icon).
Select Source sensor and model only (quick).
Change the Source sensor to sensor.althermasensors (or the specific entities, if we need to build a template sensor).
Select your model and submit. The integration will reload and begin reading the data.
Next Step:
Please run the Jinja code from either Path A or Path B (whichever applies to your setup) and paste the output here. If you are using individual entities, I can give you a template: YAML snippet to combine them into the exact format Daikin Cycle ML expects.
—
Reply to this email directly, view it on GitHub <#176?email_source=notifications&email_token=A5WCLREWRCTHW7QMUVXJCWD5XWFRXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGM2TSOBWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19435986>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5WCLRCTH6MNNRNJSAGUI6D5XWFRXAVCNFSNUABJKJSXA33TNF2G64TZHMYTGOBYGA2TINZSGY5UI2LTMN2XG43JN5XDWMJRGEZTQOBTGOQXMAQ>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/A5WCLRHFWUD4BKS4CAT7HWD5XWFRXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGM2TSOBWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/A5WCLRGZQ5QE6QGBJ6K2CHD5XWFRXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGM2TSOBWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today!
You are receiving this because you were mentioned.
|
|
you forgot to add the screenshots |
|
Hello elRadix,
The complete list EspAltherma 2 Beta is transmitting to HA for my system.
I think that a bit of coordination would help avoiding different naming between systems; we could make a translation/equivalence list as you suggest. The source is EspAltherma V2 in this case as this transmits the info but in principle all should use the naming by Daikin if that is available.
sensor.espaltherma_wifirssi: -39
sensor.espaltherma_freemem: 161412
sensor.espaltherma_uptime: 85777
sensor.espaltherma_ip: 192.168.2.189
sensor.espaltherma_operation_mode: Fan Only
sensor.espaltherma_ou_error_type: Normal
sensor.espaltherma_ou_error_code: 0
sensor.espaltherma_r1toutdoor_air_temp: 6.5
sensor.espaltherma_discharge_pipe_temp: 49.5
sensor.espaltherma_heat_exchanger_midtemp: 5
sensor.espaltherma_inv_primary_current_a: 0
sensor.espaltherma_inv_secondary_current_a: 0
sensor.espaltherma_inv_fin_temp: 6
sensor.espaltherma_inv_frequency_rps: 0
sensor.espaltherma_fan_1_step: 0
sensor.espaltherma_iu_operation_mode: Stop
sensor.espaltherma_iu_error_code: 0
sensor.espaltherma_iu_error_type: Normal
sensor.espaltherma_lw_setpoint_main: 41.3
sensor.espaltherma_leaving_water_temp_before_buh_r1t: 20.6
sensor.espaltherma_leaving_water_temp_after_buh_r2t: 20.5
sensor.espaltherma_refrig_temp_liquid_side_r3t: 20
sensor.espaltherma_inlet_water_tempr4t: 20.5
sensor.espaltherma_indoor_ambient_temp_r1t: 19.6
sensor.espaltherma_lw_setpoint_add: 41
sensor.espaltherma_rt_setpoint: 30
sensor.espaltherma_flow_sensor_lmin: 0
sensor.espaltherma_water_pressure: 1.8
sensor.espaltherma_stats_heat_output_kw: unknown
sensor.espaltherma_stats_electrical_input_estimated_kw: 0.0
sensor.espaltherma_stats_cop_estimated: unknown
sensor.espaltherma_stats_cop_today_heating: 3.82
sensor.espaltherma_stats_cop_today_hot_water: unknown
sensor.espaltherma_stats_heat_today_heating_kwh: 57.04
sensor.espaltherma_stats_heat_today_hot_water_kwh: 0.0
sensor.espaltherma_stats_heat_today_cooling_kwh: 0.0
sensor.espaltherma_stats_electricity_today_heating_kwh: 14.92
sensor.espaltherma_stats_electricity_today_hot_water_kwh: 0.0
sensor.espaltherma_stats_electricity_today_cooling_kwh: 0.0
sensor.espaltherma_stats_compressor_starts_today: 26
sensor.espaltherma_stats_compressor_starts_last_hour: 0
sensor.espaltherma_stats_defrosts_today: 13
sensor.espaltherma_stats_compressor_run_today_min: 598.48
sensor.espaltherma_stats_backup_heater_today_min: 0.0
sensor.espaltherma_stats_last_run_min: 42.07
sensor.espaltherma_stats_last_pause_min: 1.0
sensor.espaltherma_last_update: 19:11:11
Regards,
Frans
… Op 6 nov 2026, om 09:45 heeft elRadix ***@***.***> het volgende geschreven:
Hi @fransh47 <https://github.com/fransh47>,
Thanks for the screenshots. This reveals an important detail about the new ESPAltherma v2 (beta). Depending on how your MQTT broker is configured, v2 might publish telemetry in two different ways:
As attributes under a single main entity (sensor.althermasensors).
As individual entities (e.g., sensor.espaltherma_operation_mode).
Daikin Cycle ML requires a single source entity to read all telemetry from. Let's figure out exactly what your setup is providing.
Path A: Check the Main Sensor (Attributes)
If your setup uses the monolithic entity, go to Developer Tools -> Template and run this:
{{ states('sensor.althermasensors') }}
{{ state_attr('sensor.althermasensors', 'I/U operation mode') }}
{{ state_attr('sensor.althermasensors', 'Flow sensor (l/min)') }}
{{ state_attr('sensor.althermasensors', 'Discharge pipe temp.') }}
{{ state_attr('sensor.althermasensors', 'I/U Thermostat ON/OFF') }}
Path B: Smart Jinja for Individual Entities
If your setup creates individual entities (like your second screenshot suggests), run this to list everything ESPAltherma has created:
{% for state in states.sensor | selectattr('entity_id', 'match', 'sensor.espaltherma_') %}
{{ state.entity_id }}: {{ state.state }}
{% endfor %}
And this to check the critical ML attributes:
Operation Mode: {{ states('sensor.espaltherma_operation_mode') }}
Flow Sensor: {{ states('sensor.espaltherma_flow_sensor') }}
Outdoor Temp: {{ states('sensor.espaltherma_r1t_outdoor_air_temp') }}
INV Frequency: {{ states('sensor.espaltherma_inv_frequency') }}
Defrost: {{ states('sensor.espaltherma_defrost_operation') }}
3. Point Daikin Cycle ML to the Correct Source
Once we identify the correct entity or structure:
Go to Settings -> Devices & Services -> Daikin Cycle ML.
Click Configure (the gear icon).
Select Source sensor and model only (quick).
Change the Source sensor to sensor.althermasensors (or the specific entities, if we need to build a template sensor).
Select your model and submit. The integration will reload and begin reading the data.
Next Step:
Please run the Jinja code from either Path A or Path B (whichever applies to your setup) and paste the output here. If you are using individual entities, I can give you a template: YAML snippet to combine them into the exact format Daikin Cycle ML expects.
—
Reply to this email directly, view it on GitHub <#176?email_source=notifications&email_token=A5WCLREWRCTHW7QMUVXJCWD5XWFRXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGM2TSOBWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19435986>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5WCLRCTH6MNNRNJSAGUI6D5XWFRXAVCNFSNUABJKJSXA33TNF2G64TZHMYTGOBYGA2TINZSGY5UI2LTMN2XG43JN5XDWMJRGEZTQOBTGOQXMAQ>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/A5WCLRHFWUD4BKS4CAT7HWD5XWFRXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGM2TSOBWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/A5WCLRGZQ5QE6QGBJ6K2CHD5XWFRXA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGM2TSOBWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today!
You are receiving this because you were mentioned.
|
|
Hi @fransh47, Excellent — this output reveals the exact scope. Two things to fix: one on our side (native support for individual entities), one on your side (5 required sensors not yet enabled in ESPAltherma v2 beta). Part 1 (our bug): native support for individual entitiesConfirmed: ESPAltherma v2 beta publishes telemetry as individual entities ( Native support is being built for the next patch release (v1.19.11):
I will post an update here when v1.19.11 ships. Part 2 (your config): 5 required sensors missingComparing your entity list to what Daikin Cycle ML needs, 5 required sensors are not enabled in your ESPAltherma v2 configuration:
Result without these:
Fix (in ESPAltherma v2 web UI):
Part 3: naming quirks are expected in v2You spotted Our auto-discovery will reverse this algorithm. Next step: Run this Jinja after enabling the 5 sensorsOnce you have enabled the 5 missing sensors and restarted ESPAltherma, paste this into Developer Tools → Template: Note: the exact entity name for 3-way valve may differ slightly (e.g. No template sensor needed. When v1.19.11 ships, you will select "Individual entities" in the config and it will auto-discover everything. |
|
Hi elRadix,
Will test is later. Short question now: I do not have DHW hence sensors not activated. If I activate them the valve will show up un EspAlthermav2. What to do?
Frans
… Op 7 nov 2026, om 10:53 heeft elRadix ***@***.***> het volgende geschreven:
Hi @fransh47 <https://github.com/fransh47>,
Excellent — this output reveals the exact scope. Two things to fix: one on our side (native support for individual entities), one on your side (5 required sensors not yet enabled in ESPAltherma v2 beta).
Part 1 (our bug): native support for individual entities
Confirmed: ESPAltherma v2 beta publishes telemetry as individual entities (sensor.espaltherma_*) rather than as attributes under a single sensor.althermasensors entity.
Native support is being built for the next patch release (v1.19.11):
Config flow: new "Source type" selector (Monolithic entity, Individual entities (v2 beta), Auto-detect)
Auto-discovery by slug-matching. Your slug quirks (see Part 3) will be handled natively
Optional override for edge cases
I will post an update here when v1.19.11 ships.
Part 2 (your config): 5 required sensors missing
Comparing your entity list to what Daikin Cycle ML needs, 5 required sensors are not enabled in your ESPAltherma v2 configuration:
Missing sensor Why it matters
3way valve(On:DHW_Off:Space) Cannot distinguish DHW cycles from space heating
Defrost Operation Cannot detect defrost cycles in real time
Water pump operation Cannot tell if circulating pump is running
BUH Step1 Cannot detect backup heater stage 1
BUH Step2 Cannot detect backup heater stage 2
Result without these:
DHW cycles are misclassified as heating
Defrosts appear invisible (you have 13 today per stats, but we cannot detect them live)
Backup heater contribution to COP is not measured
BUH excessive alerts will not fire when expected
Fix (in ESPAltherma v2 web UI):
Open the ESPAltherma v2 web interface
Go to Settings → Definitions (or Sensor selection — depends on beta version)
Enable these 5 sensors
Save and restart ESPAltherma
Part 3: naming quirks are expected in v2
You spotted r1toutdoor (double-t) and other naming differences. These are v2's slug algorithm, not bugs:
R1T-Outdoor air temp. → r1toutdoor_air_temp
Inlet water temp.(R4T) → inlet_water_tempr4t
Discharge pipe temp.(R2T) → discharge_pipe_temp
Our auto-discovery will reverse this algorithm.
Next step: Run this Jinja after enabling the 5 sensors
Once you have enabled the 5 missing sensors and restarted ESPAltherma, paste this into Developer Tools → Template:
**Core Attributes:**
Operation Mode: {{ states('sensor.espaltherma_operation_mode') }}
Flow Sensor: {{ states('sensor.espaltherma_flow_sensor_lmin') }}
Outdoor Temp: {{ states('sensor.espaltherma_r1toutdoor_air_temp') }}
INV Frequency: {{ states('sensor.espaltherma_inv_frequency_rps') }}
Leaving Water (R1T): {{ states('sensor.espaltherma_leaving_water_temp_before_buh_r1t') }}
Leaving Water (R2T): {{ states('sensor.espaltherma_leaving_water_temp_after_buh_r2t') }}
Inlet Water (R4T): {{ states('sensor.espaltherma_inlet_water_tempr4t') }}
**New Required Attributes (check after enabling):**
3-Way Valve: {{ states('sensor.espaltherma_3way_valveondhw_offspace') }}
Defrost Operation: {{ states('sensor.espaltherma_defrost_operation') }}
Water Pump Operation: {{ states('sensor.espaltherma_water_pump_operation') }}
BUH Step 1: {{ states('sensor.espaltherma_buh_step1') }}
BUH Step 2: {{ states('sensor.espaltherma_buh_step2') }}
**All ESPAltherma Entities:**
{% for state in states.sensor | selectattr('entity_id', 'match', 'sensor.espaltherma_') %}
{{ state.entity_id }}: {{ state.state }}
{% endfor %}
Note: the exact entity name for 3-way valve may differ slightly (e.g. sensor.espaltherma_3way_valve without the On/DHW suffix). If the template returns unknown, check the full list at the bottom to see the actual name.
No template sensor needed. When v1.19.11 ships, you will select "Individual entities" in the config and it will auto-discover everything.
—
Reply to this email directly, view it on GitHub <#176?email_source=notifications&email_token=A5WCLRGTT7HFNYPRSW5PJR35X3WKRA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGU3DQMZRUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19456831>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5WCLRCSL2XATJEV667ZCJ35X3WKRAVCNFSNUABJKJSXA33TNF2G64TZHMYTGOBYGA2TINZSGY5UI2LTMN2XG43JN5XDWMJRGEZTQOBTGOQXMAQ>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/A5WCLRDHOV4762DO64UEJ7D5X3WKRA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGU3DQMZRUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/A5WCLREJFQRMFFOKKLX46O35X3WKRA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGU3DQMZRUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today!
You are receiving this because you were mentioned.
|
|
Which model is your Daikin? |
|
EHBH08E6V / ERGA06EVH
… Op 7 nov 2026, om 14:26 heeft elRadix ***@***.***> het volgende geschreven:
Which model is your Daikin?
—
Reply to this email directly, view it on GitHub <#176?email_source=notifications&email_token=A5WCLREZLHJOOUWGXRN4QPT5X4PIJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGU4TAMRXUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19459027>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5WCLRHQZOTM4LNQEGVW2GL5X4PIJAVCNFSNUABJKJSXA33TNF2G64TZHMYTGOBYGA2TINZSGY5UI2LTMN2XG43JN5XDWMJRGEZTQOBTGOQXMAQ>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/A5WCLRHA6MYPBPHE33IFXOD5X4PIJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGU4TAMRXUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/A5WCLRA775DF25SHCILIYOD5X4PIJA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJUGU4TAMRXUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today!
You are receiving this because you were mentioned.
|
|
new version is 1.2 is published, can you try and report back |
|
Hi @fransh47 — your screenshots are incredibly helpful. We've analyzed them line-by-line and identified exactly what's happening. You are running a Bivalent Direct (SH) setup. When outdoor temp drops below your [C-03] threshold, the Daikin intentionally stops the heat pump and activates your external boiler via the Erlaubnissignal (BUH1 dry contact on EKRP1HB). This explains both discrepancies perfectly: 1. Runtime under-count (6x too low)ESPAltherma shows 11h 56m, we show 1.88h. Our detector sees the intentional HP-off as a "stuck IDLE" state (tracked as #285). We are building bivalent-aware detection so the integration knows the HP is supposed to be off during boiler handover. 2. Live thermal power = 0.02 kW (should be 4.0 kW)Your ESPAltherma screenshot shows Action needed: Enable 4 registers in ESPAltherma v2To fix both issues in the next release, we need you to expose a few specific registers that are likely disabled by default. Please go to your ESPAltherma Web UI → Settings → Definitions and enable the checkboxes for these exact labels: Note: After enabling them and restarting ESPAltherma, please paste the output of this template in Developer Tools → Template: What we are buildingYour setup is now our reference case for Bivalent Direct (SH). In the next release we are adding:
We also noticed your ESPAltherma dashboard shows a 3-way valve to a DHW tank you don't have. That's a known ESPAltherma rendering quirk (it assumes a tank when the valve register is present). Our integration correctly ignores it based on your actual DHW sensors being unavailable. Thanks for the detailed report |
|
Hi @fransh47 — quick follow-up on the runtime under-count (the COP / 3-way valve issue is now tracked in #328, we're making the valve optional in an upcoming release). For the runtime mismatch (you saw ~45,000s, we show ~4,000s): we need to rule out a HA-restart reset vs. a cycle-detection gap. Could you please share:
|
|
Hi Frans, Good news — v1.22.3 is out and directly addresses your Bivalent Direct setup. Here's the full picture and what to do. What was wrongYour ESPAltherma setup is Bivalent Direct (SH-only) — no DHW tank exists, so disabling the
What v1.22.3 fixes
Your setup — exact steps
Two things to confirm after you update
If both work, you can leave Full guide📘 CONFIGURATION.md §4.8 — Bivalent systems The guide includes a decision matrix for the other two bivalent types (Indirect DHW, Indirect DHW+SH) in case you ever help someone on one of those setups. If something doesn't workPlease share:
I'd rather know immediately if Thanks again for the detailed report — #176 is what drove the — @elRadix |
|
Short one: complains about missing attribute, must be the valve.Op 11 nov 2026 om 21:13 heeft elRadix ***@***.***> het volgende geschreven:
let it run for a day or 2 and report back
I'll check for the card later :)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|























Uh oh!
There was an error while loading. Please reload this page.
Hi,
I'm currently using esphome-altherma (https://github.com/jjohnsen/esphome-altherma). It was more efficient for me, given the ESP32 boards I had and my existing ESPHome setup.
I'm very interested in the Daikin Cycle ML solution. Would it be possible to support esphome-altherma, or would I need to migrate to ESPAltherma?
Thanks for your reply and for your work!
Pierre
All reactions