unfilter on device_class adds 'device_class :' to dev tools state on single entity_id

[Mariusthvdb]

Describe the bug
A clear and concise description of what the bug is.

if adding the unfilter to device_class on sensor/binary_sensors, there is 1 entity showing both the regular device_class: in developer-tools/state, And the custom device_class :

as far as I can see, it is only showing on this particular entity, which I can not explain why

Version Custom-attributes
1.0.0 in PR
To Reproduce
Steps to reproduce the behavior:

1. see description

Expected behavior
A clear and concise description of what you expected to happen.

no extra/fake attributes in attributes column in developer-tools/state

Screenshots

Dom Path of attributes dropdown box
No error

Desktop (please complete the following information):

• OS:2023.12.3
• Browser Safari
• Version 17.1.2

The yaml config if applicable

unfilter_attributes:

#special boolean setting for all
# unfilter_all: true #/ false

  by_domain:
# filtered by Home Assistant by default
    binary_sensor:
      - device_class

    sensor:
      - device_class

Additional context

debug in inspector:

{
    "hide": [
        "icon_color",
        "id"
    ],
    "unhide": [
        "device_class"
    ]
}

[Mariusthvdb]

separately:
I just added a show_as t a UI binary threshold (whihc didnt have a device_class initially, and the correct,and fake are added in dev tools / state:

we should not show that in dev tools if possible..

[elchininet]

That is indeed an unwanted side effect of the fake attribute. I was able to reproduce it on my side, after opening a more-info dialog from the dev tools and open its attributes, if there is any unfilter fake attribute that was added to the more-info dialog, this is also added to the attributes in the dev tools.

I think that the best solution is to remove the fake attribute code and keep trying to see if there is any solution to show attributes that Home Assistant does not show on purpose in the more-info dialogs attributes.

[Mariusthvdb]

it would be too bad if we took that functionality out now...
I did only see it on 1 entity though. maybe we can have some default fake entity somehow. not sure hoe to explain, but some entity that doesnt interfere with any real life user entity....
hmm, must check if I can find if it as indeed only 1

[elchininet]

It is not about specific entities, it happens with any entity, just that you need to do specific steps to reproduce it:

1. Load a dashboard with a configuration
2. Go to the Developers tools
3. Search for an entity that has device_class as an unfilter attribute
4. Open its more-info dialog clicking on the entity
5. Open the attributes
6. Check the attributes of the Developers tools entity

[Mariusthvdb]

asked in #devs_frontend https://discord.com/channels/330944238910963714/351047592588869643/1186698001775861891

maybe some will check in here

whats the specific line In the code responsible for this? so I can post a link in Discord

[elchininet]

@Mariusthvdb,

I think that is not the question :)

There is no way to show attributes as device_class at the moment, that is the real question, how to show them.

What we are doing is not to un-filter those attributes because there is no a clear way to do that, what we are doing is to create a new attribute with the same name but with a space at the end, so that is the reason why the unwanted leakeage happens.