ZHA - Aqara Wireless Remote Switch (Double Rocker)

Blueprints Exchange
, ,
62

just got this blueprint working with a WRS-R02 directly connect via ZHA in HA. Did had to change the commands in the blueprints after listening to the events as liviumac stated.

These are the commands for the 1st button that are working for me that i adjusted in the my locally saved blueprint:

    - '{{ command == ''1_single'' }}'
    sequence: !input button_single_press_left
  - conditions:
    - '{{ command == ''1_double'' }}'
    sequence: !input button_double_press_left
  - conditions:
    - '{{ command == ''1_hold'' }}'
    sequence: !input button_long_press_left

Before using this blueprint i followed this instruction and installed the custom quirck to get the device working properly.

64

I have the same issue, can anyone help?

65

These steps are only tested with the wireless switch (lumi.remote.b28ac1)

When you use the zha event listener
(Developer tools > Events > Listens to event fill in zha_event and start listening)
Do you get single press events even when you double triple press or hold?

If so,

Do the following
1: Home Assistant > Configuration > Devices & Services > Zigbee > Click on your Aqara H1 switch
2: Click next to reconfigure on the 3 dots > Manage zigbee device
(Make sure on Clusters that AqaraRemoteManuSpecificCluster (endpoint id:1, Id: 0xfcc00, Type: in) is selected
3: Select on attributes click_mode (id 0x0125)
3.1 value fill in 2
3.2 fill in Manufacturer code override 4447
Write attribute (if its fails make sure that you press the Aqara button 5 times in quick succession to get it out of sleep mode)
3.3 Select on attributes operation mode (id: 0x0009)
3.4 value fill in 1
3.5 fill in Manufacturer code override 4447
(Same story if its fails make sure that you press the Aqara button 5 times in quick succession to get it out of sleep mode)

Now that’s done go back to the ZHA listener and verify that double pressed etc is registered.

Example when i double press:

event_type: zha_event
data:
  device_ieee: 54:ef:44:10:00:5b:72:27
  unique_id: 54:ef:44:10:00:5b:72:27:1:0x0012
  device_id: 9896c458eda01ab2a47a378ced521bd7
  endpoint_id: 1
  cluster_id: 18
  command: 1_double
  args:
    button: 1
    press_type: double
    attr_id: 85
    value: 2
  params: {}
origin: LOCAL
time_fired: "2024-03-08T21:10:46.620538+00:00"
context:
  id: 01HRFYEXJW7WJT03EAJ09377T1
  parent_id: null
  user_id: null
2 Likes
66

Thanks, it was working perfectly, until it brokes with 2024.8.2. It looks like the “pressed” condition do not work anymore. I don t know why. I fall back to 2024.7.4 and it works again.

67

You can fix it by updating the Blueprint. Open the Blueprint in Visual Studio Code and change.

trigger.event.data.args.value

to

trigger.event.data.args.attribute_value

Make sure you do it three times for right, left and double click.

Do a quick reload/restart of HA and you should be good!

68

Hi

I’m new to HA, but have successfully configured a few ZHA devices. I have just purchased a couple of Aqara H1M two-rocker remote switches from Aliexpress, so i assume these are Chinese region variants.

I can pair the switch, but like some other posts on here, i get only battery: unknown and identity: press

I attempted to tweak/hack the custom quirk referred above to suit the device (lumi.remote.acn009) but no luck.

I could really use some help to get this working (quirk, blueprint, ?) for this device. Full device Signature is:

{
 "node_descriptor": {
   "logical_type": 2,
   "complex_descriptor_available": 0,
   "user_descriptor_available": 0,
   "reserved": 0,
   "aps_flags": 0,
   "frequency_band": 8,
   "mac_capability_flags": 128,
   "manufacturer_code": 4447,
   "maximum_buffer_size": 66,
   "maximum_incoming_transfer_size": 66,
   "server_mask": 10752,
   "maximum_outgoing_transfer_size": 66,
   "descriptor_capability_field": 0
 },
 "endpoints": {
   "1": {
     "profile_id": "0x0104",
     "device_type": "0x0000",
     "input_clusters": [
       "0x0000",
       "0x0001",
       "0x0003",
       "0x0012",
       "0xfcc0"
     ],
     "output_clusters": [
       "0x0003",
       "0x0006",
       "0x0019"
     ]
   },
   "2": {
     "profile_id": "0x0104",
     "device_type": "0x0000",
     "input_clusters": [
       "0x0012"
     ],
     "output_clusters": [
       "0x0006"
     ]
   },
   "3": {
     "profile_id": "0x0104",
     "device_type": "0x0000",
     "input_clusters": [
       "0x0012"
     ],
     "output_clusters": [
       "0x0006"
     ]
   }
 },
 "manufacturer": "LUMI",
 "model": "lumi.remote.acn009",
 "class": "zigpy.device.Device"
}

Thanks in advance to anybody with some ideas to try.

69

Hey david,

My specific Aqara also had issues with applying the quirk for it to function properly.
(my specific one required zhaquirks.xiaomi.aqara.remote_h1.RemoteH1DoubleRocker2)
(You can check the quirck > Settings > Devices > the aqara switch > Zigbee info > then it shows quirk: xxxx for example zhaquirks.xiaomi.aqara.remote_h1.RemoteH1DoubleRocker2)

If it shows battery unknow ect, you could try to following:
Remove the device from home assistant (restart home assistant not 100% if its necessary but that worked for me. If i did not restart, but you try reload but that was months ago so that may have been fixed by home assistant or zha by now) press the button Aqara button 5 times in quick succession to get it out of sleep mode and then repair in to home assistant and test.

With mine lumi.remote.b28ac1 it took a few tries before it took the correct quirk.
As mentioned earlier i am not sure if that works for your specific version.