initial ideas to followup on

[Mariusthvdb]

• configuration option, instead of hard coding filtered attributes
• find a way to not filter options on a select or input_select entity, but do filter on an enum device_class (which was my whole purpose to begin with)

[elchininet]

Hi @Mariusthvdb,

For the first one, a lovelace config can be used. I was sure that Home Assistant front-end should have a way to send the entity to a dialog component. I have checked and each ha-more-info-dialog has an _entityId property that tells you which is the entity associated to that more-info dialog and the ha-attributes has an __stateObj property with a lot of information about the entity (and among of them entity_id). Knowing this, it is possible to do something like this:

custom_attributes:
  filter_attributes:
    ## Filter attributes from specific entities
    sensor.my_sensor:
      - some_attribute
      - some_attribute
    ## Filter attributes from entities that match a glob
    "light.kitchen_*":
      - some_attribute
      - some_attribute
    "sensor.*battery*":
      - some_attribute
      - some_attribute
    ## Filter attributes from domains
    "person.*":
      - some_attribute
      - some_attribute

For the second, I need some explanation to understand it.

[elchininet]

would you also be able to add a level by_domain and by_glob? I am aware you can use the glob for that domain (as you show in your example) but a per_domain would be even shorter and more clear to see. As would the by_glob

Yes, that is possible. But if there is a by_glob I would remove the globs from by_entity_id and from by_domain.

custom_attributes:
  filter_attributes:
    by_entity_id:
      ## Filter attributes from specific entities
      sensor.my_sensor:
        - some_attribute
        - some_attribute
    by_glob:
      ## Filter attributes from entities that match a glob
      "light.kitchen_*":
        - some_attribute
        - some_attribute
      "sensor.*battery*":
        - some_attribute
        - some_attribute
    by_domain:
      ## Filter attributes from specific domains
      person:
        - some_attribute
        - some_attribute
    by_device_class:
      ## Filter attributes from specific device classes
      enum:
        - some_attribute
        - some_attribute
      battery:
        - some_attribute
        - some_attribute
      motion:
        - some_attribute
        - some_attribute

Makes me wonder: this can only be done in that separate file? I just figured, maybe we can set it on a card level too per entity, something like

No, that would not be possible. What you add to cards is used to render the cards inside the specific card component. That is not related with the more-info dialogs. More-info dialogs don‘t have context about what you inserted in a card even if an entity in that card was the one that triggered an event to open the more-info dialog.

[elchininet]

btw, as for the merging: in customize, the individual entity mod always overrides any possibly conflicting glob. Maybe thats a thought for this too?

since were for now only talking of adding an extra filter, I suppose there is no real harm done yet. It might be a bit more complex if we are in fact able to 'unfilter' attributes, and an individual entity would need to unfilter the same attribute that was
filtered in a glob.

the individual setting would than be overriding that, and fix the conflict?
does that make sense?

That would solve it only for conflicts between specific entity_ids and globs, but there could be other overrides. Any option can conflict with other.

Something inside by_domain could conflict with something inside by_device_class for example, and something inside glob could conflict with the rest.

So, or we merge the filters or we need to specify levels of overrides, for example:

• entity_id rules over any other filters
• domain can override device class and glob
• device class can override glob
• glob could be overridden by any other filter

[Mariusthvdb]

Yes that would be my preferred choice as you write it down finally. That level of hierarchy seems correct.

Please use those by_xxx for all filter options. Very nice.

That means a yes also for taking out the globs from the other filters

[elchininet]

Hi @Mariusthvdb,
Test it deeply to detect any bug or unwanted behaviour that could occur.
Regards

[Mariusthvdb]

Btw we didn't yet discuss an 'all' option didn't we ?

We have that in custom-ui and it would really be very useful in this new resource .

Just look at the Google home devices and you know what I mean .

Would love to hear your opinion

[Mariusthvdb]

all accomplished, so closing ;-)