Bug 394130 - Minimum/maximum values for custom command sensors do not work
Summary: Minimum/maximum values for custom command sensors do not work
Status: RESOLVED NOT A BUG
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: general (show other bugs)
Version: 5.12.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-11 14:16 UTC by Frederick Zhang
Modified: 2022-11-21 11:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
nvidia sensor script (1.75 KB, application/x-perl)
2018-05-11 14:16 UTC, Frederick Zhang
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frederick Zhang 2018-05-11 14:16:30 UTC
Created attachment 112578 [details]
nvidia sensor script

I'm trying to improve https://gist.github.com/frantic1048/41f56fd6328fa83ce6ad5acb3a4c0336 so that it can show minimum/maximum values and units in Ksysguard.

According to https://techbase.kde.org/Development/Tutorials/Sensors, the info command should have the format of `Display Name of the sensor TAB minimum value TAB maximum value TAB units NEWLINE` so I tried modifying the memory line to `print "gpu_memory\t0\t$totalMemory\tinteger\n";`

But this simply makes it disappear from Ksysguard.

How to correctly set minimum/maximum values of a sensor? And what are the available "units" (I'd like to show "MiB" for GPU memory and °C for temperatures)?
Comment 1 Justin Zobel 2022-11-21 08:21:41 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Frederick Zhang 2022-11-21 11:24:09 UTC
I think I mixed up 'monitors' (typo in documentation? it should be plural) command and 'info' command back then.

And I now actually use https://gist.github.com/fonic/8f38e5e3ce5c8693ae3a23aa1af21fb9 which only reports min/max/unit through 'sensor_name?' metadata commands and it works flawlessly.