Bump yolink-api to 0.3.6 fix aiomqtt breaking changes

[matrixd2]

Proposed change

Fix aiomqtt breaking changes

YoSmart-Inc/yolink-api@v0.3.4...v0.3.6

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 # HA stopped communicating with my Yolink devices "switches & motion sensors" after 2024.4 update. #108492 Yolink stopped updating sensors in HA. Yolink App still works #108518 yolink door window sensors not responding hass 2024.1.4 #108459 Repeat of Issue #91304 #108520
• 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 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.

[balloob]

This dependency bump fixes on a fixed version of aiomqtt by setting aiomqtt==2.0.0. This means that it will start conflicting with any other dependency that will rely on aiomqtt>=2.0.1 or higher. Please loosen the dependency.

[matrixd2]

This dependency bump fixes on a fixed version of aiomqtt by setting aiomqtt==2.0.0. This means that it will start conflicting with any other dependency that will rely on aiomqtt>=2.0.1 or higher. Please loosen the dependency.

Is there any way to lock the versions of dependencies to prevent third-party library dependency updates from causing integration failures?

[frenck]

Is there any way to lock the versions of dependencies to prevent third-party library dependency updates from causing integration failures?

You could set an upper limit on the major version, however, that makes assumptions on the versioning as well (there are many different strategies). In general, the best way to handle things like this: is ensuring it works in tests.

[edenhaus]

Thanks @matrixd2 👍

I use an upper bound in my library to prevent breaking changes, as aiomqtt uses semantic versioning. The best would be to write tests as mentioned by @frenck

[matrixd2]

When will this fix be released? This error will cause a large number of client reconnections. In addition to users being unable to use it normally, it will also occupy a large number of server connections.

[balloob]

@matrixd2 I didn't realize that you bumped the dependency and have resolved my comment. This looks good.