Hwmon sensors info drowned in irrelevant data

[goc9000]

Description

(This continues the discussion I started in another issue as this one is related, but nevertheless separate)

On my machine at least, the sensors display is unusable when selecting the hwmon source. An enormous number of sensors is reported, and there is too much data to fit on screen, but in fact most of the values are not sensors at all and should be organized differently.

I've included screenshots and some specific observations:

• Note how the IT8688 chip has 124(!) "sensors" but in fact most of these are constants ("Temp Min", "Fan Min", "Fan Beep") that are of secondary importance and should not take up space in the main display. As it is, the display for 124 values is unparseable and doesn't even fit on screen.

• For the NZXT Smart Device source, note how space is taken up by PWM "sensors" that are either of super low importance (PWM values) or control values that are not sensors at all (enable, mode)

• For the NVME source, note again how most of the space is taken up by thresholds which are not very informative anyway (absolute zero, 65000 degrees etc). Only the three "Input" values are actually useful.

• As an aside, the topmost level only shows a summary of sensory sources and the number of sensors within. One has to hover over the sources to get the actual sensor values. I think it would be more useful to somehow have the sensor values from all sources in one single display, with the sources displayed as headings. It's the sensor values themselves that are of interest, after all, the sources are just means to an end.

Steps to Reproduce

1. Have a recent machine with a decent number of sensors accessible by Linux (e.g. about 6-10 temperature sensors and 4-5 fan sensors is typical).
2. Configure 'hwmon' as a sensors source
3. Enable the sensors icon and hover over it to see the info

Screenshots

Environment

• Astra Monitor Version: 26 (EGOv43)
• GNOME Version: 46
• Operating System and Version: Ubuntu 24.04
• Other Relevant System Information: -

[ljuzig]

I added a way to filter sensors with regex. While this does not really fix this bug, it might help to alleviate the problem in the meantime. The optimal solution requires a lot of work, and I do not think it is feasible at the present time.

This is before filtering:

The regex I added:

The result:

This will be available in the next release. I keep this issue open until the issue is resolved with a final and better solution.