WTH, Why cant we filter OUT (hide) in the developer-tools/state

This seems so simple and yet is not possible:

instead of entering a search term to select (Filter In) listing in developer-tools/state, it would be awesome if we could ‘hide’/deselect certain states/attributes.

Small example, because of a current issue an integration is causing cover entities to be unavailable. Are they all unavailable? Let me check in dev state:
enter cover. in the entity column, and deselect unavailable in state. O wait that wont work…

please add a filter-out option in developer-tools/state

And additionally maybe even a generic ‘hide unavailable’ option. Given the many many entities in that state it would easily lighten up the page altogether.

Works for me (using sensor as I don’t have covers), and I’m using unknown as the state as I have no unavailable sensors.

no? you Select unknown, I want to Deselect (hide), and show all other states for that entity

Gotcha.

Well they’re covers so they are going to be open or closed. Try filtering *o* in the state column.

Not saying this negates your request. It’s a pretty silly way to do it.

1 Like

ha well, clever!

yes, I understand we could try and do that with all commonalities in strings, and ofc my example was merely an actual action in todays debugging.

I would hope this to more of a generic principle though, and think of it just like we do in templates/scripts and even frontend, where the not_state is just that. Show me all except ‘not_state’

And don’t have the user need to think in Regex terms of characters in all possible strings of states and attributes.

I thought it did support regex at one stage but was too complicated for the average user. It’s just a sort of wildcard search now. I could be misremembering.

Also there is no “not” in regex, though there are ways to do it.

sure, I didnt check tbh, I just mentioned it to look more complex :wink: Ill strike the term

I’m not sure why it doesn’t support glob notation. I always assumed it did so things like [!unknown] would work, but it doesn’t.

that would be a very elegant solution indeed, add the !

Can we please hide “Unavailable” devices in Developer Tools → States?

Since editing an existing ESPHome device forces a useless numeric suffix to the entity, many of my automations, Lovelace cards and Node-Red flows are broken. I have to refer to Developer Tools/States to find the new entity name, but when the page is full of “Unavailable”, finding the latest iteration of the suffix number is a pain.

Right now I have 349 “Unavailable” devices.

WTH finished months ago and the posts have been archived. There is no point posting here.

Try a feature request instead.

1 Like

If I do post it in feature requests, a moderator yells at me for not searching for my issue on feature requests. I can’t win.

So search first.

1 Like