-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Allow user to configure the integration with UI #94
Comments
Will have to find how to implement the UI part but it is something the project should have. |
Have a look here to start: https://developers.home-assistant.io/docs/config_entries_config_flow_handler Thanks for an estimation. As mentioned, many users have to make a decision now as the other integration is broken (but able to set up using the UI). |
@dylandoamaral do you have any rough estimation? Any help needed in testing etc.? |
No I don't sorry, it is a huge work and for the moment I don't have time. It is a community project maybe someone will take the lead who knows. |
I hope so. The other (original / first) integration can be considered dead due to the missing adaptations to the trakt.tv API changes. Unfortunately there's no one from that project who could team up with you to make some consolidated progress here. Anyway I still hope this basic GUI thing will be implemented. It blocks me and many other users from switching to this integration as in 2024 using YAML to configure an integration is really not the way to go anymore. Based on my experience an integration which can be set up from the UI has a much larger potential user base as it's so much more elegant and intuitive to use. |
TBH this rather is a question in the first place. If the answer is "yes, still needed", this issue becomes a feature request.
Question: Is the usage of
configuration.yaml
following setup how-to https://github.com/dylandoamaral/trakt-integration?tab=readme-ov-file#2-update-configuration-file actually really/still needed?Asking because "the other" trakt.tv integration is fully configurable from the UI:
https://github.com/custom-components/sensor.trakt?tab=readme-ov-file#installation-in-home-assistant
Please note this is some kind of a "deal breaker" question/thing. The other trakt.tv integration became kind of useless as it needs to be updated to make use of the current api (
api.trakt.tv
). Lots of users coming in, one referenced your integration here as a potential alternative and... well, here we are. Looking at oldschool.yaml
hacking which is why I did not give it a shot yet. GUI is the future.custom-components/sensor.trakt#72
The text was updated successfully, but these errors were encountered: