You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies, I do not consider myself to be nor a YAML or an HA expert.
For the very least I am hoping to learn about a new approach that I may have not considered in the past.
Problem:
I've become addicted to the ability to reuse config for cards. Decluttering templates make a huge difference for me in maintaining configurations across my dashboards and devices.
Over time I have accumulated a large number of dashboards and views. In fact, I have a certain baseline I use for all of my views and dashboards. What I lack is the ability to reuse "view:" configuration, just as I can do with my cards.
My dashboard and view configuration is becoming more and more convoluted over time.
The solution I'd like:
Here is a simple example for illustration:
you can use a custom layout-card which can represent a whole view (although it does not support sections).
lovelace_gen - have not been able to get it to work, I'll give it another try at some point
layout-card - I am using it everywhere, but am getting funky results from time to time. a few more folks are struggling as well. It's not just the layout-card though, this path (cards as views) eventually leads to tab card hosting layout cards, etc which is getting more and more convoluted. I thought I'd simplify things and build upon what seems to be the emerging standard.
To add to that, templating a whole dashboard is my ultimate goal...
Apologies, I do not consider myself to be nor a YAML or an HA expert.
For the very least I am hoping to learn about a new approach that I may have not considered in the past.
Problem:
I've become addicted to the ability to reuse config for cards. Decluttering templates make a huge difference for me in maintaining configurations across my dashboards and devices.
Over time I have accumulated a large number of dashboards and views. In fact, I have a certain baseline I use for all of my views and dashboards. What I lack is the ability to reuse "view:" configuration, just as I can do with my cards.
My dashboard and view configuration is becoming more and more convoluted over time.
The solution I'd like:
Here is a simple example for illustration:
Alternatives I've considered:
The text was updated successfully, but these errors were encountered: