Update xknx to 0.15.3

[marvin-w]

Breaking change

The parameter context_timeout is now optional for binary sensors and will default to None. If you've previously not specified this parameter you'll have to adjust your config and add it like this:

knx:
  binary_sensor:
    - name: sensor
      state_address: "1/2/3"
      context_timeout: 1.0

This prevents users that do not use this feature from waiting one second until automations are triggered.

The parameter reset_after for binary sensors expects seconds now instead of milliseconds to streamline the different configuration options. (context_timeout also uses seconds)

The parameter ignore_internal_state for binary sensors now defaults to False as most users do not use this feature. It defaulted to True before.

If you have validation errors of your config after the update and you are using the operation_modes parameter for your climate devices please add all erroneous entries to the new controller_modes parameter.

Proposed change

Updates the underlying library to 0.15.3.
https://github.com/XKNX/xknx/releases/tag/0.15.1
https://github.com/XKNX/xknx/releases/tag/0.15.2
https://github.com/XKNX/xknx/releases/tag/0.15.3

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 KNX Binary sensor - Automation 'Already Running' #41564, fixes KNX Climate - Operation Mode switches automatically #40768, closes KNX integration issue: Can't send list payloads via knx_send after 0.115 #41761, fixes KNX reaction is slow and unreliable #42238, closes knx tunneling instability introduced in HA 0.115.  #43051
• This PR is related to issue:
• Link to documentation pull request: Update xknx to 0.15.3 home-assistant.io#15301

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

To help with the load of incoming pull requests:

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

[probot-home-assistant]

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

[farmio]

This update also adds

• reset_after option for Switches
• always_callback option for Sensors

and should fix

• problems with the StateUpdater. It previously queried to aggressive so the connection to some installations could not be made reliably.
• Climate reporting wrong mode

[sagitt]

will be in 0.117.x?

[farmio]

No. 0.117 will be released today, this is not even merged to dev currently.

[sagitt]

No. 0.117 will be released today, this is not even merged to dev currently.

thanks. i hope in 0.118... with new 0.15.3. the only way to use my knx setup now is restart home assistant every hour.

[farmio]

This review shall help HA reviewers get a picture of what we did here.

[marvin-w]

I integrated all review comments and rebased again against current dev.

[marvin-w]

Thanks @balloob <3

[SquaredCircleHunter]

From https://www.home-assistant.io/blog/2020/11/18/release-118/#breaking-changes

The parameter context_timeout is now optional for binary sensors and will default to None. If you’ve previously not specified this parameter you’ll have to adjust your configuration and add it like this: "context_timeout: 1.0". This prevents users that do not use this feature from waiting one second until automations are triggered.

I've read it 3 times, but it confuses me. I would think that if you do not specify anything, you will get context_timeout defaulted to None and thus no delay? And if you set it to 1.0, you will get the delay?

[marvin-w]

Exactly.

[sagitt]

yesterday the official documentation are note updated to new 118 configurations

[SquaredCircleHunter]

Ok, so I don't need to change anything to me pre-118 config? What was the default value before?

I already had binary sensors where it was not defined, so it was already optional.

[marvin-w]

The default before was 1.0. So you don't need to do anything.

[cg089]

After Updating to 0.118.0, the status of all switches show "off" (most of them are on). The status is not updated.
The status of the lights is correct, however. I don't use context_timeout neither in light nor in switch.

[marvin-w]

Please open an issue instead of commenting into this merged pull request.