Fix duplicated resource issue in System Monitor

[gjohansson-ST]

Proposed change

Given that arguments can be typed in many ways it results in duplicated unique id's.
Slugify the loaded resources in the comparison to avoid this.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes Systemmonitor does not generate unique IDs #107532
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[jbouwh]

Is this not a breaking change, as it changes the ID's?

[gjohansson-ST]

Is this not a breaking change, as it changes the ID's?

It's not changing the id's. It's just for comparisons to know which entities to make or not.

[MartinHjelmare]

Thanks!

[jbouwh]

LGTM,
Thnx @gjohansson-ST 👍

[jymorel]

Hi,
I got these errors when updating from 2024.1.2 to 2024.1.3:
Platform systemmonitor does not generate unique IDs. ID disk_free already exists - ignoring sensor.disk_free
Platform systemmonitor does not generate unique IDs. ID disk_use_percent already exists - ignoring sensor.disk_use_percent

No more yaml with these sensors ...

[jbouwh]

Hi, I got these errors when updating from 2024.1.2 to 2024.1.3: Platform systemmonitor does not generate unique IDs. ID disk_free already exists - ignoring sensor.disk_free Platform systemmonitor does not generate unique IDs. ID disk_use_percent already exists - ignoring sensor.disk_use_percent

No more yaml with these sensors ...

It can be the old entities need to be removed.

[jymorel]

I don't find duplicate entities ...

[jbouwh]

Please also look at disabled entities

[gjohansson-ST]

See #107903