sensors display a value from another sensor

[bredita]

TLDR; It seems like any sensor with a single digit Label works. Any sensor with two or three digits in Label gets the value from the last digit in its label: Label 121 -> Value1 Label 112 -> Value2 etc

I think the problem is related to this, in sensor.ts:

FYI: The largest "index number" in my VSB registry folder is Label/Value169:

Long explanation:

I tried again, adding buttons for the core frequencies for all 16 cores, Renamed the sensors to Core # Clock (in case the perf numbers change over time). And the three "Physical Memory" values to "Physical RAM" to make registry search easier. Made sure no sensors are disabled. Added them in the plugin, and it looks like this.

(I basically got the same result with "Shared memory support" enabled and disabled. And with "Disable drive scan" enabled and SAS/SMART/ATA disabled.)

The 6 first cores show a clock speed. I think the correct one. core 7-9 shows the sensor values for "Physical memory used". core 10-15 seem OK, they show a clock speed, but I'm not sure...

The registry says:

HWINFO64/VSB folder in registry:

Label0 = Physical RAM Used Label1 = Physical RAM Available Label2 = Physical RAM Load Label3 = Core 0 Clock Label4 = Core 1 Clock Label5 = Core 2 Clock Label6 = Core 3 Clock Label7 = Core 4 Clock Label8 = Core 5 Clock Label9 = Core 6 Clock

Label10 = Core 7 Clock Label11 = Core 8 Clock Label12 = Core 9 clock Label13 = Core 10 clock

Label20 = Core 0 T1 Usage Label21 = Core 1 T0 Usage Label22 = Core 1 T1 Usage Label23 = Core 2 T0 Usage

Label120 = PMIC High Temperature DIMM 1 Label121 = PMIC Over Voltage DIMM 1 Label122 = PMIC Under Voltage DIMM 1 Label123 = SPD HUB Temperature DIMM 2

I suspect that all the ones that fail have more than one digit sensor Labels/Values: I added Label1-4 to my streamdeck, and any other sensor that has the same last digit to the right of it:

As you can see, all sensors with a label that ends in 0 show the same data. Same with the ones that end in 1, 2 and 3.

Other things I checked that probably are unimportant:

I installed the 8gadgetpack and the HWInfoMmonitor plugin (since this is the "reason" for adding the values to the registry, according to hwinfo documentation). Tried both version 1.1 and 2.0 of this 8gadgetpack plugin and they both require "Shared memory support" in HWinfo. They both work though.

Clocks folder in registry HWINFO64/VSB:

Clock6:

Clock7:

Clock8:

Clock9:

To me it looks like the data in the VSB folder is consistent?

Other registry entries that mention the same cores, probably nothing important here:

Clocks folders in HWINFO64/Sensors/E0002000_0:

Clock6:

Clock7:

(There is no clock 8-9 in this folder)

Clocks folders in HWINFO64/Sensors/F0000300_0:

Clock6:

Clock7:

Clock8:

Clock9:

(all clocks 0-15have an entry in this folder)

(HWINFO64/Sensors/F0000501_0 also have a couple of Clock folders, Clock37 and Clock64.)

I just noticed you published version 1.0.2, so I uninstalled 1.0.1 and tried 1.0.2, but it didn't fix this issue.

[5e]

You are completely right about the way of getting the index is wrong, no idea how I missed that, will fix this.

[5e]

Hi,

https://filebin.net/exctln3y5vechbtq/com.5e.hwinfo-reader.streamDeckPlugin

If you would like to give it a go, uninstall the plugin and let me know if this version now works @bredita

Else you can wait till Elgato pushes this update in a few days to the marketplace

[bredita]

Perfect. Thank you.

[bredita]

the one from pastebin works just fine now. Version number is still 1.0.2 according to the settings/plugins tab, guess that will update when elgato pushes it to the store?

[5e]

Yep, will be updated when it’s on sent to the store but just going to add 1 more thing to this update before shipping it