meliox / pve-mods Goto Github PK

I attempted to install this by by using the instructions given:

apt-get install lm-sensors
wget https://github.com/Meliox/PVE-mods/blob/main/pve-mod-gui-temp.sh

but this just returned an error from bash:

pve-mod-gui-temp.sh: line 1: unexpected EOF while looking for matching `)'
pve-mod-gui-temp.sh: line 2: syntax error: unexpected end of file

To correct this I did the following:

1. Deleted the download .sh file (rm pve-mod-gui-temp.sh)
2. Created new file (touch pve-mod-gui-temp.sh)
3. Opened this file (nano pve-mod-gui-temp.sh)
4. Copied the script from git's raw view of the code and pasted into nano
5. Saved the file and exited (CTRL-X)

I was then able to successfully execute the script with

pve-mod-gui-temp.sh install

Not sure if anyone else ever came across this, but maybe a change in the wget command to this may work better:

https://raw.githubusercontent.com/Meliox/PVE-mods/main/pve-mod-gui-temp.sh

Does this script work on the new Proxmox version 8?

How do you go about reverting the changes manually? I found this mod last night but when I used the script it did not make a backup of my Nodes.pm or pvemanagerlib.js files so I'm unable to use the uninstall using the script.

Installed without error, pveproxy reloaded.
Repeated installation is telling:

`...
Detecting support for NVMe temperature sensors...
Detected sensors:
nvme-pci-3a00

Detecting support for CPU temperature sensors...
Detected sensor:
coretemp-isa-0000

[warning] Thermalstate already added to "/usr/share/perl5/PVE/API2/Nodes.pm".
[warning] New temperature display items already added to the summary panel in "/usr/share/pve-manager/js/pvemanagerlib.js".`

But still no temp sensors in summary !

Same with pve-mod-nag-screen.sh, still getting nag screens.

Is there anything elso to do?

I'm new to proxmox and installed 8.2.2 freshly from source.

I don't see any output related to temperature in the summary page.

Installation went trough without isse.

sensors -j reads

{
   "coretemp-isa-0000":{
      "Adapter": "ISA adapter",
      "Package id 0":{
         "temp1_input": 41.000,
         "temp1_max": 105.000,
         "temp1_crit": 105.000,
         "temp1_crit_alarm": 0.000
      },
      "Core 0":{
         "temp2_input": 39.000,
         "temp2_max": 105.000,
         "temp2_crit": 105.000,
         "temp2_crit_alarm": 0.000
      },
      "Core 1":{
         "temp3_input": 39.000,
         "temp3_max": 105.000,
         "temp3_crit": 105.000,
         "temp3_crit_alarm": 0.000
      },
      "Core 2":{
         "temp4_input": 39.000,
         "temp4_max": 105.000,
         "temp4_crit": 105.000,
         "temp4_crit_alarm": 0.000
      },
      "Core 3":{
         "temp5_input": 39.000,
         "temp5_max": 105.000,
         "temp5_crit": 105.000,
         "temp5_crit_alarm": 0.000
      }
   },
   "acpitz-acpi-0":{
      "Adapter": "ACPI interface",
      "temp1":{
         "temp1_input": 27.800
      }
   },
   "nvme-pci-0500":{
      "Adapter": "PCI adapter",
      "Composite":{
         "temp1_input": 39.850,
         "temp1_max": 82.850,
         "temp1_min": -273.150,
         "temp1_crit": 84.850,
         "temp1_alarm": 0.000
      }
   }
}

Describe the bug
Get N/A in CPU Thermal State

To Reproduce
Fresh Install

Expected behavior
CPU Temp

Screenshots

Sensors output

$ sensors -j
{
   "iwlwifi_1-virtual-0":{
      "Adapter": "Virtual device",
      "temp1":{
ERROR: Can't get value of subfeature temp1_input: Can't read
      }
   },
   "nvme-pci-0300":{
      "Adapter": "PCI adapter",
      "Composite":{
         "temp1_input": 44.850,
         "temp1_max": 89.850,
         "temp1_min": -273.150,
         "temp1_crit": 94.850,
         "temp1_alarm": 0.000
      },
      "Sensor 1":{
         "temp2_input": 44.850,
         "temp2_max": 65261.850,
         "temp2_min": -273.150
      },
      "Sensor 2":{
         "temp3_input": 61.850,
         "temp3_max": 65261.850,
         "temp3_min": -273.150
      }
   },
   "amdgpu-pci-0400":{
      "Adapter": "PCI adapter",
      "vddgfx":{
         "in0_input": 1.218
      },
      "vddnb":{
         "in1_input": 0.812
      },
      "edge":{
         "temp1_input": 58.000
      },
      "PPT":{
         "power1_input": 10.000
      }
   },
   "k10temp-pci-00c3":{
      "Adapter": "PCI adapter",
      "Tctl":{
         "temp1_input": 63.750
      }
   }
}

The installation of the temp. mod is not working for me on a Proxmox 8 node:

root@pve:~# sh pve-mod-gui-temp.sh install
pve-mod-gui-temp.sh: 15: Syntax error: "(" unexpected

Anybody else who can reproduce it?

got a weird issue with showing up the temp sensors when under a reverse proxy

so going to local-network-ip:8006 shows the sensors, but when opening the page using a domain, setup under traefik w/ssl, they don't show up at all, like it's the original page loading without any mods

i don't think it's a browser cache issue since i tried in multiple browsers and all have the same behavior

this is under rev proxy:

this is under local ip access:

can't say if it's really an issue with the mod (it doesn't sound like it) but wanted to report it, maybe there's an idea to fix it

Hi!

Is it possible to modify script to get single number (Package id 0) readings on summary screen instead of 14?)

Under a relativley fresh install of PVE 8.2.2 the installation causes a blank / black screen after a browser refresh.

note: following a tutorial to achieve a similar result, also resulted in the same issue, could be related, might not be.
running dual cpu's on Poweredge T420.
have a NIC with sensor information. (TX401)
do not know very much about perl or javascript yet, happy to help where I can though.

uninstall worked perfectly and GUI interface returned to working as expected.

What the script accomplishes in the screen shots looks perfect. Feel free to reach out if you want for more info.

It would be great if extra hardware model info could be displayed.

manufacturer
model
serial

these can be parsed out of demidecode pretty easily

dmidecode -t 1
# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.

Handle 0x0100, DMI type 1, 27 bytes
System Information
        Manufacturer: Dell Inc.
        Product Name: PowerEdge R630
        Version: Not Specified
        Serial Number: FAKESERIAL
        UUID: FAKEUUID
        Wake-up Type: Power Switch
        SKU Number: SKU=NotProvided;ModelName=PowerEdge R630
        Family: Not Specified

First of all: thank you very much for building these scripts!

Is your feature request related to a problem? Please describe.
I have the ASRockRack W680D4U-2L2T/G5 motherboard and I am running Proxmox on it.
Long story short: the default NCT6798D chip does not deliver fan speeds along with quite a bunch of other stuff. Manually enabling the kernel module doesn't help - most if not all of the relevant values are broken.

A proper IPMI driver is also not found by lm-sensors / sensors.

Describe the solution you'd like
Use freeipmi - or rather: ipmi-sensors - to retrieve RPM values of the fans. I am not sure how to go about the configuration though.
Alternatively ipmitool could be used, but in my experience so far (though I only tried it on this one motherboard) it's every so slightly slower.

Describe alternatives you've considered
I considered making a separate script rather than modifying pve-mod-gui-sensors.sh, but I feel it would be a better idea to include it in the original script, because one really would only need any values from ipmi-sensors if the regular sensors did not manage to deliver them for whatever reason.

Additional context
None yet, but I can expand and perhaps I could even help with a PR if you would consider the PR to be merged.

Sensors output

root@pve:~# ipmi-sensors
ID | Name             | Type                   | Reading    | Units | Event
1  | VOLT_3VSB        | Voltage                | 3.33       | V     | 'OK'
2  | VOLT_5VSB        | Voltage                | 5.05       | V     | 'OK'
3  | VOLT_CPU_VCORE   | Voltage                | 0.68       | V     | 'OK'
4  | VOLT_VCCIN_AUX   | Voltage                | 1.78       | V     | 'OK'
5  | VOLT_VDD2        | Voltage                | 1.10       | V     | 'OK'
6  | VOLT_1.05V_PCH   | Voltage                | 1.04       | V     | 'OK'
7  | VOLT_0V82SB_PCH  | Voltage                | 0.82       | V     | 'OK'
8  | System Event     | System Event           | N/A        | N/A   | 'OK'
9  | VOLT_1V8SB       | Voltage                | 1.78       | V     | 'OK'
10 | VOLT_VCCSA       | Voltage                | 0.90       | V     | 'OK'
11 | VOLT_BAT         | Voltage                | 3.12       | V     | 'OK'
12 | System Event Log | Event Logging Disabled | N/A        | N/A   | 'OK'
13 | VOLT_3V          | Voltage                | 3.27       | V     | 'OK'
14 | VOLT_5V          | Voltage                | 4.95       | V     | 'OK'
15 | VOLT_12V         | Voltage                | 12.20      | V     | 'OK'
16 | VOLT_PSU1_VIN    | Voltage                | N/A        | V     | N/A
17 | VOLT_PSU2_VIN    | Voltage                | N/A        | V     | N/A
18 | CUR_PSU1_IOUT    | Current                | N/A        | A     | N/A
19 | CUR_PSU2_IOUT    | Current                | N/A        | A     | N/A
20 | TEMP_CPU         | Temperature            | 28.00      | C     | 'OK'
21 | FSC_INDEX        | Temperature            | 28.00      | C     | 'OK'
22 | TEMP_MB          | Temperature            | 33.00      | C     | 'OK'
23 | TEMP_CARD_SIDE   | Temperature            | 33.00      | C     | 'OK'
24 | TEMP_X710        | Temperature            | 30.00      | C     | 'OK'
25 | TEMP_VR          | Temperature            | 31.00      | C     | 'OK'
26 | TEMP_PSU1        | Temperature            | N/A        | C     | N/A
27 | TEMP_PSU2        | Temperature            | N/A        | C     | N/A
28 | TEMP_TR1         | Temperature            | N/A        | C     | N/A
29 | TEMP_M.2         | Temperature            | 38.00      | C     | 'OK'
30 | FAN1             | Fan                    | N/A        | RPM   | N/A
31 | FAN2             | Fan                    | N/A        | RPM   | N/A
32 | FAN3             | Fan                    | N/A        | RPM   | N/A
33 | FAN4             | Fan                    | N/A        | RPM   | N/A
34 | FAN5             | Fan                    | N/A        | RPM   | N/A
35 | FAN6             | Fan                    | 2200.00    | RPM   | 'OK'
36 | FAN7             | Fan                    | 2200.00    | RPM   | 'OK'
37 | PWR_PSU1_PIN     | Power Supply           | N/A        | W     | N/A
38 | PWR_PSU2_PIN     | Power Supply           | N/A        | W     | N/A
39 | PSU1_FAN         | Fan                    | N/A        | RPM   | N/A
40 | PSU2_FAN         | Fan                    | N/A        | RPM   | N/A
41 | PWR_PSU1_POUT    | Power Supply           | N/A        | W     | N/A
42 | PWR_PSU2_POUT    | Power Supply           | N/A        | W     | N/A
43 | ChassisIntr      | Physical Security      | N/A        | N/A   | 'OK'
44 | CPU_PROCHOT      | Processor              | N/A        | N/A   | 'OK'
45 | CPU_THERMTRIP    | Processor              | N/A        | N/A   | 'OK'
46 | STS_PSU1         | Power Supply           | N/A        | N/A   | 'OK'
47 | STS_PSU1_AC_LOST | Power Supply           | N/A        | N/A   | N/A
48 | STS_PSU1_VOUT_OV | Power Supply           | N/A        | N/A   | N/A
49 | STS_PSU1_IOUT_OC | Power Supply           | N/A        | N/A   | N/A
50 | STS_PSU2         | Power Supply           | N/A        | N/A   | 'OK'
51 | STS_PSU2_AC_LOST | Power Supply           | N/A        | N/A   | N/A
52 | STS_PSU2_VOUT_OV | Power Supply           | N/A        | N/A   | N/A
53 | STS_PSU2_IOUT_OC | Power Supply           | N/A        | N/A   | N/A
54 | STS_PSU1_Fan     | Power Supply           | N/A        | N/A   | N/A
55 | STS_PSU2_Fan     | Power Supply           | N/A        | N/A   | N/A
56 | WATCHDOG2        | Watchdog 2             | N/A        | N/A   | 'OK'
66 | CPU_CATERR       | Processor              | N/A        | N/A   | 'OK'

The first time I installed this mod on Proxmox I got it working fine. I recently did an update, which included a kernel update, and after I rebooted the server, all temps were missing.
I ran the script again, and now I can see the CPU temps, but no HDD temps.
Tried the uninstall flag and then re-install, and always the same result.

Testing with the command "sensors -j" does respond with all the drives and their temps.

Not sure where to go from here.

Hello,

first of all, thanks for sharing your great work. I use proxmox at home.
I miss the fan speed:

root@pve ~ > sensors
asus_wmi_sensors-virtual-0
Adapter: Virtual device
CPU Core Voltage:          1.27 V
+12V Voltage:             12.23 V
+5V Voltage:               4.99 V
3VSB Voltage:              3.31 V
CPU Fan:                 1467 RPM
Chassis Fan 1:           1548 RPM
Chassis Fan 2:           1400 RPM
Chassis Fan 3:           1386 RPM
AIO Pump:                   0 RPM
Water Pump:                 0 RPM
CPU OPT:                    0 RPM
CPU Temperature:          +46.0°C
Motherboard Temperature:  +31.0°C
Chipset Temperature:      +45.0°C
Tsensor 1 Temperature:   +216.0°C

nvme-pci-0100
Adapter: PCI adapter
Composite:    +38.9°C  (low  =  -5.2°C, high = +83.8°C)
                       (crit = +87.8°C)

asusec-isa-0000
Adapter: ISA adapter
CPU Core:      1.26 V
CPU_Opt:        0 RPM
Chipset:      +45.0°C
CPU:          +46.0°C
Motherboard:  +31.0°C
T_Sensor:     -40.0°C
VRM:          +20.0°C
CPU:          17.00 A

k10temp-pci-00c3
Adapter: PCI adapter
Tctl:         +46.2°C
Tccd1:        +39.2°C

Do you can fix it? Many thanks!

Dirk

if I log into a Proxmox GUI with any server that had lm-sensors installed temperatures will show ,

but for systems that do not have lm-sensors installed the entire page becomes frozen

any way to put a check in place so it will skip trying to load data that does not exist ?

if I log into proxmox GUI on that machine instead of using the data center list

sed: -e expression #1, char 382: unknown command: `k'

`root@proxmox:~# ./pve-mod-gui-temp.sh install

Installing the Proxmox VE temperatures display mod...

Preparing mod installation...
ERROR: Can't get value of subfeature temp1_input: Can't read

Detecting support for HDD/SDD temperature sensors...

Detecting support for NVMe temperature sensors...
[warning] No NVMe temperature sensors found.

Detecting support for CPU temperature sensors...
Detected sensor:
k10temp-pci-00c3
k10temp-pci-00cb

Backup of "/usr/share/perl5/PVE/API2/Nodes.pm" saved to "/root/backup/Nodes.pm.2023-08-25_12-34-14".
Added thermalstate to /usr/share/perl5/PVE/API2/Nodes.pm.
Backup of "/usr/share/pve-manager/js/pvemanagerlib.js" saved to "/root/backup/pvemanagerlib.js.2023-08-25_12-34-14".
Expanded space in "/usr/share/pve-manager/js/pvemanagerlib.js".
sed: -e expression #1, char 382: unknown command: `k'
New temperature display items added to the summary panel in "/usr/share/pve-manager/js/pvemanagerlib.js".

Restarting PVE proxy...
Installation completed
`

Since a paid subscription is unlikely to be an option for private use (at least in my case), watching a nag screen on a regular basis started to annoy me more and more. So I implemented a script that blocks the popup dialog.
Such a modification is of course somehow controversial, so I'm curious if there should be a place for such a function in the project.

I get a script error when running the Proxmox temperature mod. It used to be working until I manually installed IT87 driver to display fan speeds.

This is the error output.

Installing the Proxmox VE temperatures display mod...

Preparing mod installation...
ERROR: Can't get value of subfeature temp1_input: Can't read

Detecting support for HDD/SDD temperature sensors...

Detecting support for NVMe temperature sensors...
Detected sensors:
nvme-pci-0300

Detecting support for CPU temperature sensors...
Detected sensor:
coretemp-isa-0000

Backup of "/usr/share/perl5/PVE/API2/Nodes.pm" saved to "/root/backup/Nodes.pm.2024-04-06_22-15-14".
Added thermalstate to /usr/share/perl5/PVE/API2/Nodes.pm.
Backup of "/usr/share/pve-manager/js/pvemanagerlib.js" saved to "/root/backup/pvemanagerlib.js.2024-04-06_22-15-14".
Expanded space in "/usr/share/pve-manager/js/pvemanagerlib.js".
New temperature display items added to the summary panel in "/usr/share/pve-manager/js/pvemanagerlib.js".

Restarting PVE proxy...

I have also attached my sensor output:

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:            N/A  

it8613-isa-0a30
Adapter: ISA adapter
VCore:       726.00 mV (min =  +0.00 V, max =  +2.81 V)
V_SM:          1.20 V  (min =  +0.00 V, max =  +2.81 V)
3VSB:          3.92 V  (min =  +0.00 V, max =  +5.61 V)
+3.3V:         3.34 V  
CPU_fan:     2576 RPM  (min =    0 RPM)
SYS_fan:        0 RPM  (min =    0 RPM)
CPU_temp:     +50.0°C  (low  = -128.0°C, high = +127.0°C)  sensor = thermistor
SYS_temp:     +48.0°C  (low  = -128.0°C, high = +127.0°C)  sensor = thermistor

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  (crit = +110.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +56.0°C  (high = +105.0°C, crit = +105.0°C)
Core 0:        +54.0°C  (high = +105.0°C, crit = +105.0°C)
Core 1:        +54.0°C  (high = +105.0°C, crit = +105.0°C)
Core 2:        +54.0°C  (high = +105.0°C, crit = +105.0°C)
Core 3:        +54.0°C  (high = +105.0°C, crit = +105.0°C)

nvme-pci-0300
Adapter: PCI adapter
Composite:    +48.9°C  (low  = -273.1°C, high = +69.8°C)
                       (crit = +72.8°C)
Sensor 1:     +48.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +53.9°C  (low  = -273.1°C, high = +65261.8°C)

I have also used a custom sensor.conf for lm-sensors. Is it because I've relabelled temp1?

# BeeLink EQ12/S12 series of Intel N100 based Mini-PC
# See: https://minipcreviewer.com/beelink-mini-pc-eq12-review/
#
# dmi: Board Manufacturer: AZW
# dmi: Board Product Name: EQ
# dmi: BIOS Version: N95V104 03/17/2023

chip "it8613-isa-*"
  ignore temp3
  label fan2 "CPU_fan"
  label fan3 "SYS_fan"
  label temp1 "CPU_temp"
  label temp2 "SYS_temp"
  label in0 "VCore"
  label in1 "V_SM"
  ignore in2
  ignore in4
  ignore in5
  ignore in8 # hardcoded Vbat see it87.c
  ignore intrusion0

First of all, Thank you very much for these scripts!!

Describe the bug
After a lot of work I managed to make my fan show in sensors and I wanted it displayed in gui so I uninstalled the original senors script:
./pve-mod-gui-sensors.sh uninstall
and then reinstall it with some new options like show averages and display fans and so on.
Not only that it didn't work, but now I can't restore my original files because the for some unkown reason the backup already contains the modified gui.
So now I am in a state that the cpu temps are displayed ( one for each core), the drive temp as well, but not the fans.
This is not a request on how to fix this, it is simply an issue on restoring the original gui.

To Reproduce
Steps to reproduce the behavior:

1. Go to shell
2. ./pve-mod-gui-sensors.sh uninstall
3. Reload page
4. Observe that the restored gui is actually the current one

Expected behavior
I expect to have the original gui

This is the "restored" gui
Sensors output

Additional context
updated Virtual Environment 8.2.4

I am guessing that installing all your scripts created multiple backups and the original gui is lost.

Thank you for this scripts!

When running the bash pve-mod-gui-sensors.sh install
I get an error
Invalid entry length (0). DMI table is broken! Stop.
after the Sensors' output added to "/usr/share/perl5/PVE/API2/Nodes.pm".

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Sensors output
If applicable, provide sensor datadump (use the argument save-sensors-data)

Additional context
Add any other context about the problem here.

Hello,
tanks a lot for you work!!

Could you think is possible to add support for GPU and RAM?

Best Regards
Stefano

Thanks for the script - and reading through your README - you had mentioned the DRIVETEMP KERNAL MODULE, no real instructions on making sure it was there - as I had installed lm-sensors but was not seeing anything that looked like HDD temps. My PVE box has one NVME drive via a card in a PCIe slot and an SSD drive attached to SATA port on motherboard.

After doing the steps here:

I am seeing this - but how do I know which is which for HDDs? Also - what are these other temps?

Hi,

Can you please help me to fix this error. It's probably a matter of correcting some file. Until the patch is released, I can edit it manually.

fam15h_power-pci-00c4
Adapter: PCI adapter
power1: 42.04 mW (avg = 67.69 mW, interval = 0.01 s)
(crit = 15.00 W)

amdgpu-pci-0008
Adapter: PCI adapter
vddgfx: 887.00 mV
vddnb: 887.00 mV
edge: +48.0°C

k10temp-pci-00c3
Adapter: PCI adapter
temp1: +48.8°C (high = +70.0°C)
(crit = +100.0°C, hyst = +99.0°C)

Can you add an output of sensors -j that currently works with this so i can change it to work with my output from a different cpu

Is your feature request related to a problem? Please describe.
Not really a problem but is causing I/O delay in Proxmox (about 2-5% increase)

Describe the solution you'd like
Add intervals (ie Auto, 5 seconds, 10 seconds, 15 seconds, etc.)

Describe alternatives you've considered
N/A

Additional context
N/A

Sensors output
N/A

Thank you!

I have one of those CWWK aliexpress boxes with the intel i7-1265U so 2 performance cores, and 8 efficiency cores. The script did run but something not quite right. Attached is the sensors -j output and what the dashboard is showing. I feel like I am just missing something in the variables. Any ideas?

{
   "coretemp-isa-0000":{
      "Adapter": "ISA adapter",
      "Package 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 4":{
         "temp3_input": 44.000,
         "temp3_max": 100.000,
         "temp3_crit": 100.000,
         "temp3_crit_alarm": 0.000
      },
      "Core 8":{
         "temp4_input": 44.000,
         "temp4_max": 100.000,
         "temp4_crit": 100.000,
         "temp4_crit_alarm": 0.000
      },
      "Core 9":{
         "temp5_input": 44.000,
         "temp5_max": 100.000,
         "temp5_crit": 100.000,
         "temp5_crit_alarm": 0.000
      },
      "Core 10":{
         "temp6_input": 44.000,
         "temp6_max": 100.000,
         "temp6_crit": 100.000,
         "temp6_crit_alarm": 0.000
      },
      "Core 11":{
         "temp7_input": 44.000,
         "temp7_max": 100.000,
         "temp7_crit": 100.000,
         "temp7_crit_alarm": 0.000
      },
      "Core 12":{
         "temp8_input": 43.000,
         "temp8_max": 100.000,
         "temp8_crit": 100.000,
         "temp8_crit_alarm": 0.000
      },
      "Core 13":{
         "temp9_input": 43.000,
         "temp9_max": 100.000,
         "temp9_crit": 100.000,
         "temp9_crit_alarm": 0.000
      },
      "Core 14":{
         "temp10_input": 43.000,
         "temp10_max": 100.000,
         "temp10_crit": 100.000,
         "temp10_crit_alarm": 0.000
      },
      "Core 15":{
         "temp11_input": 43.000,
         "temp11_max": 100.000,
         "temp11_crit": 100.000,
         "temp11_crit_alarm": 0.000
      }
   },
   "acpitz-acpi-0":{
      "Adapter": "ACPI interface",
      "temp1":{
         "temp1_input": 27.800,
         "temp1_crit": 105.000
      }
   },
   "nvme-pci-0100":{
      "Adapter": "PCI adapter",
      "Composite":{
         "temp1_input": 59.850,
         "temp1_max": 81.850,
         "temp1_min": -273.150,
         "temp1_crit": 84.850,
         "temp1_alarm": 0.000
      },
      "Sensor 1":{
         "temp2_input": 59.850,
         "temp2_max": 65261.850,
         "temp2_min": -273.150
      },
      "Sensor 2":{
         "temp3_input": 68.850,
         "temp3_max": 65261.850,
         "temp3_min": -273.150
      }
   }
}

Hi,

After running the script, everything went well, but my CPU Ryzen 5 5600G doesn't display its temperature. However, it's listed as a recognized CPU: "k10temp-pci-xxx".

Here is my sensors -j output :

   "amdgpu-pci-0a00":{
      "Adapter": "PCI adapter",
      "vddgfx":{
         "in0_input": 0.849
      },
      "vddnb":{
         "in1_input": 0.993
      },
      "edge":{
         "temp1_input": 40.000
      },
      "PPT":{
         "power1_average": 12.000
      }
   },
   "k10temp-pci-00c3":{
      "Adapter": "PCI adapter",
      "Tctl":{
         "temp1_input": 50.750
      }
   }

First of all, I apologize for my poor English.
I've patched the JS file to work on the mobile version by referring to another github repository and attached the diff result.
Additionally, I have also applied the auto-refresh feature for mobile pages.
However, I only have HDD and CPU temperature sensors, so I only added the relevant code.
I'm sorry, but could you please include my patch in your mod?
It is very difficult for me to write with "sed" command.

pvemanager-mobile.js.patch

Describe the bug
I have Proxmox on 2 nodes installed and made a cluster. After installing the great pve-mod-gui-sensors.sh script the sensors information is visible of a node. This is only visible when you look at the node where you currently log into. When selecting another node, the sensors information is not visible.

After reinstalling on both nodes almost the same problem occurs. Log in to node 1 and looking to the sensors information of node 2 will keep try loading. Then the other way around,log in to node 2 and looking to the sensors information of node 1 it will say 'N/A' at all sensors.

To Reproduce
Steps to reproduce the behavior:

1. Install the script on multiple nodes (for example node 1 and node 2)
2. Log in Proxmox GUI of a node 1
3. Select node 1 and the sensors information is available in de node 1 summary
4. Select node 2 and the sensors information is NOT available in de node summary and keeps loading.
5. Log in Proxmox GUI of a node 2
6. Select node 2 and the sensors information is available in de node 2 summary
7. Select node 1 and the sensors information is NOT available in de node summary and keeps loading.

Expected behavior
Temperature information is available in the GUI of multiple nodes when logged into 1 node.

Additional context
Nodes are updated to Proxmox 8.2.4.

Hi, first, congratulations for the great temp scripts, I´ve just installed it wihtout issues and sensors -j command shows ok (content below), however, no information is shown in the proxmox summary screen. When I try to install again the script, the following message shows:
Did I do anything wrong? what am I missing? thanks,

root@pve:~# ./pve-mod-gui-temp.sh install

Installing the Proxmox VE temperatures display mod...

Preparing mod installation...

Detecting support for HDD/SDD temperature sensors...

Detecting support for NVMe temperature sensors...
[warning] No NVMe temperature sensors found.

Detecting support for CPU temperature sensors...
Detected sensor:
coretemp-isa-0000

[warning] Thermalstate already added to "/usr/share/perl5/PVE/API2/Nodes.pm".
[warning] New temperature display items already added to the summary panel in "/usr/share/pve-manager/js/pvemanagerlib.js".

###################################################
SENSORS -j output:

root@pve:~# sensors -j
{
"acpitz-acpi-0":{
"Adapter": "ACPI interface",
"temp1":{
"temp1_input": 27.800,
"temp1_crit": 110.000
}
},
"coretemp-isa-0000":{
"Adapter": "ISA adapter",
"Package id 0":{
"temp1_input": 46.000,
"temp1_max": 105.000,
"temp1_crit": 105.000,
"temp1_crit_alarm": 0.000
},
"Core 4":{
"temp2_input": 46.000,
"temp2_max": 105.000,
"temp2_crit": 105.000,
"temp2_crit_alarm": 0.000
},
"Core 5":{
"temp3_input": 46.000,
"temp3_max": 105.000,
"temp3_crit": 105.000,
"temp3_crit_alarm": 0.000
},
"Core 6":{
"temp4_input": 46.000,
"temp4_max": 105.000,
"temp4_crit": 105.000,
"temp4_crit_alarm": 0.000
},
"Core 7":{
"temp5_input": 46.000,
"temp5_max": 105.000,
"temp5_crit": 105.000,
"temp5_crit_alarm": 0.000
}
}
}