Fix bluetooth tracker asyncio usage

[d03n3rfr1tz3]

Breaking change

Proposed change

This PR only fixes the compatibility of the bluetooth_tracker component with Python 3.11, by correcting the usage of asyncio.wait(). As its not allowed to pass coroutines into it anymore, therefore a task needs to be created.

Beware, this PR does not fix the requirement of PyBluez 0.22 and its setup problem.

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:
• This PR is related to issue: Blue Tooth Tracker platform issue after upgrade to 2023.6 #94189, Unable to install package pybluez==0.22 #94273 and Bluetooth tracker does not work with newer python - Can't run HA Core on python 3.11.2 because of dependency to pybluez==0.22 #89119
• 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 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.

To help with the load of incoming pull requests:

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

[home-assistant]

Hi @d03n3rfr1tz3

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[bdraco]

We can't accept requirements that aren't packaged releases.

I suggest splitting this PR so the device tracker change can be merged

[d03n3rfr1tz3]

Yeah I expected that and removed that one commit.

Do you know if, besides of HACS or waiting and praying for the owner of PyBluez releasing another official version, there is anything that can be done?

[bdraco]

Fork PyBluez and create a new GitHub org to maintain it

[bdraco]

If you are interested in maintaining it, I would try to reach out to the existing repo owners first

[d03n3rfr1tz3]

well ok. I'm not really interested in maintaining it (there are already new maintainers), mostly because its not my main language/environment. Just saw (like some others), that it got updated since the last release of 0.23 in 2019 and is even compatible to Python 3.11. sadly the PyPi release is kinda stale since 2021, because the new maintainers on GitHub dont have access to the PyPi account for example.

[bdraco]

It looks like its a fragmented mess https://pypi.org/search/?q=pybluez with no fork clearly alive or published a release in the last 6 months

[bdraco]

Please see above

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[bdraco]

Please update the proposed change text to reflect what this PR does