New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove deprecated yaml config from sma #62472
Conversation
Hey there @kellerza, @rklomp, mind taking a look at this pull request as it has been labeled with an integration ( |
Thanks for the proposal! We can remove the legacy import features from |
I applied your suggestion but tests are failing. |
See tkdrob#3 for some more cleanup. |
* Remove CONF_SENSORS and CONF_CUSTOM * Cleanup tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thanks, @tkdrob 👍
Breaking change
The previously deprecated YAML configuration of the SMA integration has been removed.
SMA is now configured via the UI, any existing YAML configuration has been imported in previous releases and can now be safely removed from your YAML configuration files.
Proposed change
Remove deprecated yaml config from sma
Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: