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
3rd step of installation guide unclear #17
Comments
Okay, now I'm gonna give a detailed explanation here and I can link to this from the Readme.
|
Adding the repo is clearly explained and straightforward. But your installation steps include a third one:
Where does this need go? |
@bertmelis I don't know what to say. You add this card like you add any other card to HA. If you use the frontend for that, then use the frontend. If you use configuration.yaml, then use that. There's nothing different from this card then any other custom card you install from HACS. But to answer your question. Those two lines go in the configuration file where you normally put the custom card imports. But you most likely don't use the yaml file, so just use the frontend like you usually do. |
Oh, yes. It suddenly all makes sense. |
This is gonna sound really stupid, but where is the custom card imports file? |
Hi, I was confused as well. I think the wording in Step 3 can be made easier to understand, because it currently does indeed sound like, with the HACS installation option, that you need to update your config. Here's a suggested revision to the HACS instructions. HACS
|
Are you adding it the Front End repo? It won't work if you're on the integrations repo menu. |
I had the same issue - entered the URL , that worked fine , but I couldn't select Lovelace. It wouldn't let me. |
Hi,
I've tried to install the repository via HACS but am not sure how to proceed in the 3rd step of the installation guide. For me, I understand that I should paste the two lines of code to my HA config, which throws me an error. May you please explain to me what I should do with those lines instead? Thank you!
The text was updated successfully, but these errors were encountered: