in the community multiple blueprints were posted already for zigbee2mqtt related to the Müller tint remote.
- the quirk for this remote: zha-device-handlers/zhaquirks/mli at dev · zigpy/zha-device-handlers · GitHub
- the remote at blakadder: Müller Licht Tint Remote Control (404011) Zigbee compatibility
Since I am using ZHA, I was checking the events, which were thrown by the remote and documented all of them over here: GitHub - SimpleUserHA/MuellerTintRGBRemote
Does it somehow make sense to wrap some of those parameters and data into the zha quirk, to make button presses easier available and accessible for a wider range of users who don’t want to deal with such low level kind of event parameters?
(sorry I might still not get 100% the scope of those quirks and how far they should go by wrapping low level parameters to make features & functionality available on a higher level)