Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Rainmeter plug-in for HWiNFO 3.1
Version 3 of the HWiNFO plug-in for Rainmeter is now available and can be downloaded from here:

3.1.0 - March 6, 2016
details here

3.0.0 - January 1, 2016

Please Note: Version 2.0 of this plugin has a dependence on the Visual C++ 2013 runtime libraries.  These are no longer being distributed with Rainmeter as of version 3.3.  Therefore, if you do not have these runtime libraries already installed on your PC, v2.0 of this plugin will error.  Updating to 3.0 will resolve this issue.

What's New
  • Added support for remote system monitoring introduced in HWiNFO 5.0
  • Updated to the latest versions: HWiNFO 5.10, Rainmeter 3.3 and Visual Studio 2015
  • Updated so VC++ runtime libraries are no longer required
To use this plugin, you need to ensure HWiNFO's sensors are running and "Shared Memory Support" is enabled in the HWiNFO settings.

To install the skin, simply run the downloaded .rmskin file. You should be presented with the following:
[Image: skin-example-v3.png]
Please Note: This included skin does not demonstrate the full capabilities of HWiNFO and this plugin. It is included simply to demonstrate how to use this plugin.

If you will continue to use the included skin (or create one based on this), then you must check the measure IDs included with the skin against the IDs for your hardware. It is possible the values on your PC do not match the ones in the skin. The IDs can be updated in the skin by editing the "Documents\Rainmeter\Skins\HWiNFO\@Resources\" file using a text editor. Then replace the IDs with the matching IDs for your hardware.

Creating Rainmeter Measures
Please read the instructions for creating measures in this post:

In addition, version 3 now includes the ability to add monitoring of remote systems into your Rainmeter skins.  To do so, you will use the optional HWiNFOHostId parameter. If you do not provide this parameter, the skin will continue to return the values from the local machine. 

The sample skin above shows 3 graphs (CPU and dual GPUs) from the local machine, as well as CPU & GPU from two other PCs on the LAN using the new remote monitoring feature.

First, you must configure additional machines to monitor in the HWiNFO settings.  There is a good tutorial for this here:

Then we can  specify which remote machine to connect to by running the included HWiNFOSharedMemoryViewer.exe file.  This application has been updated to include a dropdown of remote machines configured in HWiNFO during the previous step.  Selecting a remote machine will provide the id you need to provide to this parameter to query that specific machine.

[Image: remote-host-example.png]

For example, to query the CPU usage on the local machine, we would use a measure like this:


To return the CPU usage of a remote system, we would also include the Remote Host ID as the HWiNFOHostId parameter:


More information about creating skins, measures and meters:

Skin Authors: The plugin is included in the "Documents\Rainmeter\Skins\HWiNFO\@Resources\RedistrutablePlugin" folder. Feel free to use it in your own works. If you create a skin that you think others may want to use, kindly mention it in this forum.

If you have any questions or issues, please let me know.

A great New Year's update Smile Thanks Nick !
This plugin has been updated to version 3.1 to include more granular reported feedback about skin configuration and other related errors.  This allows skin authors to take actions based on results returned, and helps users determine the problem with the skin so it can easily be corrected.
You can download version 3.1 here

There are no changes to the demo skin, only the plugin.  If you are already using this skin, you can run the 3.1 installer and just select the option to update the plugin.  Skin authors will want to install the complete skin in order to gain access to the updated .dll files in the @Resources folder.

When Rainmeter skins can not communicate with HWiNFO properly, or there are configuration issues in the skins, specific error codes will now be returned direct to the skin.  This allows the user to quickly see what the issue is so corrections can be made.

Here is an example of a skin that is having issues returning good data:
[Image: errors.png]

Measures that are querying a string value from HWiNFO will return an appropriate error string now instead of just no value.  An example above is "HWI_ERROR_INVALID_SENSOR_ID".  Measures that return a number will now return an error specific code in the -9000 to -9999 range instead of 0.  These codes can be used to determine the specific error for those measures.  Above you can see that -9201, -9200 and -9102 are all being returned.

Once all errors are corrected, the skin would now look like this again:
[Image: good.png]

The list of error conditions are below.  The number and error name on the same line are identical.  Which one that is returned just depends on the measure type.


Logging has been enhanced to provide more information that is more accurate.  You can find this information in the Rainmeter->About dialog on the log tab.  These entries are only written when a skin is refreshed (not in real-time).  This includes when the skin is loaded, as well as when the skin is refreshed.  So for example, if one of your measures is returning -9001 and you don't exactly know what that means, simply refresh the skin and look at the log.  In this case it would correlate to the top line (remote host 0 is not reachable).  In general, log entries of type 'Error' have an issue which prevents the skin from functioning entirely (for example, HWiNFO is not running).  Entries of type 'Warning' indicate the issue is isolated to the specific measure, and the skin should otherwise function for measures with a good configuration.  Here is an example of the updated log output:
[Image: about-dialog.png]

Rainmeter also shows measure values on the Skins tab.  These are now displaying specific results as well.  Therefore, you can easily get a centralized list of all the issues.  In the example below, you can see that there are several text and several number measures with configuration problems.  Looking in the "Value" column, the first 5 entries are good, but the rest all have configuration issues.
[Image: measures.png]

Please let me know if you have any questions or issues.

- Nick

Forum Jump:

Users browsing this thread: 1 Guest(s)