Automatically populate dropdown options from effects / entity attribute lists?

[NewsGuyTor]

I am trying to create a dropdown menu to control the effect for each one of my RGB lights. My light entities has a attribute called effect_list which contains all the scene names. I was hoping I could just point the dropdown's options to this attribute, but it seems I have to manually define each effect as a separate option in the YAML. Is this accurate?

For a light with 20+ effects, in that case the card code gets very long and repetitive. It also means if I add a new scene in the Nanoleaf app for example, I have to remember to go back and update my Lovelace YAML.

It would be cool if the dropdown feature could automatically populate its options from an entity attribute that contains a list. For instance, you could point the options field to state_attr('light.my_light', 'effect_list') and the card would create an option for each item in that list.

[AlexKusnezov]

I want to know this too, if there's a way to auto populate dropdown, I have one that is dymaically populating an input_select eintity with 10 last played playlists from Music Assistant, the original tile card just wastes too much space and looks ugly: