process every incoming Telegram in all Devices

[farmio]

Description

process every incoming Telegram in all Devices regardless if a callback for the GA is registered (eg. StateUpdater) or not.

This will process Telegrams from the Device class even when a callback for this GA is registered ge. from StateUpdater. Some RemoteValues have no callbacks set (ClimateMode, Cover.position) from their Device so the state would not get initialized properly.
Also devices that use same GAs will be updated each, instead only one.

I'm not sure why this even was prohibited before - maybe @Julius2342 can help me out here?

This will need some testing - especially for climate modes and cover positions (which I don't have in my installation).

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• [?] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• I have performed a self-review of my own code
• The documentation has been adjusted accordingly
• The changes generate no new warnings
• Tests have been added that prove the fix is effective or that the feature works
• The changes are documented in the changelog
• The Homeassistant plugin has been adjusted in case of new config options

[coveralls]

Coverage decreased (-0.008%) to 94.491% when pulling 9b7cd0c on farmio:process-every-telegram into 73e42c0 on XKNX:master.

[marvin-w]

Looks good to me. What I wonder is if this has any significant impact on performance but I guess not. Code looks fine. After the next python release we no longer need to manually define the AsyncMock (i.e. when we drop support for 3.7)

Can you maybe make coveralls happy :)?

[farmio]

I think we should just exclude (debug)logging from coveralls. Doesn't make much sense to write tests for a log message.