Add support for migrated Hue bridge

[marcelveldt]

Proposed change

Philips Hue is soon (?) going to release a new Hue (pro) bridge with more capacity and features.
For a user that wants to migrate from their existing (BSB002) bridge to the new (BSB003) bridge, the Hue app will ensure a seamless migration. A bridge that was migrated however, will stop functioning in HA as it will be factory reset at the end of the process.

This PR adds support to the HA config flow for Hue to detect the situation where the Hue bridge was migrated from old to new, basically by migrating the config entry as soon as it detects a new BSB003 bridge and existing API credentials work to connect to that bridge.

As long as mdns is functioning correctly, the HA integration for Hue should be seamlessly migrated once the Hue migration was completed.

Marked as both feature and bugfix because strictly taken this fixes broken user setups when they migrate to the new Hue bridge.

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 Hue Pro bridge is not recognized #151681
• 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 @balloob, mind taking a look at this pull request as it has been labeled with an integration (hue) you are listed as a code owner for? Thanks!

Code owner commands

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

[Copilot]

Pull Request Overview

This PR adds support for migrating Hue bridge configurations when users upgrade from an old BSB002 bridge to a new BSB003 bridge. The Hue app handles the device migration seamlessly, but Home Assistant needs to detect and update its configuration to point to the new bridge.

• Adds automatic detection of migrated BSB003 bridges during zeroconf discovery
• Implements configuration entry migration by reusing existing API credentials
• Updates device registry entries to reflect the new bridge identity