home-assistant
[OpenHardwareMonitor] UoM detected based not aligned with real value
The problem
Reopening of ticket https://github.com/home-assistant/core/issues/88911 The hardware monitor UoM and the HA integraiton sensor UoM don't match.
Now in HA 2024.10 this raiser repair issues warning because the UoM keeps changing.
The unit of 'Ethernet Throughput Download Speed' (sensor.ethernet_throughput_download_speed) changed to 'MB/s' which can't be converted to the previously stored unit, 'KB/s'. If the historic statistic values have a wrong unit, you can update the units of the old values. The values will not be updated. Otherwise you can choose to delete all historic statistic values, and start over.
How do you want to fix this issue?
Update the unit of the historic statistic values from 'KB/s' to 'MB/s', without converting.
Delete all old statistic data for this entity
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
Open Hardware Monitor
Link to integration documentation on our website
https://www.home-assistant.io/integrations/openhardwaremonitor/
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
![home-assistant[bot] avatar](https://avatars.githubusercontent.com/in/97978?v=4 "Published by a pub.dev verified publisher"){kind=small}
Nothing... It's been opening for at least nearly 2 years since https://github.com/home-assistant/core/issues/88911#issue-1603231683 In there, @joostlek mentioned he had it in his list to give it some revamp.
According to https://www.home-assistant.io/integrations/openhardwaremonitor/: "The Open Hardware Monitor integration was introduced in Home Assistant 0.48, and it's used by 6 active installations." So it's an old core integration which would definetly need some love, but at the same time it only has 6 users with analytics notified.
Nearly everyone just recommends to install https://www.home-assistant.io/integrations/glances/ but I recall I tried and some of the information was not available, can't recall if network speeds or gpus or cpus temperatures. Maybe I'll give it another go to see if it has been improved/added since I tried it.
Yeah i've been looking at glances too but i don't think Glances reports fan speeds.
Seeing the same here too. What's happening is that OpenHardwareMonitor (and LibreHardwareMonitor) itself changes the units it reports in response to changing conditions, I see this mostly on network interfaces which change units between MB/s to GB/s to KB/s several times each polling interval so I'm constantly spammed with these unit change warnings.
I'd suspect that the integration would have to manually do the conversions to some common unit.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
![issue-triage-workflows[bot] avatar](https://avatars.githubusercontent.com/u/13844975?v=4 "Published by a pub.dev verified publisher"){kind=small}
Issue for me as well :-) I use the integration on 12 HA installation. Would be awesome to get this fixed. I've asked in the LHWM git for an option to simply choose a fixed unit as well: https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/issues/1701
Glances is not really possible since no fan speeds and a ton of other info missing.
Also having this issue. It's particularly vexing because KB/s, MB/s, GB/s, etc. are all entirely convertible between them.
Up to 93 active (registered) installations now! I think the main use case is for Windows since Glances can't return CPU temp. I get it after every HA restart for 2 entities (GPU throughput and something else). Would be nice to have a fix.
indeed, this seems to still be an issue.... ideally openhardwaremonitor would let us stick to one uom.... but maybe the integration could let us select one and convert to that uom whenever the program changes... i get these repairs all the time for lots of things... disk and network usage changing between mb/s and kb/s or are we being lazy and theres a good templating solution to the problem
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
still an issue as of
Home Assistant OS Core 2025.10.1 Supervisor 2025.10.0 Operating System 16.2 Frontend 20251001.0
Now there's a new integration since 2025.10 https://www.home-assistant.io/integrations/libre_hardware_monitor which seems to be more stable. (although i'm now impacted by this issue https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/issues/1844 so can't test).
still an issue as of
Home Assistant OS Core 2025.10.1 Supervisor 2025.10.0 Operating System 16.2 Frontend 20251001.0
Now there's a new integration since 2025.10 https://www.home-assistant.io/integrations/libre_hardware_monitor which seems to be more stable. (although i'm now impacted by this issue LibreHardwareMonitor/LibreHardwareMonitor#1844 so can't test).
Confirmed issue still persists. Did not know about the new integration though, I'll have to test that out — have not had issues with LHM's driver myself.
Now there's a new integration since 2025.10 https://www.home-assistant.io/integrations/libre_hardware_monitor which seems to be more stable. (although i'm now impacted by this issue LibreHardwareMonitor/LibreHardwareMonitor#1844 so can't test).
Confirmed issue still persists. Did not know about the new integration though, I'll have to test that out — have not had issues with LHM's driver myself.
nevermind, with the new integration the error also appeared. What we might be lucky with this is that the new integration is 'platinum' quality, so hopefully might have better support as its a brand new one than this one.
See https://github.com/home-assistant/core/issues/154139#issuecomment-3390255625
Just to note, even with a nightly build of LHM it will only work with the new integration. The openhardwaremonitor one should be deprecated eventually.
Thanks for the update! Just saw the other issue ticket and your reply. Not sure when a 'official' new version will be released. Last ones only happened once a year... https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/tags I just installed the latest nightly. As I understand the integration is ready to support it and the 'stable UoM' fix included. Will revert if still an issue. Thanks!
PD: Do you know if it will support choosing a fixed/specific throughput speed UoM? Other integrations with throughputs, like https://www.home-assistant.io/integrations/systemmonitor/, show the following extra field in the settings of the entity. Thanks!
I just installed the latest nightly. As I understand the integration is ready to support it and the 'stable UoM' fix included.
Correct, it should always be fixed at KB/s now.
Do you know if it will support choosing a fixed/specific throughput speed UoM?
I plan on updating and improving the integration and eventually, yes, this is something I want to add. Currently, I have to fix a couple of bugs first. So it will take time and I have to make sure that when I do this change, there is a smooth transition for existing users. For now, the fixed throughput unit is a working solution. If you need to convert the value you could do it manually e.g. with a template sensor.