WTH is there no distinction between broken and locked entities

Simple example: my dishwasher, dryer and washing machines have a button entity for start and one for abort. If it is not running the start button is available and the abort button is unavailable (users in my household including myself read this generally as “broken” or “defective”). If the machine is running the start button is unavailable and the abort button is available.
Why is there no state representing “everything is healthy, all is good but this entity is currently not interactable/usable”? Many devices have a lot of entities which are not usable on the regular due to physical device state or simply logical constraints.
This would allow automatic dashboards showing all broken entities without including those which are just locked out.

Can you at least share the Manufacturer, model # and your intergration method? You sound frustrated, but failed to share any info that would help solve your issue!

The “issue” is not with an integration, but with a missing construct for disabled/inactive entities that are not caused by an integration problem but a normal state. A dishwasher with an open door can’t be started. A Wallcharger cannot charge a car if the cable isn’t connected. Those situations are fundamentally different from connection problems, but share the unavailable state.

The result is that integrations like Wachtman need a huge list of exclusions because they would otherwise warn about dozens of entities that aren’t broken. If those entities are broken, there is no way to tell, because they are excluded.

It is also easier to write automations properly. For instance, if my car is in a state that it cannot be charged when sun is high, I give a notification. But when it is because the api is down, I want to start the wallbox anyway, because it might be connected and I just don’t know.

Happens with Home Connect, Miele, Wallbox, Skoda, …