Unfilter

[Mariusthvdb]

it might be a nice option if we could also unfilter any of the filtered_attributes that are filtered by default by the core Frontend in
https://github.com/home-assistant/frontend/blob/dev/src/data/entity_attributes.ts

let's say Id want to show the attribute device_class which is currently filtered, it would be magic if we could set something like:

custom_attributes:
  unfilter_attributes:

## Unfilter attributes from specific entities
    sensor.my_sensor:
      - unit_of_measurement
    
## Unfilter attributes from entities that match a glob
    "*.*":
      - device_class

## Unfilter attributes from domains
    "light.*":
      - color_temp
      - brightness
    "person.*":
      - friendly_name

[elchininet]

Let me check if that is possible.

[elchininet]

Yes, it it possible to unhide attributes, it shows what is already filtered from Home Assistant.

[elchininet]

Mmm, it doesn‘t work in all the cases. For example, in a person entity that recieve the extra-filters parameter I can unhide these:

But, in my printer entities (a device_class enum), the parameter is not set and I cannot show options and icon_color (and I see these included in extraFilters properties of the element).

[elchininet]

I see whats happens, options and icon_color are coming from the plugin that I was testing, they don‘t belong to that entity. So it seems that it totally possible, let me try with more entities.

[elchininet]

So, in summary, it is possible if the attribute is filtered. If the attribute is not shown because Home Assistant decided to do it (and I am seeing that device_class is not shown on purpose, and it is not filtered), it cannot be "unhidden". But I think that we can make some workarounds for that (creating DOM nodes and do not relying in Home Assistant) but this is a second step.

[elchininet]

@Mariusthvdb,

Taking into account that Home Assistant doesn‘t show some attributes that exist in the attributes list, and they decided to exclude them, not through extra-filter but using something deeper in the architecture, we can bypass that with a workaround:

Imagine, that you want to show device_class attribute and it cannot be shown because Home Assistant decided to hide it, well, we can add more attributes to the attributes list of the ha-attributes element. The element itself doesn‘t know if the attribute is real or fake, and as the device_class already exists we just need to add something else that "looks" like device_class, so if we add "device_class " (note the space at the end) it is a different attribute but if you look at it rendered on the screen you cannot see the space, and Home Assistant blindly will render it in the attributes list :)

[elchininet]

I‘ll create a list of attributes that Home Assistant hides by default, at the moment it will contain only device_class but we can extend it if we find more cases. I‘ll create a pull request so you are able to test it.

[elchininet]

It works:

It is a "hack" to mock Home Assistant but it works :)

[Mariusthvdb]

wow that sounds a bit hacky indeed....

If the attribute is not shown because Home Assistant decided to do it (and I am seeing that device_class is not shown on purpose, and it is not filtered), it cannot be "unhidden"

why do you say device_class it not filtered? it is filtered by the frontend in the state_attributes list here https://github.com/home-assistant/frontend/blob/2682a551482c288f25a7e71a81743a6dfde8693d/src/data/entity_attributes.ts#L10 ?

I figured we'd go from there and with an 'unfilter' rewrite that file somehow....

[elchininet]

I figured we'd go from there and with an 'unfilter' rewrite that file somehow....

We cannot rewrite anything, we are working with front-end here, what we can do is access the DOM elements, change properties, apply styles, no more.

[Mariusthvdb]

check, understood...

[elchininet]

I am ready to work on the unfilter feature this evening, just let me know if these attributes here are all attributes that are not shown by Home Assistant even if they are added to the extraFilters property (I thought that for now it was only device_class).

[Mariusthvdb]

I believe so yes.
Tbh, the Frontend files are like spaghetti to me, and spread over many places...
but this seems to be the main set of filtered attributes (now called differently) and besides several extraFilters set on individual domains I wouldn't know where to find them elsewhere currently.

We could ask in dev_frontend on Discord?

[elchininet]

We could ask in dev_frontend on Discord?

Sounds good, if not we can start with device_class and if you get reports of "I am trying to unhide X and it is not working", we can detect quickly what it is and add it to the list.

[elchininet]

@Mariusthvdb,

I have the code for this almost ready to push, but first we need to figure it out what you mentioned here before making more changes.

[Mariusthvdb]

believe we can go ahead now (though Ive found a bug, which I suppose can be handled separately)