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
Unfortunately, the YAML mode for Lovelace doesn't support templates.
One of the features I miss the most is the ability to refer to all members of a group objects; that'd allow me to maintain a consistent set of entities between my frontend and automations etc. This, alas, does not even work in places that are prepared to accept lists of entities.
I have to list every single sensor separately and specify further options, even if I have a group.all_windows; I don't want the UI to show whether any window is open, but the details.
If children of entities supported not just entity, but group_entity:, which then expanded and repeated the block they're in for each member of the group, this block could then look like this:
Since this is not dynamic scripting nor templating but "trivial" expansion, it'd only have to be expanded once by the YAML parser when the configuration is loaded.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Unfortunately, the YAML mode for Lovelace doesn't support templates.
One of the features I miss the most is the ability to refer to all members of a group objects; that'd allow me to maintain a consistent set of entities between my frontend and automations etc. This, alas, does not even work in places that are prepared to accept lists of entities.
Consider this simplistic (abbreviated) example:
I have to list every single sensor separately and specify further options, even if I have a
group.all_windows
; I don't want the UI to show whether any window is open, but the details.If children of
entities
supported not justentity
, butgroup_entity:
, which then expanded and repeated the block they're in for each member of thegroup
, this block could then look like this:Since this is not dynamic scripting nor templating but "trivial" expansion, it'd only have to be expanded once by the YAML parser when the configuration is loaded.
Would this be a possible feature to consider?
Beta Was this translation helpful? Give feedback.
All reactions