The Xwidget program cannot obtain temperatures from the o/s by itself as the temperatures are NOT provided by the o/s.
Speedfan only provides the temperature data for a set number of sensors without naming or identifying the sensors properly. Therefore you don't know whether sensor 1 is the CPU core sensor or the ambient temperature sensor. This is why the information as presented by Xwidget is so vague (temp1, temp2, temp &c).
Coretemp has been around for a while now and it has been suggested that it is a bit long in the tooth and not being actively developed so newer motherboards/devices may not be supported.
That leaves us with Open Hardware Monitor which is a much better tool and uses the Windows Management Instrumentation (WMI) layer to provide the information in a more structured way. We can just hope that Tony will write a new core for OHM that will allow widgets access to all the sensor information for all devices without having to write the WMI code in javascript to access the WMI data independently.
Alternatively, provide the community with the APIs or information that is needed for a core to interface to Xwidget and we could write a core to do same. The C code exists to extract information from WMI, all we need to know is how to present that data to Xwidget.Statistics: Posted by yereverluvinuncleber — March 16th, 2016, 5:06 am
]]>