[Bug] My CPU is a bit cold

[Lars-]

Describe the bug
The temperature indicator in the system status widget reports -263200 degrees Celsius

To Reproduce
Steps to reproduce the behavior:

1. Simply open CasaOS

Expected behavior
Report a normal temperature

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Browser Chrome
• Version 107.0.5304.88

Additional context
I think I once saw it at a normal temperature, but I don't know why. It runs on an Intel NUC and it's the only application on the system.

[LinkLeong]

I'm sorry we don't offer a Win client, how do you run it in Win?

[Lars-]

I don't run it on Windows. I open the browser on Windows. I run it on Debian 11.

[LinkLeong]

Can you run "cat /sys/class/thermal/thermal_zone0/temp" and "cat /sys/class/hwmon/hwmon0/temp1_input" and give me the results?

[Lars-]

[mojothemonkey2]

submitted a fix for this #677
my first "go" at golang ;), so please check for weirdness.

basically, the cpu temp is not always in thermal_zone 0.
so we need to find the right zone by the name in "type".
this can have many values, depending on platform. so search by list of strings, like others have done eg:
https://github.com/ThomasKaiser/sbc-bench/blob/master/sbc-bench.sh#L952

don't think we need to search hwmon too - they are created as part of thermal_zone registration, if I'm reading the doc right:
https://www.kernel.org/doc/html/latest/driver-api/thermal/sysfs-api.html

Test Evidence:

# /DATA/Documents/Code/CasaOS/dist/casaos-arm64_linux_arm64/build/sysroot/usr/bin/casaos -c /etc/casaos/casaos.conf
/bin/bash -c source ./shell/helper.sh ;GetDockerRootDir
{"level":"info","ts":1668340906.3049521,"msg":"CPU thermal zone found: soc_thermal, path: /sys/devices/virtual/thermal/thermal_zone0.","func":"service.GetCPUThermalZone","file":"/code/CasaOS/service/system.go","line":319}

[LinkLeong]

Thanks for the submission @mojothemonkey2 , I've merged it and will update it in a later release.

[raller1028]

@Lars- This problem has been fixed in v0.3.8, can you upgrade to v0.3.8 to verify if this problem has been fixed?

[Lars-]

Done, it works now! Thank you all!