-
-
Notifications
You must be signed in to change notification settings - Fork 28.9k
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
Wh is not a recognized volume unit - 2023.9 beta #99525
Comments
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) energy documentation |
The bug is related to the unit of the gas price, and the linked PR fixes that. However, that bug is very old and was not introduced in 2023.9 beta. |
I didn't change anything with 9 beta. The price sensor I am using house_consumption_cost is in $/kWh. I have other sensors in the gas consumption dashboard which are in units kWh and are still functioning correctly, but this one sensor which is reporting in Wh is causing this issue, which I note is different to the denominator of the price sensor above. |
The problem
With the 2023.9 beta Wh is again causing issues on the Gas Consumption dashboard.
Gas consumption measured in Wh is an allowed sensor for the Gas consumption dashboard:
This was functional with 2023.8 and earlier, kWh is still functional, just sensors in Wh are causing this issue.
What version of Home Assistant Core has the issue?
core-2023.9.0b
What was the last working version of Home Assistant Core?
core-2023.8
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
energy
Link to integration documentation on our website
https://www.home-assistant.io/docs/energy
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
The fix for a similar issue back in November was:
home-assistant/frontend#14448
unsure if there is a similar cause this time around?
The text was updated successfully, but these errors were encountered: