I have two Aqara Motion sensors, and like @AlecM, when in normal mode the hardware is blind for 60 seconds after detected motion, not 120 seconds. All other user reports I’ve read here on the ST forums and elsewhere online show the hardware reset normally happens at 60 seconds.
The default of the DTH preference to reset motion before @ArstenA just changed it was 60 seconds, same as the hardware. It even says that in the text of the preferences. The code is written so that if the preference is left blank, it will still use a reset time of 60 seconds.
Did you re-pair the Aqara Motion sensor when you switched to the new DTH? As @AlecM mentioned, when the sensor is paired or if you short-press the reset button, the sensor will start a “test mode” which lasts for about 2 hours. During the test mode, the sensor hardware is only blind to motion for about 5-6 seconds.
I think the problem relates to the fact that the DTH doesn’t ignore any motion detected messages from the sensor during the countdown to the 60 second reset (or whatever the user entered in preferences.)
We could change the DTH so that even if the sensor is in test mode, the frequent motion detected messages are ignored, until the DTH countdown is finished and it resets with the “inactive” event.
@ArstenA / @AlecM - what do you think?
EDIT: I looked around again, and even in this (somewhat badly translated) Xiaomi device API document, it confirms the 1 minute hardware motion detection timeout:
Aqara human illuminance sensor:
Information will be immediately reported to a report when the human sensor detects the movement of
people have also report illumination value “lux” at the same time. In the case where people have been
moved, to conserve power, the human body sensor transmits a fastest one minute report. When the humanbody sensor of each heartbeat, also report the current illuminance value “lux”. In all other cases, it does not report the human body sensor light luminance value.