HTPCInfo plugin v1.15.0 for MediaPortal 1.3.0 and higher (1 Viewer)

[nicsergio]

Hi @nicsergio
Im using the Titan Skin. Ok the files for HTPCInfo need a little adjustments in terms of size and position but other than that its fine. Yea Speedfan is giving me the correct temperatures. Hardwaremonitor however doesnt.

I have attached the screenshots...
View attachment 122455 View attachment 122456 View attachment 122457

It's simple:
the name of the property that HtpcInfo makes available in the skin is made ​​up of

#HTPCInfo.SensorTemperature followed by the name that you set in the configuration page of the sensors, where you put Temp1/Temp2/Temp3

then becomes #HTPCInfo.SensorTemperatureTemp1 for the first sensor

the same way as the fan speed are made
#HTPCInfo.SensorFan << Name set

and the measured voltages
#HTPCInfo.SensorVoltage << Name set

this because the flag "build skin property from related sensor name" is set..

In the Titan skin, from what I see, the names of the properties displayed for the temperatures are:
#HTPCInfo.SensorTemperatureCPU
#HTPCInfo.SensorTemperatureSystem

so if imposed instead of Temp1 and Temp2, CPU and System names (in the correct order) should display..
also as sensor provider should select SpeedFan

bye!

 

[niutachy]

Hi @nicsergio,

thanks for your quick response. So i switched the Sensor Provider to speedfan, should have noticed that before. I removed the flag for building skin property and adjusted the skin file HTPCInfoGauges.xml for testing
#HTPCInfo.SensorTemperatureCPU -->#HTPCInfo.SensorTemperatureTemp1



However the result is still not showing up in Mediaportal. Also i still cant get the diagnostic tool to run.

bye

 

[nicsergio]

In this case you have to keep active flag "build skin property from related sensor name", otherwise, as explained in the documentation (Chapter 5) the name of the properties exposed by the plugin becomes:

#HTPCInfo.SensorTemperature0, #HTPCInfo.SensorTemperature1, ...

bye

 

[niutachy]

Great it worked.
Thanks for your help.

bye

 

[Micropolis]

Dear community,
please find at the first post of this thread release candidate 1 of HTPCInfo v1.7.0.
Main goal of this release was the support and integration of the processor monitor CoreTemp (see http://www.alcpu.com/CoreTemp).

Cheers and happy testing, Micropolis

 

[Game_dude]

Hmm trying to get RC1 working with MP 1.3 RC and after copying everything to the correct folders I get this error

---------------------------
MediaPortal
---------------------------
TvPlugin and MediaPortal don't have the same version.
 
Please update the older component to the same version as the newer one.
 
MpConfig Version: 1.2.300.0
 
TvPlugin Version: 1.2.100.0
---------------------------
OK 
---------------------------

 

[Micropolis]

Hello Game_dude,
I do not understand why the same questions must be asked again and again.

... after copying everything ...

What means "everything"? When the error occurs? Do you have changed anything regarding your installed MediaPortal RC 1.3.0 TV libraries?
HTPCInfo v1.7.0RC is compiled against MediaPortal v1.2.0 system libraries, but will work with newer versions completely. The installer does not replace or change MediaPortal system libraries, all my test systems (v1.2.0, v1.3.0beta and v1.3.0RC) runs without any problems.

Micropolis

 

[Game_dude]

Nah, I haven't changed anything. Though I don't use live tv with Mediaportal if that helps?

 

[Micropolis]

Dear community,
as part of the easter rollout of my plugin collection please find version 1.7.0 of HTPCInfo at the first post of this thread and in our plugin repository.

Personal note: Due to the expected workload in the next month and lack of time I feel compelled to reduce the plugin development to a minimum. I'm not sure when I'll have the time again, but I assure that the plugins are not dead and showstopper problems will be fixed in a timely manner. I ask for proper understanding and thank everyone for the many years of support.

Cheers and see you soon as possible, Micropolis

 

[fischy667]

Hi, thanks for your great work.

But after the update to HTPC 1.7 the parameter #HTPCInfo.MemoryPercentUsed gives me a strange valvue. See picture (second line 33.9...)

The same with #HTPCInfo.MemoryPercentAvailable.

The values ​​show too many numbers after the decimal sign.