Temperature reading from the wrong sensor

Bug Report

Summary

Affected module: sensors

Description: My output for sensors -u:

$ sensors -u    
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:
  temp1_input: 46.000
  temp1_max: 100.000
  temp1_crit: 100.000
  temp1_crit_alarm: 0.000
Core 0:
  temp2_input: 46.000
  temp2_max: 100.000
  temp2_crit: 100.000
  temp2_crit_alarm: 0.000
Core 1:
  temp3_input: 45.000
  temp3_max: 100.000
  temp3_crit: 100.000
  temp3_crit_alarm: 0.000

acpitz-virtual-0
Adapter: Virtual device
temp1:
  temp1_input: 44.000
  temp1_crit: 103.000

iwlwifi-virtual-0
Adapter: Virtual device
temp1:
  temp1_input: 44.000

pch_skylake-virtual-0
Adapter: Virtual device
temp1:
  temp1_input: 40.500

What is the current behaviour and what is the expected behaviour?

Instead of the Package id 0 temp1_input I see the temperature reported by the Virtual device adapter. I managed to fix this by changing the sensors call like this: sensors -u coretemp-isa-0000 but I don’t know if this is a viable solution for everyone. Maybe modifying the regex to look for ‘Package id 0’ would be more portable.

[cdarken]

Awesome, it works. Sorry for the noise, I didn’t read carefully the available parameters.

[tobi-wan-kenobi]

My bad, there was a bug in the module, which should now be fixed.

Actually, right now, the only thing you have to provide is the “match_pattern” (if you want to read “temp1_input”):

/bumblebee-status -m sensors -p sensors.match_pattern="Core 1"

This gets you the value of the next “temp1_input” that follows “Core 1”.