dont yet understand the history: back commandā¦ hmm. how does the name: of the button cause the history to go back?? Or does it set the name, and by clicking the is goes back in history? that would be crafty
does work indeedā¦ how cool thanks, and to Romrider of course, Iāll post this in button-card, as answer on my own question for reference.
the swiper card adds the swipe functionality to HA, so it does offer the extra UX. Its more than merely overkill, and kind of nice once you get used to its behavior.
you could probably also wrap them in a grid card, to auto fit and go to the next line. Its what I do with my dynamically created alert buttons
Hi Todd
I havenāt explained it anywhere but itās possible to use it with the UI editor if you copy / paste the content of button_card_templates.yaml into the config editor.
I write it down to add it to the github
Cheers mate, yeah thatās how I was able to accomplish it as well, did take me a bit to stumble across the fact !include doesnāt work in UI editor. Yeah, may be worth mentioning in GitHub for others
On a side note, Iām currently looking at what is involved with Lovelace Strategies to auto populate Lovelace views, would you mind if use your cards in it (if I can get it to work of course)?
What do you think about creating an addon section in your button_card_templates for community chips and cards ?
I do some tests on my side and it seems to be easy to implement
Replace include by this one in your ui-lovelace.yaml : button_card_templates: !include_dir_merge_named lovelace/button_card_templates
Put your ābutton_card_templates.yamlā in a specific folder and create an addon folder
Guys like @clemalex, @djacid or me could post our addons (button card templates) in this folder with a Readme file and community could download just what they want.