With the energy dashboard now set water to m3 instead of L
I cannot hover the dashboard anymore if I use less then 10L in that hour.
So I won’t know if I consumed 1 or 2L.
(sorry no screenshot for now)
But having this hover option at least on a 3 decimal digets would be really helpfull.
or just go back to Liter,
I see there are some workarounds, But I need time to fix this.
You can try my custom integration; it was not affected by the HA 2025.8.2 update.
I think we can expect a lot of migrations to webawesome components in the future 
GitHub · Where software is built.
here we go… holding breath
It’s very simple. HA just shows what your integration provides.
Go to the Integration Settings->Devices, click on the value with Water usage and change M3 back to L. Within an hour it shows L in the Energy Dashboard again.
Worked fine for my HomeWizard Energy Water meter.
Has anyone else notice that when you restart Home Assistant the disabled sidebar devices are displayed. Only with a browser refresh do they go away. This happens with multiple browsers.
It happens to me but only in companion app on iOS. App also forgets the theme I set.
Refreshing does not help. For sidebar items I need to enter sidebar configuration popup and just save setup (all options there are remembered properly, just not respected). For theme I need to re-set it again.
probably,
but now flushing the toilet costs me 6M3 of water
I added a new sensor for L
but using this one removes my history
What’s the problem? 
No, that custom card uses mwc-button and mwc-icon-button so will need to be updated to use ha-button.
Thanks. I’ll pass that on.
You should not add a new sensor, as that is exactly what you would get by doing that.
Home Assistant history will convert the water usage to the correct amount.
When mine was back to m3 it showed as 353,64 and after changing back to L it showed as 353.643 which is correct. The history only stores the numeric value, for viewing it converts it to the unit you provide.
1m3 = 1000L.
My L/min value didn’t change by the way, only the cumulative usage.
I cannot imagine that somebody thought this was a good idea:
This is very ugly and way too much in your face, Is this intended?
Yes,
But if I simply register m3 as L I’m a factor 1000 off.
history is ok, but current values are not.
I changed the sensor itself in esphome, and now everything seems to be ok.
I am not using ESPHome, for me I only needed to change it in HA itself and it converted the values correctly.
sorry, user error (allowlist_external_dirs was wiped during testing, and never turned back on…)
btw, this is for the Dutch users
file size is translated, the others are not.
Should we reset Bestandsgrootte to File size, to keep them ordered corectly, or, translate the others to Bestand, en Lokaal Bestand…?
I really dislike translated integration names… especially if they touch system nomenclature like here
Lokalise even mentions it being translated in the reload services but its not even there?
Very nice solution
Yeah, those integrations are a bit weird/different. Their names are “things” as opposed to brands.
There does not seem to be a hard rule on what integrations to translate. Looking at my integrations (ignoring the ones with brand names) it seems a mix of translated names and not translated ones.
For the File case I would personally go for translating them all. “Bestand” and “Lokaal bestand” sound fine to me.
