search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.9k stars 30.12k forks source link

[Systemmonitor] cannot read CPU / processor temperature information and other "small issues" #107057

Closed ChristophCaina closed 9 months ago

ChristophCaina commented 9 months ago

The problem

I am running HomeAssistant OS within a Proxmox VM. Until now, I had used the Systemmonitor within the configuration.yaml - and only configured 'some' basic information I needed.

With 2024.1. and moving the Integration into the UI, I am now getting the following warning in the logs:

Logger: homeassistant.components.systemmonitor.sensor
Source: components/systemmonitor/sensor.py:443
Integration: System Monitor (documentation, issues)
First occurred: 07:02:22 (1 occurrences)
Last logged: 07:02:22

Cannot read CPU / processor temperature information

This might be, because the CPU temperature will not be exposed to the VM from Proxmox.

Another issue that came with the movement is the amount of entities. The Integration is showing 425 entities in total: image

Most of them are hidden / deactivated and a result comming from the many different network interfaces (just randomly picked some for the screenshot) image

But there are also other "duplicated" sensors, that don't make much sense - such as the "Disk use ..." and "Disk free ..." sensors. image

As long as they are on the same harddrive, all sensors will report the same values.

While having the integration configured manually, you could just configure the entities you wanted ... Now, you have all of them (still, deactivated)...

It would be great, if there would be a way in the integration configuration, to select which sensors / entities you want to create at all. This would allow an individual setup just as it was with the manual configuration -> Or just move the manual configuration with the configured entities into the UI ...

What version of Home Assistant Core has the issue?

2024.1.0

What was the last working version of Home Assistant Core?

2023.12.x

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 9 months ago

Hey there @gjohansson-st, mind taking a look at this issue as it has been labeled with an integration (systemmonitor) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `systemmonitor` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign systemmonitor` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)

systemmonitor documentation systemmonitor source (message by IssueLinks)

gjohansson-ST commented 9 months ago

Cannot read CPU / processor temperature information will be removed to the upcoming version. Now it's always logging regardless if you try to use it or not which obviously is pointless.

Regarding the many entities this is the way how we try to set integrations in general to provide all and then the user can enable those wanted. We move away from too much configuration so also including this one. I know you get a lot of entities for the same disk but that's Linux way of mount points which is what is automatically discovered and setup.

Thanks for providing the feedback 👍

ChristophCaina commented 9 months ago

We move away from too much configuration so also including this one.

I fully understand - and support the 'less configuration' ... at least, when it comes to reduce the configuration in yaml and provide a proper UI...

But: showing hundresds of 'auto discovered' entities, just to hide them is not the solution in my opinion. You could provide a UI page where the user can check, what entities the system monitor should provide - and then, he can select very specific, what should be visible and what not.

Right now, it would also require to go through the list of disabled entities to check for the ones he want to see.

gjohansson-ST commented 9 months ago

But: showing hundresds of 'auto discovered' entities, just to hide them is not the solution in my opinion. You could provide a UI page where the user can check, what entities the system monitor should provide - and then, he can select very specific, what should be visible and what not.

Right now, it would also require to go through the list of disabled entities to check for the ones he want to see.

What's the difference between the entities page and if I build a new page with all those entities the system can support? Also you would use the filter so if you want "disk free" for / you would filter for "disk free" and then enable the one you want.

There is no upside to have this as configuration option rather than just enabling entities you want (or disabling for that matter).

gfn256 commented 8 months ago

@gjohansson-ST

Cannot read CPU / processor temperature information will be removed to the upcoming version. Now it's always logging regardless if you try to use it or not which obviously is pointless.

I'm still getting on boot-up:2024-01-08 09:26:00.499 WARNING (MainThread) [homeassistant.components.systemmonitor.sensor] Cannot read CPU / processor temperature information

System Information

version core-2024.1.2
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.11.6
os_name Linux
os_version 6.1.70-haos
arch x86_64
timezone xxxxxxx/xxxxxxx
config_dir /config
Home Assistant Cloud logged_in | true -- | -- subscription_expiration | August 11, 2024 at 3:00 AM relayer_connected | true relayer_region | xxxxxxxxxxxxxxxxxx remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | true remote_server | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx certificate_status | ready instance_id | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Home Assistant OS 11.3 -- | -- update_channel | stable supervisor_version | supervisor-2023.12.0 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 30.8 GB disk_used | 10.6 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Mosquitto broker (6.4.0), File editor (5.7.0), Home Assistant Google Drive Backup (0.112.1), RPC Shutdown (2.4), Samba share (12.2.0), Terminal & SSH (9.8.1), eWeLink Smart Home (1.4.3)
Dashboards dashboards | 3 -- | -- resources | 0 views | 15 mode | storage
Recorder oldest_recorder_run | December 30, 2023 at 6:53 PM -- | -- current_recorder_run | January 8, 2024 at 9:25 AM estimated_db_size | 92.73 MiB database_engine | sqlite database_version | 3.41.2
gjohansson-ST commented 8 months ago

I'm still getting on boot-up:2024-01-08 09:26:00.499 WARNING (MainThread) [homeassistant.components.systemmonitor.sensor] Cannot read CPU / processor temperature information

Everyone does if it can't be read from your system. Like I wrote it will be fixed to the upcoming version e.g. 2024.2

gfn256 commented 8 months ago

Everyone does if it can't be read from your system. Like I wrote it will be fixed to the upcoming version e.g. 2024.2

Thanks - its just that I thought it had already been updated in 2024.1.2