-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Migrate various platforms to config flow instead of yaml #20
Comments
IMHO: I've moved to the UI setups more. Credentials and secret files sometimes confuse the users so I feel as though the change won't have a negative effect on the shareability of it all. |
This was referenced Jul 26, 2020
pinkywafer
added a commit
that referenced
this issue
Aug 30, 2021
pinkywafer
added a commit
that referenced
this issue
Feb 16, 2022
pinkywafer
added a commit
that referenced
this issue
Feb 16, 2022
pinkywafer
added a commit
that referenced
this issue
Mar 29, 2022
pinkywafer
added a commit
that referenced
this issue
May 10, 2023
pinkywafer
added a commit
that referenced
this issue
Nov 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
More components are able to be set up on the front end using config flow. Some have to be set up in config flow.
Consider migrating from yaml to config flow where available
NB I'm still using yaml for many integrations, and i like it as I feel it makes the config files more 'complete' but as some things can't be set up in yaml, and config flow is clearly the intended route forwards, it may be worth migrating
The text was updated successfully, but these errors were encountered: