That does not fix it. Prepare the new state_class : total_increasing for Home Assistant · Issue #8453 · Koenkk/zigbee2mqtt · GitHub
1 Like
The current changes have been about energy. Water usage is relevant, but it is not energy use.
If you want to measure and graph your water usage, there is nothing to stop you. But it ain’t energy unless you have a lake with a hydro scheme.
3 Likes
Yes I did. Updated Z2M before the core update.
No upgrade available yet, first time such a delay
Rome wasnt built in a day, its only been 2 releases and what they have added is amazing.
Banging on about they should have this and this and yet its only just been released, slow down
3 Likes
I honestly feel we should move from the to simple ‘Energy panel’ to a ‘Home resources panel’ if we really want Home Assistant to give us the complete picture and assist in reducing the ecological footprint.
It would be very educational to see how much energy was used to clean our drinking water supply, and how useful it would be to what that consumption.
We might no (yet) see water in our energy bill directly, I wouldn’t be surprised we will anytime soon.
Water == energy most certainly! In more ways we realize. Even our bills (which might be called Tax… paying that locally every month, based on cumsoption thresholds, just like each and every citizen in the Netherlands ).
1 Like
I try to create GAS Sensor for Energy integration. Unfortunate it does not appear in the drop down list for gas consummation.
- platform: mqtt
state_topic: "peep_sensors/GasCounter"
value_template: "{{(value_json.value | float) * 0.001 }}"
device_class: energy
unit_of_measurement: "m³"
state_class: measurement
name: "Gasverbrauch"
but water is renewable, I do not see any big water problem unless there is a desrtification process in your area.
Energy on the contrary is not yet fully renewable.
Energy to pump water in your area its negligible
My water bill no doubt includes the cost the cost of energy it took to process it. Utilities don’t do it for free
1 Like
Look I don’t disagree, but working out how much energy a cumec of water takes to pump, clean and deliver is no easy task, and hyperlocal.
You might need last_reset: attribute
Not 100% on this
I ran the beta on 3 instances, 2 using a Pi3…
what was the issue?
2021.9.0 - causing my Pi3 to restart over & over ? · Issue #55541 · home-assistant/core (github.com)
Looks like the HA team are after some more information from those with the issue. in the github issue above
One step forward each upgrade.
Water in your house with 4 daughters != energy, showering == energy because of gas/electric usage.
The fact water costs us money in the Netherlands doesn’t make it energy.
In a global world water production == energy, because of transportation, water treatment, in some places desalination…
But I can understand the teams choice to focus on just energy in your home at the moment.
Home assistant already has plenty of features to measure water usage and limit it. Lovelace has plenty of options to make a water dashboard.
Choices have to be made when diverting resources into certain development routes.
Perhaps in the future a climate footprint dashboard will be made, including energy, water consumption and other consumptions. Nothing stands in your way to give a good example, I just don’t think it’s something we’ll see standard in HA for some time 
what was the issue?
Boot loop apparently, according to HA twitter feed.
yeah, I know, it might not be too straightforward getting a local energy/m3 gauge . Getting the big picture is my aim though.
It would be very very easy to simply add the total_increasing water meter to the overview, and add a new circle in the graph. Compare it to the CO2/non fossil circle if needed. Nothing to do with your actual energy contract, but a mere impression of the footprint one causes with the total amount of energy consumed.
They only recently overhauled their webUI, maybe an internal repo?
I see, and yes, we had that on beta (Discord) where b02 caused a restart loop for some. It was fixed though, and was identified as being a ‘Bad regex version’. And didn’t relate to Pi3 specifically as it happened on Pi4 too.
no problem on those 2 instances now using rpi3.
the dev team is on this (different issue?) though, so fully confident your particular issues will be fixed soon!
i dont have the issue