Do you mean config-template-card?
On the 1st look, the state-switch could be a good solution.
But I was thinking about reducing a code: it will be ONE card (some decluttering template) but with different sets of sensors.
So, something like this in pseudo code:
sensors[] =
{
{sensor_11,sensor_12,sensor_13,sensor_14},
{sensor_21,sensor_22,sensor_23,sensor_24},
{sensor_31,sensor_32,sensor_33,sensor_34}
}
switch(input_select_selection)
{
case choice_1: i=0;
case choice_2: i=1;
case choice_3: i=2;
case choice_4: i=3;
}
show_some_card(sensors[i])
Not sure if it’s new, but this is where the type: conditional is perfect! You give it a condition for when to show and a row for what to show.
My Case: only show date field X if the stage X has been passed.
type: entities
entities:
- type: conditional
conditions: # only if it has started blooming
- entity: input_select.plant_stage
state: Flower
row: # show the flower open date
entity: input_datetime.big_tent_flower_start
- entity: input_select.plant_stage
- entity: input_number.week
- entity: input_number.gallons
view_layout:
position: sidebar