-
Notifications
You must be signed in to change notification settings - Fork 34
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
Cannot add include in ui-lovelace.yaml #12
Comments
I need to add a description for installing templates in ui mode. I was busy with my blueprints the last time. You cant simply add the templates this way in ui mode. You need to do it that way: https://github.com/custom-cards/button-card#configuration-templates So just need to copy the contents of the cards you need and paste them under the button_card_templates section. |
I'd also love to see this, really like the room card and would like to use it as well |
Thanks for all the work on your example. After first starting with the Rounded-Theme which seems to be no longer maintained? I today tried to include the templates from your setup. .Getting the same error as mentioned above. So now reading this, do I need to copy all the templates into the folder of the button_card_templates ? There are all_ready templates with the same names but different content? How to deal with that? Than, having: |
yes i dont understand.. too |
Hello, Late response to this, but I'm also having problems installing. You've put everything nicely in a folder, and then I still have to add everything manually? Or have you already made progress, and perhaps it is time to adjust the manual? |
The following error occurs if I try to add the line
button_card_templates: !include_dir_merge_named "ui/templates"
.When I hit "save", this message pops up:
YAML kann nicht geparst werden: YAMLException: unknown tag !<!include_dir_merge_named> (1:63) 1 | ... _dir_merge_named "ui/templates" -----------------------------------------^ 2 | ... 3 | ...
I edited it in Lovelace Mode RAW config editor.
The text was updated successfully, but these errors were encountered: