Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Watermeter on energy dashboard: entity specs ? #24801

Closed
jjvandenberg opened this issue Nov 3, 2022 · 10 comments
Closed

Watermeter on energy dashboard: entity specs ? #24801

jjvandenberg opened this issue Nov 3, 2022 · 10 comments

Comments

@jjvandenberg
Copy link

Feedback

Hi, can you add to the docs, the necessary entity definition for the watermeter, like

  • state_class
  • unit_of_measurement
    -device_class

Thanks !

URL

https://www.home-assistant.io/docs/energy/water/

Version

2022.11

Additional information

No response

@fvschie
Copy link

fvschie commented Nov 3, 2022

I have issues where my water meter sensors (of type 'total', both in liters and m3) aren't showing up. It's possible it needs a total_increasing, which would be annoying, as that's harder to fabricate.

So I second a list of requirements for the sensor.

@helmuto-maker
Copy link

I have these settings - but doesn't work and does not show up as possible entity to choose in water - energy dashboard. My gas-meter does show up as possible entity in the water-section:
state_class: total_increasing
unit_of_measurement: m³
icon: mdi:chart-line
friendly_name: Total Water Use Daily
last_reset: '1970-01-01T00:00:00+00:00'
device_class: water

@helmuto-maker
Copy link

I figured this out. My sensor had two different units in the long term statistics. After fixing this (in developer tools -> statistics), the sensor is available to choose.

@neuhausf
Copy link

neuhausf commented Nov 4, 2022

I had that too, but removing the old statistics didn‘t help. My sensor is a restful, total_increasing with unit m3. Additionally I have setup utility_meters for different periods (hourly, daily, weekly, monthly and yearly). Statistics are generating fine. What am I missing?
884605E0-05B4-4F5E-88ED-2D7AE25559A1

@frenck
Copy link
Member

frenck commented Nov 4, 2022

That sounds backwards? You don't adjust entities to make them work with the energy dashboard... instead configure entities correct according to the data they provide. If they provide the right data, they become available for the energy dashboard.

@jjvandenberg
Copy link
Author

jjvandenberg commented Nov 4, 2022

So if the question was "how do i need to configure my entities so the energy dashboard can use them for the water meter", it would have been answered?
why so unfriendly?

for all that had the same qustion:
unit_of_measurement: m³ (use an uppercase 3, not a regular 3, that's where I went wrong)
device_class: water

seems more people have this question , like #24813

@jjvandenberg
Copy link
Author

jjvandenberg commented Nov 4, 2022

solved it
unit_of_measurement: m³
device_class: water

@mrandt
Copy link

mrandt commented Nov 4, 2022

I had to fiddle with this, too. My watermeter integrates via MQTT.

Eventually I figured out I had to configure the following for my sensor in configuration.yaml:

      unit_of_measurement: "m³"
      device_class: water
      state_class: total_increasing

With this config, I could integrate the sensor into the Energy Dashboad.

I also had to change the unit of my helper variable to track the costs to "EUR/m³" as "€/m³" did not work ;-)

@helmuto-maker
Copy link

I find it a bit frustrating that is so difficult to find information on exactly how the sensors should be configured to comply with the energy-dashboard. The dashboard is really excellent, so would be nice with some clear guidance on the sensors (including the cost sensors).

@helmuto-maker
Copy link

That sounds backwards? You don't adjust entities to make them work with the energy dashboard... instead configure entities correct according to the data they provide. If they provide the right data, they become available for the energy dashboard.

It is just very difficult to figure out what is "the right data"

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants