Fix reload of AVM FRITZ!Tools when new connected device is detected

[mib1185]

Proposed change

Newly detected device trackers are disabled while adding to hass and gets enabled automatically if a device entry for the mac address gets registered or does already exists (eq. through another integration). This works perfectly fine for integration, which only creates device trackers, but no other entities for a tracked physical device.
The fritz integration does not only create device trackers, but also switches (to control the internet access) and buttons (to trigger wol via the Fritzbox router). So when a newly connected device is detected, the integration will create a new device tracker (which is disabled by the device tracker platform while adding to hass) and the other entities, which also register proper device entries and those will enable the device tracker. This causes the integration to be reloaded by the device registry, because of "disabled_by has been changed".

With this PR we manually register the device-registry entries for newly detected devices before we trigger to add the new entities.

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 Fritz Integration repeatedly losing and re-detecting all devices on network #138262
  • fixes Fritz!Box Tools states gets unavailable when new devices enters network #80385
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend 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 @AaronDavidSchneider, @chemelli74, mind taking a look at this pull request as it has been labeled with an integration (fritz) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of fritz 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 fritz 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.