This is quite easy to “fix” yourself by creating template sensors. I’m assuming you have the entities sensor.extra_total and sensor.extra_usage from your Youless - if yours are named different replace the names below with what you’ve got.
Place the following in your templates.yaml file (assuming there’s a line “template: !include templates.yaml” in your configuration.yaml):
- sensor:
- name: "Water totaal"
available: "{{ is_number(states('sensor.extra_total')) }}"
unique_id: sensor.water_totaal
state_class: total_increasing
device_class: water
unit_of_measurement: m³
icon: "mdi:water"
state: "{{ states('sensor.extra_total') | float(0) }}"
- name: "Water verbruik"
unique_id: sensor.water_verbruik
icon: "mdi:water"
unit_of_measurement: l/min
state: "{{ states('sensor.extra_usage') | float(0) / 60 }}"
Then check your configurations file for errors, and restart Home Assistant. You should then see the new enitties in the development tools. If you’re on version 2022.4 or higher you can opt to set the sensor.extra_total and sensor.extra_usage entities to hidden so they won’t appear on auto-generated dashboards anymore. Don’t disable them though, they are needed for the template.
If you want to keep dayly and monthly totals as well, put the following line in your config.yaml (if it is not already there):
utility_meter: !include utility_meters.yaml
And create a file utility_meters.yaml with the following content
water_dagelijks:
source: sensor.water_totaal
name: Water dagelijks
cycle: daily
water_maandelijks:
source: sensor.water_totaal
name: Water maandelijks
cycle: monthly
Do note that by default Home Assistant does not keep long term history by itself. The energy dashboard uses a special long term storage, but normal sensors do not. I use influxdb for that (and Grafana to display it). But that is another topic entirely, you can find lots of topics on that subject here as well.
