Same issue with Aqara H1 Wireless Switch via Zigbee direct to Homey Pro Mini
I have an Aqara H1 Wireless Switch connected via Zigbee directly to Homey Pro Mini (without Aqara M3 hub). The buttons do not send any event to Homey:
Note: I have an Aqara H2 EU with the same issue via Zigbee direct. The H2 EU works correctly when connected via Matter over Thread or via Zigbee through the Aqara M3 hub.
It seems Zigbee direct to Homey does not work correctly for Aqara wireless switches (H1 and H2). Is there a fix planned?
You might want to check the first post of the Aqara app for Homey topic (linked below), if your specific model/product ID is supported (you can find de ID in the Advanced Settings section of the device tile). If not you can contact the developer via that topic to request support for your specific model.
Hi ,
Thank you for your reply. I checked the Advanced Settings and my device is the Light Switch H2 EU (4 buttons).
I can confirm the device is recognized and added to Homey correctly. However I want to clarify several specific issues I have experienced:
1. Double press not available as trigger When connected via M3 (Matter) or Zigbee direct to Homey, double press and long press are not available as trigger options in Flows — only single press appears.
2. Decoupled button does not work via Zigbee direct When connected directly via Zigbee to Homey Pro Mini (without M3), the decoupled buttons do not send any events at all — nothing appears in Flow history when pressing them.
3. Decoupled button via Matter is unreliable for daily use When connected via M3 (Matter over Thread), the decoupled buttons work sometimes but with significant issues:
-
Noticeable delays on button press — making real-time control very frustrating
-
Frequent missed presses — the trigger simply does not fire
-
The response is too inconsistent and unreliable for smooth daily use
All of these issues make it very difficult to use the H2 EU decoupled buttons reliably in Homey, regardless of the connection method used.
Could you confirm if these are known limitations or if there are planned improvements?
Thank you very much for your time and support!
I personally cannot, as I don’t have this device myself. Maybe other forum users can help out. Alternatively, as indicated in my prior post, you may want to contact the developer.