Orphaned MAC addresses breaks UniFi options flow

[Kane610]

Breaking change

Proposed change

Multi selects expect all defaults to exist in the value list.

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)
• 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 Unifi - Orphaned MAC addresses prevent configuration of switch element during configuration #64183, fixes UniFi: GUI locks up with User input malformed #59978
• 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
• The code has been formatted using Black (black --fast 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.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[bdraco]

Same fix as #60061

[Kane610]

Thanks @bdraco should we add some error to the multi select if there is an object mismatch?

[bdraco]

Thanks @bdraco should we add some error to the multi select if there is an object mismatch?

I'm pretty sure the error is happening on the frontend side since it used to not care before a frontend bump.

It would be good to improve the error message there as its hard to track down and confusing.

[Kane610]

This here improves the error message https://github.com/home-assistant/core/pull/60057/files#diff-18bdd6bece82eddbd89e2920d3f26d446ec523340f24159cfe44bb146583d11e