Ensure sonos always gets ssdp callbacks from searches

[bdraco]

Proposed change

#55540 limited callbacks to only happen when something had changed in the search. This is great for performance, but unfortunately, Sonos needs the callback regardless to tell it the device is still alive.

• Add more detail to the change type

SEARCH_ALIVE - Search response, device is alive
SEARCH_CHANGED - Search response, device is new or an attribute changed (implies the device is alive since it responded)

Requires StevenLooman/async_upnp_client#87

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)
• 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:

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
• The code has been formatted using Black (black --fast 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.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[bdraco]

@StevenLooman I bumped to 0.22.0 here. Unfortunately it looks like there is a regression as the UPNP entry for my UDM pro no longer has any entities.

[StevenLooman]

@StevenLooman I bumped to 0.22.0 here. Unfortunately it looks like there is a regression as the UPNP entry for my UDM pro no longer has any entities.

UDM pro is your router, I think? Can you check if the IGDv1 (or v2) device is an embedded device? Or better yet, can you send the device description (xml) file?

[StevenLooman]

StevenLooman/async_upnp_client#88 is on its way.

[bdraco]

Also I think we can remove defusedxml from the requirements of ssdp in a future PR since its no longer used directly.

[bdraco]

StevenLooman/async_upnp_client#88 is on its way.

Pulled your branch. Tested and working 👍

[StevenLooman]

Published async-upnp-client==0.22.1

[StevenLooman]

No doubt you'll upgrade the PR to async-upnp-client==0.22.1.