I have struggled quite a lot to get it automatically populate and look the way I want it. The biggest struggle for me was nesting the layout cards and figuring out how to properly configure which part the card is going to duplicate, because in combination with the auto-entities card, the configuration for the created card actually needs to be added as option parameter.
For me personally it makes the most sense to just replicate the cards section for each entity and allow to use a placeholder for the entity. Of course this has the drawback of not being as flexible, as you are not able to add special behavior for each entity anymore.
@kamtschatka Thank you for the work on this card. Should make it much easier!
Would you mind posting the yaml and other requirements to create the dashboard in the picture you posted? I am in the process of creating a statistics view and this would provide inspiration.
To explain it a bit and make it a bit easier to understand:
I am using the auto-entities card to select all on/off switches for docker containers. Very important to use the switches, because the template card will rerender whenever a value changes, so if you for example use the cpu values of the docker containers, this will mean a huge CPU load.
I am then using the config-template-card to replace the name of the docker container switch to the sensors and add the “_cpu”, “_memory”, … to the fold-entity-row.
The easy-layout-card is used to configure the folded down row + every element you see(I have tried to get it to work with the standard layout-card and it has 60 lines more, less reusable code and it required me a very long time to set it up)