Aqara Motion Sensor Hack for 5 sec

Configuration Zigbee
109

Can someone explain/show how to do it with a pencil? I don’t have any soldering equipment

110

Literally just draw a pencil line between the two points on the PCB. It works best with a softish pencil, but I used an HB pencil and just overdrew the line a couple of times to deposit enough graphite.

111

I have 2 aqara motion sensors. One of them resets at 5 seconds without any hardware modification, the other does not (I’ve set deconz.configure duration 5 for both). Weird

112

Are you sure it actually resets? From what I know, setting the deCONZ duration will make it send a “no motion detected” event after that many seconds regardless of whether the sensor is ready or not. So does the sensor trigger again after 5 seconds?

113

It does trigger again. I ended up setting a 15 sec delay in node-red, cause it was triggering too often.
The other one resets in HA, but does not trigger.
I checked and they both have the same firmware version, so I don’t know what’s the difference. Maybe one was from a test batch or something

114

Update: the second one works now on 5 seconds too, without me doing any hardware mod. I’ve just been tinkering with them in HA / deconz, pressed the side button once, I have no idea what changed.

  - service: deconz.configure
    data:
      entity: binary_sensor.office_motion_sensor_presence
      field: /config
      data:
        duration: 5
1 Like
115

For german spreaking - or at least understanding - people, I created a video about this topic (ZHA with hardware hack) on youtube. Enjoy: https://youtu.be/VIXZz9oy68w

Für deutsch sprechende bzw. lesende Leute habe ich zu dem Thema ZHA und Aqara Motion Sensor Hack ein Video erstellt: https://youtu.be/VIXZz9oy68w

2 Likes
116

so all of your sensors now work without the hardware hack? only with your automation?

117

Thats correct. No hardware hack, just the ‘reset’ automation. I was surprised as you are :slight_smile:

1 Like
118

But from what I see in your automation you reset the sensor state after 15 seconds: why?

15 seconds are much longer than the 5-seconds reset interval with the hardware hack: could it work also if you set the delay to 5 seconds in the automation? and without ghost re-activations?

119

So just add this to the config file? And change the entity field to the name of the motion sensor?

120

just tried a modded motion sensor with ZHA after using it succesfully with deconz. Used the ‘zha.set_zigbee_cluster_attribute’ reset automation but after a reset of status the sensor doesnt recognize motion after status is clear. It has the wait for 60 seconds after a retrigger can happen.
In deconz ig worked fine but with ZHA it looks like the motion sensor isn’t even modded.
I can put the sensor in test mode by push the button a single time. Then the sensor works for an hour like it should. But after an hour the sensor has the 60 sec retrigger wait. Very annoying as it works with deconz but not with zha

121

UPDATE: after trying an other aqara motion sensor it worked.
also checked the mod from the sensor that didn’t work and the electric paint didn’t make a good connection anymore so did the modification again.

122

UPDATE: Still works on ZHA with the service: zha.set_zigbee_cluster_attribute
no more ghosting.

123

Hi,

Do i need to change any values beside the entities?

124

Hi, I have to confirm post from krad23. It worked fine for me - add new automation to home assistant, then run it, then push the button on motion sensor once and shortly, and 5s interval is working well without any hardware hack. :wink:

So, the change is not permanent. In the evening, it worked well, but in the morning, it switched back to 60s. Anyway, 60s is still better than original 90s. And to be honest 60s is fully sufficient. For someone who needs less, HW hack is the only chance in combination with this SW fix working with deCONZ.

alias: Aquara motion sensor hack
description: ''
trigger:
  - platform: homeassistant
    event: start
condition: []
action:
  - service: deconz.configure
    data:
      entity: binary_sensor.motion_sensor_entrance_hall
      field: /config
      data:
        duration: 60
mode: single
127

This is a very late addition to this topic, but I thought, that my generic automation based on earlier comments might be helpful for some.
The advantage of this is that you can reset all motion sensors with a single automation, and each additional motion sensor is only 2 lines of code. (or one additional trigger in the UI):

- alias: Motion Generic Reset
  trigger:
  - platform: state
    entity_id: binary_sensor.motion_1
  - platform: state
    entity_id: binary_sensor.motion_2
  condition:
  - condition: template
    value_template: '{{ trigger.to_state.state == "on" }}'
  action:
  - delay:
      seconds: 5
  - service: zha.set_zigbee_cluster_attribute
    data:
      ieee: '{{ device_attr(trigger.entity_id, "identifiers") | first | last }}'
      endpoint_id: 1
      cluster_id: 1280
      attribute: 2
      value: '0'
  mode: parallel
  max: 10

So for each additional motion sensor, you just have to add these lines:

  - platform: state
    entity_id: binary_sensor.motion_x

The IEEE address is extracted using the new device template function introduced in release 2021.8.0

11 Likes
128

Thanks for this! I’m okay with the default behavior but this might be useful down the road.

129

Any chance you can share your flow to reset your sensor? Did you just add another call service node (after the events:state node that trigger when motion is detected) that resets the zha state as well?

1 Like
130

The best solution at the moment!

Danke!