Fix Devolo cloud connection within API

[2Fake]

Breaking change

Proposed change

Bump API version to keep a cloud session alive.

Release notes: https://github.com/2Fake/devolo_home_control_api/releases/tag/v0.11.0
Changelog: 2Fake/devolo_home_control_api@v0.10.0...v0.11.0

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

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

The issue was fixed in the underlying API see here

• 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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

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

[probot-home-assistant]

Hey there @Shutgun, mind taking a look at this pull request as its been labeled with a integration (devolo_home_control) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[frenck]

@2Fake I've updated the PR description with links to the changelog and release notes. Please make sure you include them next time, as it saves us the need to search for them.

Looking at the changes upstream, it is not just a fix, but there is a whole bunch of new features implemented. From question on Discord, I understand you wanted this to go into a patch release. However, I'm not sure if that is a safe thing, considering all the changes.

Can you elaborate on that?

[2Fake]

@frenck You are right, that the API can do more, but home assistant will not use them, because the integration will just use the binary switches delivered by the API. The other devices will come with another pull request. The important file for this integration in the API is properties/binary_switch_property.py. This file was not touched in this release.

The change we need merged into home assistant is in the file backend/mprm_websocket in function _on_pong()
There are a bunch new files in the API, but this will just enable the API to gather data from devices which have other functions than a binary switch. For example a dimmer. But this will not affect the binary switches provided to home assistant

[frenck]

Thanks, @2Fake 👍