I’ve now got a house full of Light Switch H2 (US variant, but I’m in AU). I’ve noticed there’s a delay between clicking a button and when the event is received! All my other ZigBee devices are effectively instantaneous, so I think this could be a firmware bug with these H2 switches.
I’ve got them in ZigBee mode, the relay buttons are decoupled and the wireless buttons have multi-click enabled. I’ve noticed that if I set the relay switches to directly drive the relay, that clicks on and off instantly! There is still a delay in receiving the click event though.
Has anyone else experienced this? If it’s widespread, can we get a firmware update to rectify this? Having all my lights turn on on a delay is not ideal 
2 Likes
Hi there, it looks like you’re experiencing a support-related issue. We’ve automatically created a support ticket for you and will reach out via the forum email within the next two business days.
If other members have any suggestions or insights on this topic, feel free to share!
The multipress mode for the wireless switch I noticed adds a significant delay. This is stated under the settings when you turn that mode on. I do wish it was a bit faster in decoupled mode. When I add these switches to Z2MQTT the buttons trigger alot faster than they currently do via Matter.
Multi-press mode for the wireless button slowing down decoupled buttons definitely sounds like a bug 
I’ve got some 2 button 2 channels that are also slow though, so I don’t think that’s necessarily the issue
Hello, what are you turning on with the H2 switch? There may be a delay due to automation for the smart lamp.
1 Like
I thought that might’ve been the case originally - I’m controlling mains-powered downlights. I’ve ruled that out though, since the lights respond with no perceivable delay when I manually control them, or when I manually trigger the automation. I can see a noticeable delay between me clicking the H2 button and the event appearing in history too
In the automation of switching on, the first action is to set the function “On”, this helped me (THEN). The next step can be adjustment or mode selection.
Hi there, as this issue has already been resolved with our support team via email, we’ll be closing this topic on the forum as well. If you have any further questions or run into any other issues, please feel free to reply directly to our support email. Thanks for your support and understanding!
The issue has not been resolved, please disregard this. Support needs logs, and I’m not home to reconnect devices to get them access to that for a while.
Alright so we finally came to a resolution - TL;DR there is a built-in debounce on the switch buttons. This means you will receive all button click events on a short delay, and there is no way around it.
It’s been a long back-and-forth with Simone from Aqara support! About a month in I picked up an Aqara Hub M100 to connect a switch to their ecosystem for debugging. The first 2 months went pretty well I’d say! Solid conversations, new discoveries and frequent updates. Unfortunately I started getting the same “oh it’s just standard network delay and other processing” at some stage, and after a miscommunication that looped in the distributor my thread was abruptly closed with a similar “network delays and other processing” message (though this is where debounce was mentioned).
Thanks to Simone for helping to troubleshoot this! Even if the thread was closed off so abrubtly, you did still end up sharing the actual cause in amongst the noise.
1 Like
Thank you for updating us on this issue!
@Cifer_Aqara do you have any additional idea on that?
I do have one final update here - someone with EU switches (and more testing capacity than me) has done a decent write-up on Reddit. The conclusion is this is indeed built-in software delays for button press reporting in ZigBee mode only.
Ref: https://www.reddit.com/r/Aqara/comments/1maus6t/h2_eu_4_buttons_switches_slow_response_in/
As harsh as their conclusion is, I’d have to agree. I quite enjoy my switch hardware, but based on the software experience I would not recommend these to anyone, nor will I be considering Aqara devices moving forward (which is unfortunate, their sensor-only devices have been solid so far).
Thanks all who helped look into this!