-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
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
Cannot select correct unit (kW) for sensor.energy_log_current_power_consumption_32306 #127832
Comments
Hey there @elupus, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) nibe_heatpump documentation |
Are you sure. "Current".here could mean the momentary power. If it is wrong it need to be fixed in upstream lib. |
I've launched pull request yozik04/nibe#181 to fix this in the upstream lib. |
Saw that this fix was commited in upstream lib, would it be possible for a new release to get this updated and fixed? |
@elupus would it be possible to bump the integration to version 2.13 for this fix to be part of next HA version? |
Good evening! |
Go ahead and create a pull request. its a community project, so its up to all to contribute. I can review, but not time to do the changes myself at the moment. |
The problem
Entity "NIBE S320 current power consumption" (sensor.energy_log_current_power_consumption_32306) should have W or kW unit of measurement, because it is CURRENT consumption. But only Wh or kWh can be selected .
What version of Home Assistant Core has the issue?
core-2024.10.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
NIBE heat pump
Link to integration documentation on our website
https://www.home-assistant.io/integrations/nibe_heatpump/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: