JakeStanger/ironbar

Fork 0

mirror of https://github.com/JakeStanger/ironbar.git synced 2026-07-11 06:15:21 +01:00

[GH-ISSUE #1090] Sys_info: Temperature sensor no longer reporting value #3150

New issue

Closed

opened 2026-05-22 23:54:17 +01:00 by JakeStanger · 8 comments

JakeStanger commented

2026-05-22 23:54:17 +01:00

Owner

Originally created by @ItsLemmy on GitHub (Jul 15, 2025).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1090

Describe the bug
My bar is now reporting 0° celsius for my CPU since I updated ironbar on 2025-07-14

To reproduce
Steps to reproduce the behavior:

Add module type sys_info
Set a valid format for the sensor, ex: "format": [" {temp_c@AMD TSI Addr 98h°"]
Observe that the value is always zero/null

Expected behavior
Module should report the temperature properly.

System information:

Distro: Arch Linux
Compositor: Niri
Ironbar version: ironbar 0.16.1 - git 622ca3cc4f

Configuration

Config

Using chezmoi for templating

      {
        "type": "sys_info",
        "interval": {
          "memory": 30,
          "temps": 5
        },
        "format": [" {temp_c@{{ .cpu_thermal_sensor }}}°", "  {memory_percent:<1.0}%"]
      },

Styles

Additional context

Screenshots

Originally created by @ItsLemmy on GitHub (Jul 15, 2025). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1090 **Describe the bug** My bar is now reporting 0° celsius for my CPU since I updated ironbar on 2025-07-14 **To reproduce** Steps to reproduce the behavior: 1. Add module type `sys_info` 2. Set a valid format for the sensor, ex: "format": [" {temp_c@AMD TSI Addr 98h°"] 3. Observe that the value is always zero/null **Expected behavior** Module should report the temperature properly. **System information:** - Distro: Arch Linux - Compositor: Niri - Ironbar version: ironbar 0.16.1 - git 622ca3cc4f3494d35b0e189d57b2a4f7cffb8e6c **Configuration**  <details><summary>Config</summary> Using chezmoi for templating { "type": "sys_info", "interval": { "memory": 30, "temps": 5 }, "format": [" {temp_c@{{ .cpu_thermal_sensor }}}°", " {memory_percent:<1.0}%"] }, </details> <details><summary>Styles</summary> ```css ``` </details> **Additional context**  **Screenshots**

JakeStanger

2026-05-22 23:54:17 +01:00

closed this issue
added the
A:Documentation

M:SysInfo
labels

JakeStanger commented

2026-05-22 23:54:18 +01:00

Author

Owner

@quietvoid commented on GitHub (Jul 15, 2025):

Getting the same here.

{temp_c@CPU}°C "

@quietvoid commented on GitHub (Jul 15, 2025): Getting the same here. ```" {temp_c@CPU}°C " ```

JakeStanger commented

2026-05-22 23:54:18 +01:00

Author

Owner

@JakeStanger commented on GitHub (Jul 15, 2025):

I'm assuming this did it: https://github.com/JakeStanger/ironbar/pull/1085

You should be able to query the values from the sys_info module, as they're now set as internal ironvars. If you try and explore the values using list and get, what are you seeing?

ironbar var list sysinfo.temp_c

@JakeStanger commented on GitHub (Jul 15, 2025): I'm assuming this did it: https://github.com/JakeStanger/ironbar/pull/1085 You should be able to query the values from the `sys_info` module, as they're now set as internal ironvars. If you try and explore the values using `list` and `get`, what are you seeing? ```shell ironbar var list sysinfo.temp_c ```

JakeStanger commented

2026-05-22 23:54:18 +01:00

Author

Owner

@quietvoid commented on GitHub (Jul 15, 2025):

ironbar var list sysinfo.temp_c

amdgpu edge: 41
amdgpu junction: 47
amdgpu mem: 42
asusec CPU: 50
asusec Chipset: 38
asusec Motherboard: 25
asusec T_Sensor: -40
asusec VRM: 20
k10temp Tccd1: 38.75
k10temp Tccd2: 34.5
k10temp Tctl: 49.375
max: 50
mean: 31.87291653951009
min: -40
nvme Composite WDS500G3X0C-00SJG0: 36.849998474121094
sum: 382.4749984741211

Changing to asusec CPU works for me.

@quietvoid commented on GitHub (Jul 15, 2025): ``` ironbar var list sysinfo.temp_c amdgpu edge: 41 amdgpu junction: 47 amdgpu mem: 42 asusec CPU: 50 asusec Chipset: 38 asusec Motherboard: 25 asusec T_Sensor: -40 asusec VRM: 20 k10temp Tccd1: 38.75 k10temp Tccd2: 34.5 k10temp Tctl: 49.375 max: 50 mean: 31.87291653951009 min: -40 nvme Composite WDS500G3X0C-00SJG0: 36.849998474121094 sum: 382.4749984741211 ``` Changing to `asusec CPU` works for me.

JakeStanger commented

2026-05-22 23:54:18 +01:00

Author

Owner

@ItsLemmy commented on GitHub (Jul 15, 2025):

Works for me two, thanks. I guess the Wiki should be updated.

@ItsLemmy commented on GitHub (Jul 15, 2025): Works for me two, thanks. I guess the Wiki should be updated.

JakeStanger commented

2026-05-22 23:54:18 +01:00

Author

Owner

@JakeStanger commented on GitHub (Jul 15, 2025):

Cool that's good news. Are you both on AMD CPUs?

@JakeStanger commented on GitHub (Jul 15, 2025): Cool that's good news. Are you both on AMD CPUs?

JakeStanger commented

2026-05-22 23:54:18 +01:00

Author

Owner

@ItsLemmy commented on GitHub (Jul 15, 2025):

Yes, I run a 9950X.
Sensor name changed from "AMD TSI Addr 98h" to "nct6687 AMD TSI Addr 98h"

amdgpu edge: 42
amdgpu junction: 49
amdgpu mem: 68
k10temp Tctl: 56.75
max: 68
mean: 49.791175842285156
min: 37.25
nct6687 AMD TSI Addr 98h: 55
nct6687 Diode 0 (curr): 52
nct6687 Thermistor 15: 46
nct6687 Thermistor 1: 51.5
nvme Composite CT500P1SSD8: 45.849998474121094
nvme Composite Samsung SSD 990 PRO 1TB: 44.849998474121094
nvme Sensor 1 CT500P1SSD8: 47.849998474121094
nvme Sensor 1 Samsung SSD 990 PRO 1TB: 44.849998474121094
nvme Sensor 2 CT500P1SSD8: 43.849998474121094
nvme Sensor 2 Samsung SSD 990 PRO 1TB: 52.849998474121094
nvme Sensor 5 CT500P1SSD8: 60.849998474121094
r8169_0_a00:00 temp1: 48
spd5118 temp1: 37.25
sum: 846.4499893188477

@ItsLemmy commented on GitHub (Jul 15, 2025): Yes, I run a 9950X. Sensor name changed from "AMD TSI Addr 98h" to "nct6687 AMD TSI Addr 98h" ``` amdgpu edge: 42 amdgpu junction: 49 amdgpu mem: 68 k10temp Tctl: 56.75 max: 68 mean: 49.791175842285156 min: 37.25 nct6687 AMD TSI Addr 98h: 55 nct6687 Diode 0 (curr): 52 nct6687 Thermistor 15: 46 nct6687 Thermistor 1: 51.5 nvme Composite CT500P1SSD8: 45.849998474121094 nvme Composite Samsung SSD 990 PRO 1TB: 44.849998474121094 nvme Sensor 1 CT500P1SSD8: 47.849998474121094 nvme Sensor 1 Samsung SSD 990 PRO 1TB: 44.849998474121094 nvme Sensor 2 CT500P1SSD8: 43.849998474121094 nvme Sensor 2 Samsung SSD 990 PRO 1TB: 52.849998474121094 nvme Sensor 5 CT500P1SSD8: 60.849998474121094 r8169_0_a00:00 temp1: 48 spd5118 temp1: 37.25 sum: 846.4499893188477 ```

JakeStanger commented

2026-05-22 23:54:18 +01:00

Author

Owner

@quietvoid commented on GitHub (Jul 15, 2025):

5900X here on an ASUS X470 Prime Pro mobo.

@quietvoid commented on GitHub (Jul 15, 2025): 5900X here on an ASUS X470 Prime Pro mobo.

JakeStanger commented

2026-05-22 23:54:18 +01:00

Author

Owner

@JakeStanger commented on GitHub (Jul 15, 2025):

Man those are some ugly sensor names. I'll try and make sense of them to get the wiki updated with a more comprehensive list, but I think for reference:

k10temp Tctl is the AMD CPU internal sensor
asusec CPU and nct6687 AMD ... are the motherboard chipset sensors

k10temp generally seems a more stable option, but it depends on whether that's what you want.

@JakeStanger commented on GitHub (Jul 15, 2025): Man those are some ugly sensor names. I'll try and make sense of them to get the wiki updated with a more comprehensive list, but I think for reference: - `k10temp Tctl` is the AMD CPU internal sensor - `asusec CPU` and `nct6687 AMD ...` are the motherboard chipset sensors `k10temp` generally seems a more stable option, but it depends on whether that's what you want.