Bump async-upnp-client to 0.46.2

[StevenLooman]

Proposed change

Bump async-upnp-client to 0.46.2, to update python-didl-lite to 1.5.0. Change by @mastikamastika, via StevenLooman/python-didl-lite#35, ultimately from music-assistant/support#4398

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: Error while requesting latest state from player music-assistant/support#4398
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:
  • async-upnp-client:
    • Changelog: https://github.com/StevenLooman/async_upnp_client/blob/development/CHANGES.rst#async_upnp_client-0462-2026-01-03
    • Changes: StevenLooman/async_upnp_client@0.46.1...0.46.2
  • python-didl-lite:
    • Changelog: https://github.com/StevenLooman/python-didl-lite/blob/master/CHANGES.rst#python-didl-lite-150-2026-01-03
    • Changes: StevenLooman/python-didl-lite@1.4.1...1.5.0

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:

• 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 @chishm, mind taking a look at this pull request as it has been labeled with an integration (dlna_dms) you are listed as a code owner for? Thanks!

Code owner commands

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

[home-assistant]

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

Code owner commands

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

[home-assistant]

Hey there @chemelli74, @epenet, mind taking a look at this pull request as it has been labeled with an integration (samsungtv) you are listed as a code owner for? Thanks!

Code owner commands

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

[home-assistant]

Hey there @zewelor, @shenxn, @starkillerOG, @alexyao2015, mind taking a look at this pull request as it has been labeled with an integration (yeelight) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of yeelight 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 yeelight 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 bumps the async-upnp-client dependency from version 0.46.1 to 0.46.2, which includes an update to the underlying python-didl-lite library to version 1.5.0. This is a straightforward patch version dependency upgrade.

Key changes:

• Updated async-upnp-client version from 0.46.1 to 0.46.2 across all requirement files and integration manifests
• All 6 integrations that depend on this library have been consistently updated

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
requirements_test_all.txt	Updated async-upnp-client version in test requirements
requirements_all.txt	Updated async-upnp-client version in all requirements
homeassistant/package_constraints.txt	Updated async-upnp-client version constraint
homeassistant/components/yeelight/manifest.json	Updated async-upnp-client requirement to 0.46.2
homeassistant/components/upnp/manifest.json	Updated async-upnp-client requirement to 0.46.2
homeassistant/components/ssdp/manifest.json	Updated async-upnp-client requirement to 0.46.2
homeassistant/components/samsungtv/manifest.json	Updated async-upnp-client requirement to 0.46.2
homeassistant/components/dlna_dms/manifest.json	Updated async-upnp-client requirement to 0.46.2
homeassistant/components/dlna_dmr/manifest.json	Updated async-upnp-client requirement to 0.46.2

---

Review Summary: This is a clean dependency upgrade with all version references properly updated across the codebase. The changes are consistent, and all integrations that depend on async-upnp-client have been updated to version 0.46.2. No issues were identified.

[StevenLooman]

Thanks!