Proposed change

local_strategy contains useful information about dpId <-> dpCode mappings

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 thedevelopment checklist
• I have followed theperfect 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:

• Documentation added/updated forwww.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• Themanifest 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 torequirements_all.txt.
  Updated by runningpython3 -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 otheropen pull requests in this repository.