Skip to content

Avoid using zigbee macs as network macs in hue#175083

Draft
joostlek wants to merge 1 commit into
home-assistant:devfrom
joostlek:hue-zigbee-macs
Draft

Avoid using zigbee macs as network macs in hue#175083
joostlek wants to merge 1 commit into
home-assistant:devfrom
joostlek:hue-zigbee-macs

Conversation

@joostlek

Copy link
Copy Markdown
Member

Proposed change

Avoid using zigbee macs as network macs in hue

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:
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to frontend pull request:

Checklist

  • I understand the code I am submitting and can explain how it works.
  • 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.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

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 diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

@joostlek joostlek added this to the 2026.7.0 milestone Jun 28, 2026
@joostlek joostlek requested a review from marcelveldt as a code owner June 28, 2026 21:17
Copilot AI review requested due to automatic review settings June 28, 2026 21:17
@home-assistant home-assistant Bot added bugfix cla-signed has-tests integration: hue Top 100 Integration is ranked within the top 100 by usage Top 200 Integration is ranked within the top 200 by usage Top 50 Integration is ranked within the top 50 by usage labels Jun 28, 2026
@home-assistant

Copy link
Copy Markdown
Contributor

Hey there @marcelveldt, 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 mark-draft Mark the pull request as draft.
  • @home-assistant ready-for-review Remove the draft status from 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 update-branch Update the pull request branch with the base branch.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes a bug in the Philips Hue integration where Zigbee MAC addresses of Hue devices were stored in the device registry as CONNECTION_NETWORK_MAC connections instead of CONNECTION_ZIGBEE. It corrects new device creation and adds a config-entry migration (minor version bump 1 → 2) to fix already-registered devices on existing v2 bridges.

Changes:

  • In v2/device.py, use dr.CONNECTION_ZIGBEE (instead of CONNECTION_NETWORK_MAC) when registering a device's Zigbee MAC.
  • Add async_migrate_entry/_migrate_v2_zigbee_connections to rewrite existing devices' connections, bump MINOR_VERSION to 2 in the config flow, and gracefully defer migration (retry next start) when the bridge is unavailable.
  • Add tests for the new device connection, the migration of existing entries, and the v1 skip path; mark existing/mock config entries as minor_version=2 so they bypass the new migration.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
homeassistant/components/hue/v2/device.py Register Zigbee MAC under CONNECTION_ZIGBEE instead of CONNECTION_NETWORK_MAC.
homeassistant/components/hue/init.py Add async_migrate_entry and helper to migrate existing v2 device connections; defer on bridge errors.
homeassistant/components/hue/config_flow.py Bump MINOR_VERSION to 2 to trigger the migration.
tests/components/hue/test_init.py Add test that new devices get a Zigbee connection; set minor_version=2 on existing entries.
tests/components/hue/test_migration.py Add tests for v2 connection migration and v1 skip behavior.
tests/components/hue/conftest.py Default mock config entries to minor_version=2 to skip the new migration.

Comment on lines +38 to +40
except AiohueException, aiohttp.ClientError, TimeoutError:
# bridge unavailable, retry the migration on the next start
return True
await _migrate_v2_zigbee_connections(hass, entry)
except AiohueException, aiohttp.ClientError, TimeoutError:
# bridge unavailable, retry the migration on the next start
return True

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How many times we allow the migrations retry? Also, maybe the users should be getting some information in the logging (e.g. maybe they can fix stuff on their end if they're aware of it).

@home-assistant home-assistant Bot marked this pull request as draft June 29, 2026 07:17
@home-assistant

Copy link
Copy Markdown
Contributor

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.

@frenck frenck modified the milestones: 2026.7.0, 2026.7.1, 2026.7.2 Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix cla-signed has-tests integration: hue Quality Scale: No score Top 50 Integration is ranked within the top 50 by usage Top 100 Integration is ranked within the top 100 by usage Top 200 Integration is ranked within the top 200 by usage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants