COP Calculation

[tgeldhauser]

Hi,

i just added this great integration to read my AIT Heatpump. One thing i am very interested in is the statustics of the COP - somehow i am a bit struck here, as don't seem to get a statistics out of it. My current code is:

template:

• sensor:
  • name: "COP"
    unique_id: "WP_COP"
    #unit_of_measurement: "Watt"
    state_class: "measurement"
    state:
    "{{((states('sensor.luxtronik_0_00_heat_amount_heating') | float(0) / states('sensor.luxtronik_0_00_heat_energy_input') | float(0))) }}"

Also my issue is, that "heat_amount" is the sum and not the current heat - Does anyone have a working code for this he can share ?

Thanks,

Tobias

[AJediIAm]

Hi @tgeldhauser,

When I got started with this integration, I made a SCOP sensor using a shelly smart plug (since the heat energy input was not yet available) but it never worked properly and it broke some time ago. This is a good opportunity to work on it together and maybe document our findings for others to use.

Since the heat energy input was not available yet when the heatpump was installed, the heat amount is the total over the past 4 years while the energy input is the total for the past year. A simple division of the two values to calculate the lifetime COP won't work in my case.

I'm starting with some basic measurements:

Today, the heat_energy_input entity showed 8.28 kWh, dhw_energy_input showed 0.59 kWh
The shelly meter showed 9.4kWh. This leaves 0.53 kWh consumed by other electronics.

Looking at the history, the heat energy input is not very smooth. It's updated every 2 hours or so. We need to keep this in mind. Calculating the COP for a given hour won't work. Calculating the COP over the past 2 hours, day, month or year is all possible.

Got some other stuff to do now, so I'll pick it up later. Next step is to have a look at the utility meter helper to see if I can create daily and monthly sensors for heat energy and heat amount.

Stay tuned ;)

[tgeldhauser]

Hi AJedilAm,

thanks for the quick response.

you are right - i was not aware of the different reading frequency:

... my problem is, that i do not even know how to calculate the COP based on an eg 2h interval - this would be a nice first step and better than no data :)

Can you read the timestamp of the last 2 datapoints in one set and use these to get the data from another set ? I am quite new to HomeAssistant.

From my side i have an additional energy reading from my Shelly giving me the Power consumption of the heatpump - but again, here the timestamp might not be synched, so its a similar issue.

Tobias

[AJediIAm]

Hi Tobias,

I'll get to that, hopefully later this weekend.

Your graphs look very different from mine... Good that we found that.
Which firmware version are you running?

Can you map your german names to the english once?

(or post a screenshot of your diagnostic sensors of the heating device)

[tgeldhauser]

Hi AJedilAm,

sorry for the late reply.

Here is the graph with sensor names:

Hope this helps.

BR, Tobias

[tgeldhauser]

Sorry, i made a mistake, the above plot is already tha plotted change between the current and the previous timestamp. Here is the plot of the state of the sensor:

I am running Version 2024.9.30 on the integration and i think 3.90.2 on the Luxtronik.

BR,

Tobias

[Mehli12]

I have a COP for heating and for warm water as well. I also use a power meter for my heat pumpe. So I have the power consumption from my heat pump.

I have a template for the COP:

{{ (states('sensor.luxtronik2_current_heat_output') | float / states('sensor.wirkleistung_gesamt') | float) | round (1) }}

and then 2 other templates for the COP WW and COP heating

template: - sensor: - name: "COP Heizung" unique_id: 198ba133-be7c-4114-b840-8c9f847d639b state: "{{ ( states('sensor.luxtronik_cop') | float(0) | round(1) ) }}" availability: "{{ is_state('sensor.luxtronik2_status', 'heating') }}" unit_of_measurement: " " state_class: measurement - name: "COP Warmwasser" unique_id: 963d7513-be02-4cdb-860c-015a4ffd7219 state: "{{ ( states('sensor.luxtronik_cop') | float(0) | round(1) ) }}" availability: "{{ is_state('sensor.luxtronik2_status', 'hot water') }}" unit_of_measurement: " " state_class: measurement

Sorry idk how to paste the code in the right way...

Give me this statistics:

Maybe this will help u as well.

[tgeldhauser]

Hi Mehli,

thanks for sharing. Looks great. As i also have a powermeter (Shelly), this could work.

I tried to sort it a bit:

{{ (states('sensor.luxtronik2_current_heat_output') | float / states('sensor.wirkleistung_gesamt') | float) | round (1) }}

template:

• sensor:

  • name: "COP Heizung"
    unique_id: 198ba133-be7c-4114-b840-8c9f847d639b
    state: "{{ ( states('sensor.luxtronik_cop') | float(0) | round(1) ) }}"
    availability: "{{ is_state('sensor.luxtronik2_status', 'heating') }}"
    unit_of_measurement: " "
    state_class: measurement

  • name: "COP Warmwasser"
    unique_id: 963d7513-be02-4cdb-860c-015a4ffd7219
    state: "{{ ( states('sensor.luxtronik_cop') | float(0) | round(1) ) }}"
    availability: "{{ is_state('sensor.luxtronik2_status', 'hot water') }}"
    unit_of_measurement: " "
    state_class: measurement

What are the sensors

• sensor.luxtronik_cop
• sensor.luxtronik2_status

My sensors look differently ? Are they defined previously ?

Thanks,

Tobias

[Mehli12]

Hello,

sensor.luxtronik_cop is the COP overall, like of heating and warm water.

{{ (states('sensor.luxtronik2_current_heat_output') | float / states('sensor.wirkleistung_gesamt') | float) | round (1) }}

This sensor is a helper created by myself.

sensor.luxtronik2_status is the sensor with the status like "warm water" / "heating" / "cooling" this is from the integration.

[AJediIAm]

Got distracted on some other stuff for a bit, but then I came across an example from someone else (Thanks Tim) and remembered to finish this.

Option 1
As we all know, we need to divide the heat energy (output) by the electrical energy (input).

This is relatively easy since the later firmware versions provides the total heat amount in watts.
Using a smart energy plug with power metering, we can create a template sensor get the SCOP *:

{{ (states('sensor.luxtronik2_heat_output') | float(0) /  
states('sensor.smartplug_power') | float(1)) | round(1) }}

Since the energy of the display is included, we should never divide by zero.

SCOP *: describes the total efficiency including power consumption of the display unlike COP which only calculates the efficiency of the heat generator.

Option 2
Alternatively, we can divide the heat energy per hour (output) by the electrical energy per hour (input).

Since the energy input is only updated every two hours, we need a larger timeframe than hours (such as days) or we need to use the smart plug. While we're at it, lets split the SCOP for DHW and heating.

There is a neat little trick to let Home Assistant split an energy sensor into multiple utility meters:

utility_meter:
  hourly_energy:
    source: sensor.energy
    name: Hourly Energy
    cycle: daily
    tariffs:
      - heating
      - dhw

automation:
  triggers:
    - trigger: state
      entity_id: 
        - sensor.luxtronik2_status
      to: Heating
      variables:
        tariff: "heat"
    - trigger: state
      entity_id: 
        - sensor.luxtronik2_status
      to: Domestic Water
      variables:
        tariff: "dhw"
  actions:
    - action: select.select_option
      target:
        entity_id: select.hourly_energy
      data:
        option: "{{ tariff }}"

The automation above stores the "tariff" in a variable and switches the utility meter over to the right "tariff". The result should be two separate utility meters which reset hourly. You might want to add a trigger and tariff for idle and cooling to have it make more sense.

Note: most of this can be created using the UI. Only the variable in the automation needs a bit of yaml editing.

Next, we need an utility meter helper for the output energy. This is relatively straightforward.
Divide the two just like in option 1 and you're done!