[GH-ISSUE #536] Switching to LibreHardwareMonitor for more support ? #489

New issue

Closed

opened 2026-02-26 00:32:47 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 00:32:47 +03:00

Owner

Originally created by @dan-and on GitHub (Aug 14, 2018).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/536

Hi @hirschmann,

Have you thought about switch to https://github.com/LibreHardwareMonitor/LibreHardwareMonitor ?
It would allow much more support on CPUs (i.e. AMD Ryzen) and is far more active in development.

We are nearly before getting a Config for the Ryzen based Envy X360, but we are missing the cpu temperature support.

Originally created by @dan-and on GitHub (Aug 14, 2018). Original GitHub issue: https://github.com/hirschmann/nbfc/issues/536 Hi @hirschmann, Have you thought about switch to https://github.com/LibreHardwareMonitor/LibreHardwareMonitor ? It would allow much more support on CPUs (i.e. AMD Ryzen) and is far more active in development. We are nearly before getting a Config for the Ryzen based Envy X360, but we are missing the cpu temperature support.

kerem

2026-02-26 00:32:47 +03:00

closed this issue
added the
enhancement

Stale
labels

kerem commented

2026-02-26 00:32:48 +03:00

Author

Owner

@hirschmann commented on GitHub (Aug 14, 2018):

Yes, I have actually planned to switch to LibreHardwareMonitor as base for NBFC plugins for Windows.
I just haven't had enough time yet to port some of the changes I made to my fork of OHM back to LHM.

@hirschmann commented on GitHub (Aug 14, 2018): Yes, I have actually planned to switch to LibreHardwareMonitor as base for NBFC plugins for Windows. I just haven't had enough time yet to port some of the changes I made to my fork of OHM back to LHM.

kerem commented

2026-02-26 00:32:48 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 24, 2019):

This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed

@github-actions[bot] commented on GitHub (Nov 24, 2019): This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed