Add support for device registration, GUI configuration flow and additional sensor entities #166
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replace PLATFORM_SCHEMA with CONFIG_SCHEMA (breaking change unfortunately).
… when device is removed or disabled
…tores the front-ends units but is being accessed by the backend in C. Simply fetching the data immediately seemed like a better solution
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR is a major overhaul of the integration to support GUI configuration, registering devices and adding additional entities to expose temperature sensors.
Closes #153
Support for legacy YAML configuration was removed. Devices are now added using the GUI, which also supports the options flow for changing (some) device options.
This PR is based on #165 but could be modified to support msmart 0.2.3