The special casing of OnOff client clusters should likely be removed in preference to event entities

[elupus]

Currently there is a special logic at

zha/zha/application/discovery.py

Line 449 in 9fe8345

def handle_on_off_output_cluster_exception(self, endpoint: Endpoint) -> None:

that converts a OnOff output (client) cluster into a virtual server cluster through a handler. It will generate attribute updates based on the commands generated by the client cluster.

I assume this logic stems from before we had event entities in home assistant and was some type of attempt to create a binary_input like entity from an OnOff client cluster.

We should add support for event entities for output clusters, and drop this rather confusing special logic for OnOff clusters.

[puddly]

Any sort of virtual clusters need to go, in my opinion. They were created to re-use the existing cluster handlers to create entities. With the ZHA library allowing direct entity creation, we need to start replacing virtual clusters with those.

[elupus]

In this case it's not virtual clusters, it's a virtual entity linked to a handler. The clusters are real here.

[elupus]

The attributes on the cluster is virtual thou.