Washing machine water and energy sensors reset to zero after program, how to sum?

I have a Miele washing machine that reports energy and water consumption. Like in the attached image.

My problem is that I have not found a way to sum the consumption. Essentially I only want to sum all the peak values of all the program runs. Riemann integral for example results in way too large value as it obviously sums all the reported values and not only the maximum.

Any ideas how to get total consumption sum from this kind of sensor?

Have a state trigger on the consumption (empty to and from).
Then in the condition template {{ trigger.to_state.state == "0" }}.
Action set input number {{ input number + trigger.from_state.state }}

Perhaps this could be a triggered template sensor.
Most of it is the same it’s just some minor corrections needed

Thank you, I will test that later when I’m back at home!

I never got around trying this as I found that I could just do a utility helper for it, just had to check the delta so it is summing the delta between the values and not the actual values.

I have exactly the same problem. Using a utility helper with delta activated doesn’t work for me, since it increases the sum everytime the sensor updates its value throughout a washing cycle. Could you maybe share or explain your solution further?

Any ideas?

Sorry for the delay, sometimes life just interferes with the hobbies…

What I ended up using is the Utility sensors, with the following configurations. These are automatically generated, but shows the basic idea.

      {
        "entry_id": "10eada4f38026a2cbc2627537699213a",
        "version": 1,
        "domain": "utility_meter",
        "title": "Dryer elapsed time, monthly",
        "data": {},
        "options": {
          "name": "Dryer elapsed time, monthly",
          "source": "sensor.tumble_dryer_elapsed_time",
          "cycle": "monthly",
          "offset": 0.0,
          "tariffs": [],
          "net_consumption": false,
          "delta_values": false
        },
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "user",
        "unique_id": null,
        "disabled_by": null
      },

and

      {
        "entry_id": "9f28efaaf0ddf36dc1b6dc97ef05b3fd",
        "version": 1,
        "domain": "utility_meter",
        "title": "Dryer machine energy consumption, monthly",
        "data": {},
        "options": {
          "name": "Dryer machine energy consumption, monthly",
          "source": "sensor.tumble_dryer_energy_consumption",
          "cycle": "monthly",
          "offset": 0.0,
          "tariffs": [],
          "net_consumption": false,
          "delta_values": true
        },
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "user",
        "unique_id": null,
        "disabled_by": null
      },

Difference is the delta, weirdly the time value was messed up whith the delta: true, and the kwh value needed it. But it works for me with those.

I am using a helper as well WITHOUT DELTA. It has been shaky this winter and I have redone it several times, but always come back to a standard utility helper with the default parameters. At times, it continued counting after the machine had finished. A bug?

Anyway, the result looks like this, as I like for me and everyone else in the household to see the actual consumption:

It could be developed into showing actual cost as well, since we are on an hourly rate.

Unfortunately, I can’t disclose the helper configuration here, since helper configurations don’t seem to be available anywhere.

/Fumble