[FALSE] System Monitor deprecated; what to use else?

Hi,

Currently I’m using “System Monitor” to read the process usage, space etc from my Home Assistant PI. Since the last Home assistant core update; it states this will be deprecated in 6 months. What should I use instead to monitor my PI running Home Assistant Core?

Thanks in advance,

System monitor won’t be removed, it’s just moved to integrations…look there.

1 Like

Please indicate where you read that the System Monitor integration is deprecated.

According to the Release Notes for version 2024.1.0, the System Monitor integration is now configured via the UI.

What is deprecated is configuring the System Monitor integration via YAML.

Thanks @123 and @Protoncek … I should have read the release notes. The error didn’t gave the hint to use an integration.

1 Like

My strong advice: ALWAYS!!! Read thoroughly release notes BEFORE!!! you do an update. It’s easy to mess up your system, not so easy make it right again. Trust me, i’m talking from experience!

1 Like

Post the entire “error” message.


EDIT

Given that rwzdoorn’s declaration is false and has not provided any evidence to support it, I have modified the topic’s title to ensure it doesn’t mislead other readers.

2 Likes

I think it was done in a beautiful manner. I ran the upgrade and then went in and removed the code in configuration.yaml, it really is amazong, I examined the integration itself and was BLOWN AWAY! There are 434 hidden diagnostic sensors on my system in there - throughput and connectivity about every device, tit is A.M.A.Z.I.N.G… KUDOS KUDOS KUDOS!

Yeah, and visible are only those you’ve had already in config before, so really nothing changes…

Thanks for changing the title. Again, sorry for misunderstanding the message but it was not clear it was moved into an integration.

The original error was:

The System Monitor YAML configuration is being removed

This stops working in version 2024.7.0. Please address before upgrading.

Configuring System Monitor using YAML is being removed.

> Your existing YAML configuration has been imported into the UI automatically.
This line was not clear enough. There should have been a bit more explaining regarding it was moved into an integration to be honest.

Remove the systemmonitor configuration from your configuration.yaml file and restart Home Assistant to fix this issue.

Warning - 1/4/2024

1 Like

Hm… that looks clear enough to me, to be honest… where else would be imported if not in integrations?

?

Perhaps you misinterpreted what Protoncek wrote “it’s just moved to integrations”.

System Monitor has always been an integration and continues to be an integration.

  • Previously, you configured the System Monitor integration via YAML.
  • Now you configure the System Monitor integration via the UI.

That’s why it clearly states:

The System Monitor YAML configuration is being removed

and

Configuring System Monitor using YAML is being removed

and

Your existing YAML configuration has been imported into the UI automatically.

To summarize, support for configuring the System Monitor integration via YAML is being removed and will no longer be supported in version 2024.7.0. Your existing YAML configuration for the System Monitor integration has been imported into the UI. Remove your existing YAML configuration for the System Monitor integration and restart Home Assistant.

It didn’t because it was and still is an integration. It has not been moved “into an integration”. It’s simply an integration whose configuration method has changed.

In addition, I believe the message is categorized as a warning, not an error. It’s an important difference.

Actually, it’s a bit misleading to say that and perhaps that’s why rwzdoorn has misunderstood it.

The System Monitor integration is no longer configured via YAML but via a different method, sometimes referred to as ‘config flow’. Integrations using this method store their configuration in one or more hidden files in JSON format. The files are hidden to discourage users from editing it directly. The integration’s configuration is edited via the UI as displayed in, for example, Settings > Devices & Services > Integrations > System Monitor.

What has happened in this version is that a user’s existing YAML configuration, of the System Monitor integration, has been automatically converted and imported into the hidden JSON file and now you use the UI to modify its configuration.

1 Like

After the update I saw 100+ devices in system monitor. Next I removed the old config in configuration.yaml. And now all my devices are gone. Configure with the GUI shows the following options:

  • python3
  • s6-ipcserverd
  • s6-linux-init-shutdownd
    -s6- supervise
    -s6-svscan

I tried them all with no result

Removed the integration and added it again. No effect

HassOS on a NUC

I’m in the same boat. I only had 3 items to monitor but it appears none of them were imported.

i deleted all sensor config as suggested, installed the system monitor integration and selected all the options (that to me are totally unclear what they meant) but sensors are unavailable on a total of 189 entities showed; before with those symple yaml file i was able to see lot of data from my istance running on Proxmox. Surely i am doing something wrong, but using the HACS integration for proxmox i can see lot of sensors running well, so why this new feature doesn’t work?

1 Like

I cannot find sensor.date_time
Apparently not part of the replacement System Monitor Integration.
Is there a replacement?

UPDATE - found my answer.
There is a Time & Date Integration, but I could not install it. However, when I updated my system from 2024.1.5 to 2024.2.1, I could install the Time & Date Integration.
I now have the entity sensor.date_time