A Lovelace card for Home Assistant that enables dynamic UI configurations using JavaScript templates.
Config Template Card is a custom Lovelace card for Home Assistant that enables dynamic dashboard configurations using JavaScript templating. It allows users to create conditional card layouts, styles, and content based on real-time entity states, solving the limitation of static Lovelace configurations.
Home Assistant users and dashboard designers who want to create more interactive, responsive, and logic-driven Lovelace interfaces without writing full custom cards.
It provides unparalleled flexibility within Home Assistant's Lovelace ecosystem by allowing JavaScript templating directly in YAML configurations, enabling complex conditional logic and dynamic updates that aren't possible with standard cards.
📝 Templatable Lovelace Configurations
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows embedding JavaScript expressions within `${}` in YAML, enabling conditional card configurations based on real-time entity states, as shown in examples that switch card types or labels.
Supports local and dashboard-wide variables, plus global JavaScript functions defined in variables to avoid repetitive logic, simplifying complex templates across multiple cards.
Can function as a card, row, or element within other Lovelace cards like picture-elements, providing versatile layout possibilities without custom development.
Watches specified entities in the `entities` list and updates the UI automatically on state changes, ensuring dashboards stay current without manual refreshes.
Users must be proficient in JavaScript to write effective templates, creating a barrier for those only familiar with basic YAML or visual tools.
JavaScript errors in templates can break dashboards silently, and troubleshooting requires browser console checks, with the README only linking to external guides for help.
Real-time monitoring of multiple entities and JavaScript execution may introduce latency, especially in resource-constrained Home Assistant setups.
Tied to Home Assistant 0.110.0+ and the Lovelace ecosystem, limiting use in older installations or standalone projects outside this environment.