Also, the folks that have gotten Xiaomi / Aqara devices working with the DeCONZ Rest Plug-in are very close to getting the Aqara-Opple switches working for them. See this (long!) thread for more details:
I have posted to ask for clarification, but I believe the solution to the groupcast issue is probably to make a "fake"/empty group owned by the coordinator (hub) that the switch's binding is assigned to (instead of the "all devices" group). and the solution to disable the broadcast messages that affect all bulbs / switches is to configure the Aqara-Opple button to create bindings from the On/Off and Level Control clusters to a specific ZigBee group. Then the coordinator would need to be set up look at the state of that group as a switch itself that can then be used to triggers for automations.
The problem is that this scenario is much like what is needed to get the IKEA 5-button "steering wheel" remote working on the Hubitat Hub, and that is never going to happen:
Original explanation from July 2018 of how the IKEA 5-button remote uses groupcast messages:
Declaration of no support for the IKEA 5-button remote in April 2019:
Since the Aqara-Opple switches only use groupcast messages seem to always send groupcast messages in addition to reports to the coordinator (hub), I am going to guess that they also will not work with the Hubitat Hub, and won't be supported.
