Open joncage opened 7 months ago
The same for EDLA models. I installed it today and created the following workaround:
- platform: template
sensors:
altherma_operation_mode:
unique_id: "altherma_operation_mode"
friendly_name: "Altherma Operation Mode"
value_template: >
{% set value = state_attr('sensor.altherma_sensors', 'Operation Mode') %}
{% if value == 'Heating' %}
Running
{% elif value == 'Fan Only' %}
Idle
{% endif %}
I'm sorry, to reply on this older thread, but it's very confusing to me. So far I understood, when sensor.espaltherma_operation = fan only --> system is IDLE. (Heating = Heating :))
However, today I saw something strange. sensor.espaltherma_iuoperation --> Heating, & sensor.espaltherma_operation = Fan Only So, I would expect idle. Right?
However, flow sensor showed a flow, external power meter detected kW of power, temperature was rising.. heatpump was really heating.
A few hours later, both iuoperation as _operation swichted to heating.
Took me a while to realise, but it looks like then the
Operational Mode
isFan Only
in my heat pump (no fans that I can see are running during these periods), what it really means isNot Running
,Inactive
orIdle
or something along those lines.Could this be changed to more clearly report the state when the heat pump is not active?
I'm using the
Altherma(LT_CB_11-16kW Bizone).h
configuration currently if that makes a difference. I think I'm using the wrong one and we actually have a signle-zone system with two thermostats which affect some flow switches the Daikin machinery doesn't report on as I can't see a difference in any of the logged outputs when one thermostat calls vs the other.