Same H2 action, different commands in Aqara and HomeKit

Hi,

I have a Bulb T2 and a Shutter Switch H2, both in Zigbee mode and connected to my Hub M3. The H2 is configured in multi function mode and is available in both Aqara Home and Apple Home.

I can therefore configure the same H2 button action differently in each platform.

For example:

Long press on the upper button in Aqara: increase Bulb T2 brightness
Same long press in Apple Home: set Bulb T2 brightness to 100%

What happens in this case? Does the Bulb T2 receive both commands? If so, how are two different commands triggered by the exact same button action handled?

The long press is just an example. My question is more generally about using different Aqara and HomeKit actions for the same H2 button event.

Thanks!

1 Like

@awax_38 Great question! This is a really common point of curiosity when diving into dual-platform setups with Aqara devices.

From what we know about the Shutter Switch H2 EU in Zigbee mode, it supports single press, double press, and long press as distinct automation triggers within the Aqara Home ecosystem. When you pair it with HomeKit, those same physical button events become exposed to Apple’s automation engine as well.

Here’s the thing: both platforms can indeed “hear” the same button event simultaneously. The switch itself doesn’t know or care that you’ve set up two different automations on two different platforms—it just reports “long press on upper button” to the hub, and the hub broadcasts that event to both Aqara Home and HomeKit.

So in your specific example, yes, the Bulb T2 would receive both commands—the incremental brightness increase from Aqara and the “set to 100%” from HomeKit. Typically they’d fire nearly simultaneously, and the result depends on execution timing and how the bulb handles rapid successive commands. You might see it jump to 100%, or you might see a brief flicker as both commands process.

My practical take? This overlap usually creates more chaos than value. Most folks I know pick one “master” platform for each device’s automations to avoid conflicts. Aqara Home tends to offer more granular control for Aqara-native gear, while HomeKit shines for broader ecosystem scenes.

If you’re set on mixing, you could also explore using virtual switches or dummy automations as intermediaries—though that’s admittedly more hacky than elegant.

Have you actually tested this yet and noticed any weird behavior with the Bulb T2? Would love to hear what you’re seeing in practice