No CPU temperature for Intel Celeron DN2820

[Scoff123]

The problem

I'm running on an Intel NUC DN2820FYKH which i believe uses the Bay Trail processor. The CPU temp is exposed in the system bios. There is no processor temperature reported via System Monitor integration. There is no folder called thermal_zoneX

What version of Home Assistant Core has the issue?

core-2021.12.9

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

systemmonitor

Link to integration documentation on our website

https://www.home-assistant.io/integrations/systemmonitor

Example YAML snippet

- platform: systemmonitor
    resources:
      - type: disk_use_percent
      - type: disk_use
      - type: disk_free
      - type: memory_use_percent
      - type: memory_free
      - type: processor_use
      - type: memory_use
      - type: swap_use
  - platform: version
    source: local
    name: HomeAssistant Version
  - platform: command_line
    name: "cpu_temperature"
    command: "cat /sys/class/thermal/thermal_zone2/temp"
    unit_of_measurement: "°C"
    value_template: '{{ value | multiply(0.001) | round(2) }}'  - platform: systemmonitor
    resources:
      - type: disk_use_percent
      - type: disk_use
      - type: disk_free
      - type: memory_use_percent
      - type: memory_free
      - type: processor_use
      - type: memory_use
      - type: swap_use
  - platform: version
    source: local
    name: HomeAssistant Version
  - platform: command_line
    name: "cpu_temperature"
    command: "cat /sys/class/thermal/thermal_zone2/temp"
    unit_of_measurement: "°C"
    value_template: '{{ value | multiply(0.001) | round(2) }}'

Anything in the logs that might be useful for us?

cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:18:48 ERROR (SyncWorker_4) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp
cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:19:48 ERROR (SyncWorker_4) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp
cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:20:48 ERROR (SyncWorker_3) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp
cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:21:48 ERROR (SyncWorker_5) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp
cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:22:48 ERROR (SyncWorker_2) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp
cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:23:48 ERROR (SyncWorker_2) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp
cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:24:48 ERROR (SyncWorker_3) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp
cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:25:48 ERROR (SyncWorker_0) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp
cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:26:48 ERROR (SyncWorker_5) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp
cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:27:48 ERROR (SyncWorker_2) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp
cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:28:48 ERROR (SyncWorker_4) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp
cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:29:48 ERROR (SyncWorker_2) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp
cat: can't open '/sys/class/thermal/thermal_zone2/temp': No such file or directory
2022-01-19 18:30:48 ERROR (SyncWorker_4) [homeassistant.components.command_line] Command failed: cat /sys/class/thermal/thermal_zone2/temp

Additional information

This issue was previously raised by another user here: https://github.com/home-assistant/core/issues/57048

[probot-home-assistant[bot]]

systemmonitor documentation systemmonitor source _{^{(message by IssueLinks)}}

[Scoff123]

I've explored some of the folders within /sys/class and there is a /sys/class/hwmon folder but it is empty. There is a /sys/class/thermal folder which contains the folders cooling_device0 and cooling_device1. Within each of these folders are the following:

Checking out the files within, shows the following:

All of the similar posts about finding the CPU temp on an Intel NUC seem to point to the fact there should be a thermal_zone directory within the thermal folder, however this is not present when using HA OS on an Intel NUC DN2820

[tommyjlong]

As an FYI, I have the same model NUC, but running Ubuntu with HA running in Python-venv. Here are a few notes I took:

  Where * is 0 or 1 or 2:
  $ cat hwmon*/name
  coretemp
  soc_dts0
  soc_dts1

  Where * is 0 or 1:
  $ cat /sys/class/thermal/thermal_zone*/type 
  soc_dts0
  soc_dts1
  
  $ cat /sys/class/thermal/thermal_zone*/temp
  36000
  37000

[Scoff123]

Interesting thank you. There must be a difference between the system monitor that is integrated in HA OS for x86 generic, and HA OS for other platforms then? My hwmon folder is empty and I don't have a thermal_zone folder either, so there isn't any way of getting the coretemp.

[giannisj5]

No CPU Temperature for Gigabyte Brix BMCE-5105. Intel N5105 2.9GHz, 4C/4T Core

[drmulligan]

No CPU Temperature for Intel NUC DC3217IYE with Intel Core i3-3217U.

• is only 0 ➜ ~ cat /sys/class/hwmon/hwmon*/name acpitz

Where * is 0, 1 or 2. ➜ ~ cat /sys/class/thermal/thermal_zone*/temp 27800 29800 66000 ➜ ~ cat /sys/class/thermal/thermal_zone*/type acpitz acpitz x86_pkg_temp

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Scoff123]

This is still an issue, running the latest: Home Assistant Core 2022.5.3 Home Assistant Supervisor 2022.05.1 Home Assistant OS 7.6 Kernel version 5.10.108

HWMon folder is still empty, and there are no thermal zone sub directories under the thermal directory.

[Mariusthvdb]

running a mini PC with Intel Celeron J4125, there's no temp either (nor ipv4 address for that matter)

I can see the temp using

  - platform: command_line
    name: Cpu temp (read)
    command: >
      read -r val </sys/class/thermal/thermal_zone0/temp;echo ${val}
    value_template: >
      {{value|multiply(0.001)|round(1)}}
    unit_of_measurement: °C

not a fix, but a workaround ;-)

[Mariusthvdb]

btw, reading the code: https://github.com/home-assistant/core/blob/c075760ca0872d047e6a7c0bb7101bc66878c602/homeassistant/components/systemmonitor/sensor.py#L345 a warning should be logged if integration cant read the temp from device.

In my config, no warning is thrown, so must we conclude the temp should be readable. Why then is it not shown.

update setting level to debug made the Warning show... even though warning is the default level, so that a bit odd too. going for the workaround then.

[adwoodworth]

I have the same issue with AMD PRO A10-8770E R7. No temperature is returned, "Cannot read CPU / processor temperature information"

[bearhntr]

I have done about a dozen installs of the Generic x86-x64 HASS OS installation 8.4 to an HP ThinClient t620 and an Intel NUC (as well as other installed ‘Supervised on Debian 11’, 'VMWare" and ‘Proxmox attempted’). It has an AMD GX-415GA 1.5 GHz quad-core CPU. When I initially got started with HA - I built out the HA “Supervised” version on a DEBIAN 11 (HA 2022.7.6) load. It seemed to work fine - Wi-Fi was detected, and it appeared that everything else did as well. I then came to realize that at some point DEBIAN 11 would be to old, and opted to put the HASS OS installation on here. Now I cannot seem to get a CPU Temp reading using the same lines as I was using for DEBIAN (in fact the HWMON folders appear to be empty on HASS OS).

The installations that I am using now are HASS OS using the ‘Generic x86-x64 install’ from here: Generic x86-64 - Home Assistant 1

When I was using Debian - I used these: Installing Home Assistant Supervised on Debian 11 1

Is there someplace in HASS OS that I can see if ‘this value’ is actually being pulled from the CPU (in the OS)? I would not think the AMD CPU would be that different from an INTEL CPU. I have another one of these HP t620 that is running pfSense (FreeBSD) and it shows me the CPU temp and other things.

I have performed a test - I made a bootable Alpine 3.15.0 (from their Standard .ISO) to a USB device and I booted with it. I then followed the path listed in the CPU_TEMP (Command Line) page Command line Sensor - Home Assistant 1

– this path does not exist: /sys/class/thermal/thermal_zone0/temp

but I tracked it down to the following path and file: /sys/class/hwmon/hwmon1/temp1_input

I then shut down, and removed the Alpine Linux 3.15.0 LIVE USB and booted back to the HASS OS 8.4 installation - went looking for the same data…it is not there. Why? Why would it be different?

Please assist in getting this working - being able to monitor the TEMP of a small device which is basically headless and out-of-site - is CRITICAL.

[krystof-k]

Running on Intel Atom D525 and nothing works (/sys/class/hwmon is empty and /sys/class/thermal contains only cooling_device*).

[bearhntr]

Running on Intel Atom D525 and nothing works (/sys/class/hwmon is empty and /sys/class/thermal contains only cooling_device*).

Yeah - I learned with a lot of playing that not all hardware will report CPU temp. I have read that many of the RPi devices simply will not do it.

As I test to get mine fixed - I had to install Debian 11, and Alpine Linux and do lots of testing to get what needed to be turned on.

Use the FEATURE REQUEST/BUG REPORT in the HA Dashboard and report it. Make sure you fully identify the issue and the hardware. If you install Debian or another Linux and you cannot get a CPU temp reading - most likely not supported.

[krystof-k]

Yeah, I Googled and there were some issues with this processor, and it's a really old board, so it is probably not worth the effort.

[ElProempie]

Having the same issues here. Just cooling_device0 and cooling_device1 and an empty hwmon folder. Funny thing is the bios can read temps and when running Win10 and Core Temp, it also displayes temps.

Using apk add lm-sensors installed sysfsutils and lm-sensors. But now I cannot figure out how to run it. Both cooling_device0 & cooling_device1 stay empty. Also hwmon is still empty.

EDIT: Turns out using the SSH & Terminal add-ons, you're working in a Docker environment. Using apk add lm-sensors will install it but will also delete when exiting or rebooting HAOS.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.