Fix Matter startup when Matter bridge is present

[marcelveldt]

Proposed change

Fix small oversight in the patch for transitions. In case of a bridged device the deviceinfo is different.
Fixes a crashing set-up of Matter in 2024.5 release reported on discord and forum.

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 Matter integration "Needs attention" "Failed to setup" after recent update to home assistant. #116566
• This PR is related to issue: https://community.home-assistant.io/t/2024-5-just-a-little-bit-smaller/724135/10
• 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.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @home-assistant/matter, mind taking a look at this pull request as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

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

[marcelveldt]

codecov can be ignored because this is a patch for a temporary patch

[MartinHjelmare]

Why should we not add tests? Things can still go wrong even if it's temporary.

[marcelveldt]

Why should we not add tests? Things can still go wrong even if it's temporary.

Because the actual temporary patch doesn't have a test either. This is temporary code we want to rip out asap.
I did have a look at quickly adding a test but as that required a whole test fixture (or a bit of rewrite of the test logic) it wasn't the worth it to me now (with limited time) but we can do it later. I can add tests after may 9th

[frenck]

Going to merge and move forward atm, as I want to ship the patch release and not leave this known issue in.

../Frenck