Platform systemmonitor does not generate unique IDs

Hi all

Since updating to 2024.1.3 I’m getting this error in my log:

Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:610
Integration: Sensor (documentation, issues)
First occurred: 02:04:11 (6 occurrences)
Last logged: 12:50:28

Platform systemmonitor does not generate unique IDs. ID disk_use_percent already exists - ignoring sensor.disk_use_percent
Platform systemmonitor does not generate unique IDs. ID disk_use already exists - ignoring sensor.disk_use

I don’t think I had this with 2024.1.2 and definately didn’t have it when I had this configured through yaml.

Any ideas how to resolve?

1 Like

When you originally upgraded to 2024.1.X, it imported your existing YAML configuration for the System Monitor integration into the (hidden) registry.

I believe it then suggests you remove the System Monitor’s YAML configuration.

Did you remove it before upgrading to the latest patch release (2024.1.3)?

Perhaps if you did not remove it, 2024.1.3 attempted to re-import it but now runs into the situation where the sensors it wants to import already exist in the registry.

ID disk_use_percent already exists - ignoring sensor.disk_use_percent

However, if you did remove System Monitor’s YAML configuration, then I don’t know what’s causing 2024.1.3 to report the error message.

Hi @123

Yes, I did.

Maybe I should report an issue via GitHub.

OK then, yes, report it; seems odd that it’s complaining about existing sensors.

FYI

Not exactly the problem you’re experiencing but seemingly related to System Monitor’s (mis)handling of sensor discovery/creation.

Looks like someone beat me to it #107926

Looks like 2024.1.4 will contain a fix for it.

1 Like