Revert #122676 Yamaha discovery

[joostlek]

Proposed change

Revert Yamaha discovery since a lot of users have trouble with the discovery, causing stability issues. This PR reverts #122676. Instead, we should follow up with migrating to the config flow, where we can use the SSDP methods from Home Assistant, which are way more robust.

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 #
• 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.

To help with the load of incoming pull requests:

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

[joostlek]

@pssc I discussed the problem with some people from the core team and we think this is the better step instead of overengineering a storage and thing. Also, we can use a flow similar to reolink or dlink to link a DHCP mesasge to a succesfully loaded intergation, allowing us to set the unique_id for manual setup or imported configurations

[joostlek]

Tested OK by @tomlut

[pssc]

@pssc I discussed the problem with some people from the core team and we think this is the better step instead of overengineering a storage and thing. Also, we can use a flow similar to reolink or dlink to link a DHCP mesasge to a succesfully loaded intergation, allowing us to set the unique_id for manual setup or imported configurations

Thanks for the feedback @joostlek understood lets get people working again.

[joostlek]

This PR was meant for 2024.9, but didn't make it. Can we look into config flow for 2024.10?

[pssc]

fixes #123861 #124087 #124012

[joostlek]

Did I ask if you have discord yet?

[pssc]

Did I ask if you have discord yet?

Yes sporadically seems to be a number of months since I logged in.

[joostlek]

We can discuss on there if you want

[avwuff]

Confirmed, 2024.9.1 no longer breaks my Yamaha. Thanks!