[FEATURE] View Node temperature

[HarshitBhatt043]

Describe the solution you'd like
Users can install lm-sensors on their nodes and check their node temp using sensors command , it would be beneficial if we can get the highest temp or Package id 0 temp in the web ui.
Below is an output of sensors command
`Adapter: Virtual device
temp1: +26.0°C
temp2: +35.0°C
temp3: +29.0°C
temp4: +29.0°C
temp5: +32.0°C
temp6: +30.0°C

acpitz-acpi-0
Adapter: ACPI interface
temp1: +16.8°C
temp2: +16.8°C
temp3: +27.8°C

coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +30.0°C (high = +84.0°C, crit = +100.0°C)
Core 0: +28.0°C (high = +84.0°C, crit = +100.0°C)
Core 1: +28.0°C (high = +84.0°C, crit = +100.0°C)
Core 2: +31.0°C (high = +84.0°C, crit = +100.0°C)
Core 3: +26.0°C (high = +84.0°C, crit = +100.0°C)
Core 4: +27.0°C (high = +84.0°C, crit = +100.0°C)
Core 5: +26.0°C (high = +84.0°C, crit = +100.0°C)

nvme-pci-0400
Adapter: PCI adapter
Composite: +31.9°C (low = -0.1°C, high = +69.8°C)
(crit = +84.8°C)
Sensor 1: +49.9°C (low = +0.0°C, high = +0.0°C)`
We can also get nvme temps if we want.

Describe alternatives you've considered
i have tried https://github.com/henrygd/beszel , but its using agents to get all the info, same with others like netdata.

[rcourtman]

Hi @HarshitBhatt043,

Thanks for the feature request! Temperature monitoring is definitely something I've heard requested from multiple users, so it's on my radar.

It's not on my immediate to-do list, but I will look into implementing this in the near future. I'll need to research the best way to retrieve temperature data from Proxmox nodes reliably.

I'll update this issue when I start working on it.

[martusi61]

I agree about the importance of temperature values to monitor, this feature would make the package very complete. Thanks for the work done now.

[rcourtman]

Closing as stale. This feature request is from 6+ months ago. Feel free to reopen if you still want node temperature monitoring added to v4.

[rcourtman]

Reopening

[krom]

Proxmox does not provide this functionality in its basic form, but there is a project that allows you to display additional information in the web interface. Please take a look, maybe you can reuse it. I'm not sure that data is added to the REST API, but maybe it's worth taking as a basis. Otherwise, you will need to install additional software on the server.

[kenrmayfield]

@rcourtman
@krom

That Project for PVE-MODs(https://github.com/Meliox/PVE-mods) is a Excellent Repository.

I suggest it All the Time to Users whom want that Information in the Proxmox DashBoard.

Like krom stated.............the User will have to Install the Repo on their End as a PreRequisite and Pulse can Pull the Temperature and Fan Speed Data through REST API or maybe there is Another Method to Pull the Temperature Data and Fan Speed Data without Installing the PVE-MODs Repo by Strictly using Code Directly in Pulse that Directly accesses lm-sensors.

[rcourtman]

thanks for the discussion everyone. i've been thinking about this and here's my take:

modifying proxmox with pve-mods isn't sustainable - it breaks on updates and requires users to hack their systems. not ideal.

i'm considering a simpler approach:

1. use the existing api credentials to ssh into nodes
2. run sensors -j or read /sys/class/thermal/ directly
3. parse and display the temps in pulse

this would work with stock proxmox, no modifications needed. if sensors aren't installed or available, we just don't show temps for that node.

would this work for everyone's use case? main requirement would be that the pulse user has ssh access (which the auto-setup script could configure).

thoughts?

[rcourtman]

for those not familiar with the auto-setup script (it's a newer feature):

how it works:

1. go to Settings → Nodes in pulse
2. click "Setup Script" next to any discovered node
3. pulse generates a one-liner bash script
4. run it on your proxmox node (as root)

what the script does:

• creates a dedicated user (pulse-monitor@pam)
• assigns minimal required permissions (PVEAuditor role)
• generates an api token for that user
• registers the token with pulse automatically
• optionally enables ssh for the pulse-monitor user (for features like temperature monitoring)

security:

• the pulse-monitor user has READ-ONLY permissions
• can't modify vms, containers, or settings
• can't access vm consoles or data
• only gets monitoring metrics
• ssh access (if enabled) is restricted to the pulse-monitor user, not root

why this matters for temperature monitoring:
if we implement temp monitoring via ssh, the auto-setup script could handle configuring ssh access for the pulse-monitor user automatically. no manual ssh key setup needed.

the script is transparent - you can read it before running. it's basically automating what you'd do manually but with consistent security settings.

[kenrmayfield]

@rcourtman

Your Comment..........................
modifying proxmox with pve-mods isn't sustainable - it breaks on updates and requires users to hack their systems. not ideal.
..................................

Technically Yes on Updates to Proxmox you would have to Reinstall. The PVE-MODs Script Inserts Code into pvemanager.js and nodes.pm Files. The Original Files get Backed Up by the Script.

[tim-rex]

Personally, I don't love the idea of allowing/requiring direct ssh into any PVE nodes.. Ideally we would petition upstream Proxmox to expose sensors -j or /sys/class/thermal directly via their API though I appreciate that might be a non-starter