Bump onvif-zeep-async to 1.2.11

[bdraco]

Proposed change

reverts a change to the wsdl document creation that broke tplink c110s and fixes more I/O in the event loop

sets a minimum version of zeep to ensure upstream fixes are included

changelog: openvideolibs/python-onvif-zeep-async@v1.2.7...v1.2.11

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:

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 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.

To help with the load of incoming pull requests:

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

[home-assistant]

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

Code owner commands

Code owners of onvif 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 onvif Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[bdraco]

I think I can iterate on this one more time and make it simpler

Will do another pass after lunch

[bdraco]

No reason to not merge this though as it can happen in another pass and the fixes are still good here

[bdraco]

I'm going to do the revert for now and than work through the I/O in the event loop in another PR

[bdraco]

Still working on the I/O
2023-04-15 14:26:29.140 WARNING (MainThread) [asyncio] Executing <Task pending name='config entry setup LC - 00:11:11:11:11:91 onvif 9185c96eef011edc1ddbc33c084b252c' coro=<ConfigEntry.async_setup() running at /Users/bdraco/home-assistant/homeassistant/config_entries.py:383> cb=[gather.<locals>._done_callback() at /opt/homebrew/Cellar/[email protected]/3.10.10_1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/asyncio/tasks.py:720] created at /opt/homebrew/Cellar/[email protected]/3.10.10_1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/asyncio/tasks.py:337> took 0.248 seconds

[bdraco]

2023-04-15 14:26:25.620 WARNING (MainThread) [asyncio] Executing <Task pending name='config entry setup e1 192.168.107.103 - b8:ab:62:af:d1:ee onvif 18b01db4bcc1956ee419853a61713b3e' coro=<ConfigEntry.async_setup() running at /Users/bdraco/home-assistant/homeassistant/config_entries.py:383> cb=[gather.<locals>._done_callback() at /opt/homebrew/Cellar/[email protected]/3.10.10_1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/asyncio/tasks.py:720] created at /opt/homebrew/Cellar/[email protected]/3.10.10_1/Frameworks/Python.framework/Versions/3.10/lib/python3.10/asyncio/tasks.py:337> took 0.174 seconds

[bdraco]

The reason the other fix can't move forward yet is because its actually relying on the event loop being blocked for a moment since we don't have mvantellingen/python-zeep#1369 Otherwise we ask too quickly if the camera supports events and sometimes we don't get a reply in time. 🤦

[bdraco]

so its flakey with every version because sometimes creating a subscription has transient failures 😢

[bdraco]

So lets do the bump to 1.2.10 and see if we can make event startup more reliable in another PR

[bdraco]

The reason it was flakey was the old subscriptions were never being removed because of #91482

[bdraco]

So the reason its flakey is most cameras only allow 3 subscriptions and we set the subscription time to 24 hours.

If you restart 3 times you run out of slots and have to wait for a free one.

#91485 will adjust that to resub every 5 minutes so we don't ever run out of slots

[frenck]

Thanks, @bdraco 👍

Failing test seems unrelated, going to merge this one in.

../Frenck

[home-assistant]

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]

Wrong button