[c0m4r]

Temperatures monitoring will be added. Initially, I implemented too many metrics, so during development I limited them to a reasonable level to make them manageable, but I'll be adding more as the project matures. Thanks for the feedback!

[atmanactive]

Looking forward, thanks!

[c0m4r]

If you have a moment, I would be grateful if you could create an issue on github. I will then be able to let you know when it's ready and ask you to try it out. Please also let me know which temperatures you'd like to primarily monitor. I assume I'll have to gradually introduce the supported ones, as not all of them can be detected at once.

[atmanactive]

Sure thing. In my experiences based on using LibreHardwareMonitor [1] on Windows, and Dunnart [2] on Linux, dealing with temperature monitoring is not trivial. But it's not impossible either. For example, in Linux, looking at /sys folder for CPU temperatures, I can often find several entries, of which, some are dead, some are way off, and some are correct, but it is always a hit and miss endeavour. So, reliably monitoring temperatures requires a bit of an algorithm to detect the right source.

[1] https://github.com/LibreHardwareMonitor/LibreHardwareMonitor

[2] https://github.com/warthog618/dunnart

[c0m4r]

That's true, which is why I assume I'll have to gradually implement this feature. It probably won't be perfect, but it's worth trying :)

Thank you for opening the issue!

[smashed]

Most (all?) temperature monitoring tools on Linux rely on libsensors.

Seems like hardware maintainers never could agree on a standard way of exposing temperature on Linux.

[c0m4r]

Yeah, that's a pain. Every time I boot up new hardware, I wonder how many readings I'll be able to get this time, and if it's even possible. On one computer, I have practically all the temperatures, voltages, and fan speeds, while on another, I can barely read the CPU temperature alone. Not to mention the need to sometimes compile sketchy drivers from github...