Hello
I thought that disabling an entity makes its state “unavailable”. It seems it doesn’t work like this. Setting the entity to disabled makes it disappear from the Dev Tools / States, but it is still listed by card editors, ie Entity card.
Obviously, cards show the state of such an entity even if it’s disabled.
What’s the point then of such a feature?
Background: I have a dashboard that hides entities under certain conditions, for instance, if the state is unavailable. I wanted to hide a particular entity, regardless its state. I was expecting the state of the disabled entity to be reported as unavailable. It’s not. How can I filter a disabled entity (ie within custom button card)
I don’t get how you can claim with such confidence that I haven’t done that. I feel offended by this.
Yes, I’m sure I disabled it because it disappeared from developer tools (I mentioned that).
It has eventually synced to dashboards later on (I did not looked on this for several hours). Another proof I have disabled it.
Now, disabling another entity is reflected to dashboard immediately.
The only explanation that came to my mind is that there were some cache invalidation problems. My guess is that data for developer tools/states is not cached (the same way data for dashboards is).
Anyway, I’m glad that it works as I initially expected.
some of the entity dropdowns and lists in the interface are cached and will take a moment to properly reflect a disabled entity. None of the user dashboards will have this behavior.
Frontend cards and the device page like @tom_l is mentioning, will immediately reflect the missing state as they are driven by the state machine, not the entity registry. Just like the developer tools state page.
Thanks for that detail. Although it in this context it’s even more unexpected that the entity disapeared from dev tools/states while remained available on dashboard and dashboard editor entity picker.
I was afraid something changed (I use this feature infrequently, ussually two times a year) but you’ve confirmed it didn’t. Since it happened for the first time and then disappeared on its own I would consider it as a glitch and move on.
