Temperature doesn't support tempN properly #17

Closed
divansantana opened this Issue May 28, 2014 · 4 comments

Projects

None yet

2 participants

@divansantana

Hi,

Firstly this is awesome so thank you.

Secondly, I think the temperature component is not working correctly.
By default it's set to:
[temp: $temp0°C]

However on my system I need it set to temp1 as temp0 doesn't exist:

# /usr/bin/sensors -u    
asus-isa-0000
Adapter: ISA adapter
temp1:
  temp1_input: 48.000

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:
  temp1_input: 50.000
  temp1_max: 100.000
  temp1_crit: 100.000
  temp1_crit_alarm: 0.000
Core 0:
  temp2_input: 50.000
  temp2_max: 100.000
  temp2_crit: 100.000
  temp2_crit_alarm: 0.000
Core 1:
  temp3_input: 48.000
  temp3_max: 100.000
  temp3_crit: 100.000
  temp3_crit_alarm: 0.000

When I set it to

[temp: $temp1°C]

It literally displays

[temp: $temp1°C]

Instead of converting $temp1 to a variable as expected.

@arcan1s
Owner
arcan1s commented May 28, 2014

No, it is not. Numbering of elements of temperature, hdd usage, hdd speed, hdd temperature refers to elements from second tab (advanced settings). You should add item to the required listWidget (temperature device in your case) first. And the first element in the listWidget will be $temp0.

In my case (see the attached screenshot) Physical_id_0 is $temp0 and temp1 is $temp1.
screenshot
And here is my sensors -u:

thinkpad-isa-0000
Adapter: ISA adapter
fan1:
  fan1_input: 0.000

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:
  temp1_input: 57.000
  temp1_max: 86.000
  temp1_crit: 100.000
  temp1_crit_alarm: 0.000
Core 0:
  temp2_input: 57.000
  temp2_max: 86.000
  temp2_crit: 100.000
  temp2_crit_alarm: 0.000
Core 1:
  temp3_input: 57.000
  temp3_max: 86.000
  temp3_crit: 100.000
  temp3_crit_alarm: 0.000
@arcan1s arcan1s added the question label May 28, 2014
@arcan1s arcan1s self-assigned this May 28, 2014
@arcan1s
Owner
arcan1s commented May 28, 2014

hm, I think it should be added to the README

@divansantana

Oh dear, it works just fine as per your comment.
Thanks for the feedback and apologies.
I looked (too) briefly on the site and should have definitely looked into it more before reporting an issue.
Github makes things a little too easy to complain ;)

@arcan1s
Owner
arcan1s commented May 28, 2014

Don't worry about it. Some things in my applications really are not obvious =) And that's why there is a special label for issues (question).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment