Split features and move battery and tx_busy values to base entity #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will split the humidity and level related features into own classes, so they can be used by any sub device unit (eq. separate sensor units on devices).
To further follow this concept, the battery related and tx_busy values are moved to the base entity. Nevertheless, the battery values from
hkrnode (thermostat) are kept for backwards compatibility with Fritz!OS < 7.08.Last but not least, there are also some debug logging added.