Add own coordinator to devolo_home_network

[Shutgun]

Proposed change

The fix I tried in #122847 doesn't work. It seems I have to coordinate the coordinators, which I try by introducing an own coordinator that is tied to a semaphore.

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: devolo_home_network - Error fetching... #110555
• 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.

[home-assistant]

Hey there @2Fake, mind taking a look at this pull request as it has been labeled with an integration (devolo_home_network) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of devolo_home_network can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign devolo_home_network Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[joostlek]

The PARALLEL_UPDATES one is a blocker because the integration is platinum. afaiw, the parallel_updates is also used with service calls

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

[joostlek]

Putting to draft for the parallel updates

[Shutgun]

I had to add a pylint disable to the device_tracker.py (is this rule new?). Moving the entity to the entity module as suggested would more or less empty the device_tracker.py and hide stuff, that belongs into the device_tracker.py IMHO.

[epenet]

ScannerEntity should take precedence over CoordinatorEntity, and so pylint disable shouldn't be needed.
Is this branch up-to-date with latest pylint plugin?

Suggested change

	class DevoloScannerEntity( # pylint: disable=hass-enforce-class-module
	CoordinatorEntity[DevoloDataUpdateCoordinator[list[ConnectedStationInfo]]],
	ScannerEntity,
	class DevoloScannerEntity(
	CoordinatorEntity[DevoloDataUpdateCoordinator[list[ConnectedStationInfo]]],
	ScannerEntity,

[Shutgun]

Obviously not ... I did a rebase and now it is working 👍

[epenet]

This is weird - it's now causing issue in CI - but I can't replicate locally.
Could you please add a follow-up PR with the pylint disable and an extra comment linking to pylint-dev/pylint#9138 ?

[Shutgun]

Done: #129429