Hey there @ooii, mind taking a look at this issue as it has been labeled with an integration (suez_water) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

suez_water documentation
suez_water source
_{^{(message by IssueLinks)}}

To work around this I have the following template sensor (that also converts to m3) :

template:
  - sensor:
      - name: water
        unit_of_measurement: "m.."
        state: "{{ states('sensor.suez_water_client') | float * 0.001 }}"
        device_class: water
        state_class: total_increasing
        unique_id: water

I can see this one in the selection list for Energy sensor

Thanks a lot for this solution.
As a newbie, could you please indicate if this template has to be included right away in the configuration.yam file.
I noticed that the Suez integration fail often to receive data from "toutsurmoneau" Suez site and need to be reloaded in order to receive new data.
Is there also a way to set the frequency for the reload of data ?
Thanks for your help,

Hello,

@ybizeul thanks for sharing your configuration. Regarding the unit_of_measurement, it should be m³ to have it working IMHO.
However even by doing that I have this error message in the energy dashboard "statistics_not_defined sensor.water"

It is m3 (exponent) but is displayed as two dots probably because of utf8 terminal settings.

It should not get a state class since the value of the sensor is the value of yesterday. Instead we have some integrations that can load older data as statistics, it should do that

Thanks for clarifying ! Hopefully the author will be able to implement that

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

It's not working

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Unstale

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Unstale

Hi,
I'm coming a bit late to this but I have started to make some changes to suez_water integration.

I should be addressing this in future improvments.
I have experimented a bit and I'm planning to implement it like @joostlek said by storing directly data in statistics.

I'll keep you updated as I move forward with this.