Bug 394130

Summary:	Minimum/maximum values for custom command sensors do not work
Product:	[Unmaintained] ksysguard	Reporter:	Frederick Zhang <frederick888>
Component:	general	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	frederick888
Priority:	NOR
Version First Reported In:	5.12.5
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	nvidia sensor script

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.