Fix Acmeda integration

[atmurray]

Breaking change

Proposed change

As part of homeassistant code refactoring changes were made to the acmeda integration that broke the integration when discovering new hubs. This pull request fixes the discovery of hubs and other reported defects:

• Rollease Acmeda integration fails with "UnboundLocalError: cannot access local variable 'hubs' where it is not associated with a value" #124025
• Cannot add integration from 2024.7.0 onwards (Rollease Acmeda Automate integration) #123510

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:
  Rollease Acmeda integration fails with "UnboundLocalError: cannot access local variable 'hubs' where it is not associated with a value" #124025
  Cannot add integration from 2024.7.0 onwards (Rollease Acmeda Automate integration) #123510
• 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]

Can we try splitting some bug fixes in different PRs? Haven't read the code yet, but having a non string unique id usually requires a migration

[atmurray]

Done, reverted changes to unique_id

[joostlek]

Awesome, can we also do the bump in a separate PR? :)

[atmurray]

Done

[joostlek]

I think the comments from bdraco mean that we should refactor the library to remove the extra async loop stuff and because the library is async we don't have to worry about running non-async code

[atmurray]

Have reverted the change to the notification callback and submitted a pull request to resolve that separate issue:
#125483

[frenck]

There is an merge conflict, could you take a look?

..?Frenck

[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.