Aqara Light Switch H2

🧰 Built-In Apps and Drivers
1

Hi,
I'm trying to integrate a brand new Aqara Light Switch H2 with my Hubitat C-8. The H2 natively supports Matter over Thread and I have it linked to Apple Home and HE. I was able to pair the H2 with my C-8 but it only shows as a "Device". The model H2 I have has 4 buttons and 3 internal relays (these are linked to buttons 1-3 with the 4th button open for use in automations) so I can't just change the device type to Generic Matter Switch. Any hints on when support for H2 will be added or other ideas would be greatly appreciated.

Also, the protocol can on the H2 can be changed to Zigbee. This is designed for tighter integration with the Aqara ecosystem. One of the features of using Zigbee protocol is that you can disconnect the first 3 buttons with the relays. In this way the buttons can do anything and the relays simply controlled through automations. I'm told this can't be done with Thread because Matter doesn't support disconnecting. If there is any way to work around this limitation that would be great.
Thanks in advance for the help

2

@jbasen, did you ever find anything?

3

Unfortunately, no. I wasn't able to find a way for the C-8 to recognize the Light Switch H2 properly. The workaround for the 2nd problem was to connect the Light Switch H2 to an Aqara hub through Zigbee. The hub can then expose the Light Switch H2 to other ecosystems as a Matter device and you can then configure the Light Switch H2 to disconnect the first 3 buttons from the built-in relays.

Hope this helps

4

Switch 1 seems to work as a generic matter device. The ugly workaround i have been doing for unsupported additional endpoints is to create a virtual device in hubitat, expose it through the home kit integration and use automations on the apple side to sync the virtual switch with the aqara's different endpoints. the problem seems to be Hubitat isn't recognizing the additional endpoints in the data structure. Be nice to have a version of the generic driver which discovered the multiple endpoints.

5

Thanks @bruce.g.ramsay . That is an interesting workaround. A bit of a round-about solution but it would definitely work.

6

I created a driver for this switch, it's not perfect (2nd button just registers as a push but you can then create events for it)

/**

  • Aqara H2 US 2-Button 1-Channel Switch - Hubitat Driver
  • Supports: lumi.switch.agl004, lumi.switch.agl009
  • Tested with: H2 US 2-Button 1-Channel (lumi.switch.agl004)
  • Based on prestonbrown/hubitat-drivers (AqaraZigbeeDimmer.groovy)
  • GitHub - prestonbrown/hubitat-drivers · GitHub
  • ── How this driver works ───────────────────────────────────────────────────
  • The device exposes two separate Zigbee endpoints:
  • Endpoint 01 → top button (also controls the physical relay)
  • Endpoint 03 → bottom button (no relay — buttons only)
  • Button press events arrive on Zigbee cluster 0x0012 (Multistate Input),
  • attribute 0x0055. The endpoint tells us which button; the value tells us
  • the action: 1 = pushed, 2 = doubleTapped, 255 = held
  • The relay (switch on/off) is reported separately on cluster 0x0006.
  • Note: the bottom button does NOT have a relay — only the top button does.
  • ── Button numbers & how to automate them ───────────────────────────────────
  • Button 1 = top button → pushed / held / doubleTapped
  • Button 3 = bottom button → pushed / held / doubleTapped
  • (Button 2 is unused — the hardware skips it)
  • In Rule Machine or Button Controller, trigger on:
  • "Button 1 pushed" → top button single press
  • "Button 1 held" → top button press-and-hold
  • "Button 1 doubleTapped" → top button double press
  • "Button 3 pushed" → bottom button single press
  • "Button 3 held" → bottom button press-and-hold
  • "Button 3 doubleTapped" → bottom button double press
  • ── Child devices ───────────────────────────────────────────────────────────
  • This driver intentionally creates NO child devices. All button events and
  • the switch state are reported on the parent device. If Hubitat created child
  • devices before you assigned this driver, they can be safely deleted.
  • ────────────────────────────────────────────────────────────────────────────
  • Licensed under the Apache License, Version 2.0
    */
1 Like