Custom user sensors in HWiNFO

[Fr0stX76]

Mm that is weird. I assume you had deleted the previously created lines from your registry?

At least it's an improvement, your Hotspot at 50.6c is I assume correct, so is your Junction temp at 48c. The issue seems to be with that the GPU temperature is creating a sensor named hotspot temp (but the temp would be correct at 38.5c, the lowest right?). Not sure why this is happening.

 

[SomeSmartGuy]

I played around a little more. No success :-( Then I deleted the complete HWInfo key from the registry, not only Custom.
After a restart it seems to work how it is intended. Not sure what it was but it works now. Thanks for your support.

kind regards

SomeSmartGuy

 

[Vamp]

Any one tried use ClockX? looks like this one not working properly, its always show only maximum and didnt changed:



Maybe I do something wrong but on others like temperature or voltage its working normally...

 

[abernitz]

UPDATE:
Since HWiNFO version 7.65, the following path is also supported: HKEY_LOCAL_MACHINE\Software\HWiNFO64\Sensors\Custom
but all custom sensors must reside either in HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE.

Unfortunately I still can't read anything from HKEY_LOCAL_MACHINE\Software\HWiNFO64\Sensors\Custom - is there a switch somewhere I have to use? I am on 7.72.

 

[Martin]

Unfortunately I still can't read anything from HKEY_LOCAL_MACHINE\Software\HWiNFO64\Sensors\Custom - is there a switch somewhere I have to use? I am on 7.72.

You're not supposed to read values from those keys, it's HWiNFO that reads them when they are populated by user/other apps.

 

[abernitz]

You're not supposed to read values from those keys, it's HWiNFO that reads them when they are populated by user/other apps.

Thanks, there was a misunderstanding. Got it now.

 

[dainar]

Any one tried use ClockX? looks like this one not working properly, its always show only maximum and didnt changed:

View attachment 10657

Maybe I do something wrong but on others like temperature or voltage its working normally...

I has the same issue. In fact the data in all columns appears shortly, but then it is zeroed.

 

[cyp0633]

Any one tried use ClockX? looks like this one not working properly, its always show only maximum and didnt changed:

View attachment 10657

Maybe I do something wrong but on others like temperature or voltage its working normally...

TLDR: switch to English interface until the problem gets fixed.
This seems to be a localization related problem. The labels may be automatically translated to your localization after startup. For example, when set to zh-CN, "E-core 5 Clock" is translated to "E-core 5 频率" (the labels can be seen by going to sensor settings -> customize -> label, as the picture I posted). The label we referred in Windows registry might corresponds to "E-core 5 频率" (current, localized version), so if you type in "E-core 5 Clock" (original, English version) HWiNFO64 may not be read after the localization is applied, and thus get only one value.

 

[Banel0]

Just a quick report: storing the custom sensors in HKEY_LOCAL_MACHINE\Software\HWiNFO64\Sensors\Custom if all the actual sensor data are in HKEY_CURRENT_USER\Software\HWiNFO64\Sensors doesn't appear to work (the sensor entry is created within HWiNFO but the readings are not listed). It worked just fine when i moved them from HKEY_LOCAL_MACHINE to HKEY_CURRENT_USER. As per the first post, it seems that you can chose either one as long as all the custom ones are in the same place, but it appears that both custom and default need to share the parent path. HWiNFO64 v8.10-5520.

On a different note, now i know you already stated that only number-based values are to be supported, but I wonder if it would be possible to leverage the Unit value so that string data can also be displayed? It would only be required the unit field to also be updated during polling, whereas now the Unit string only gets read once and not updated ever. Do you think that would be possible? I'm trying to find a way to add the top CPU process name to the data monitored and it seems that leveraging the custom sensor support is the only way to do that.

 

[Black_Phillip]

This is great. Very simple for us noobs.
Even I who do not know much about programming managed to get some sensors going with help of cheat engine + chatgpt.