Proposal: Do not use entity availability to indicate printer status

[EuleMitKeule]

I would like to propose a change to how some of the entities behave depending on the printers state. The button entities for example set themselves as unavailable in scenarios where a button press would not actually perform any action.
In my opinion, unavailability should not be indicated in such a case, since the printer is still available and no errors or problems are present, which is something an unavailable state indicates to the user.
There might be multiple solutions to improve this behaviour. One would be to simply move the checks from the available property to the button press callback and have the button just not do anything.

[AdrianGarside]

The unavailable state is specific to the entity in question. It doesn't tell you anything about the device. There are specific entities that allow you to track device availability.

Disabling buttons when they are unable to perform their task due to current state is a standard UX behavior.