You are using deconz ?
If you try to awake the device in same time, same result ?
The value needs to be written via REST-API (which also takes care to transmit as soon as the device is awake) otherwise it can be reverrted later on.
I tried to awake the device by moving de sensor and or pressing its button and trying to write the new sensitivity value via deconz short after, but that didn’t do the job…
I even took out the battery and tried it after putting it in again…
I’m not really familiar with using the REST-API MANUally ( 
) is there another way or maybe will there be a bugfix?
thx for your help
I m trying to do both action in same time, but your procedure is fine for me, you are trying to set “0” instead of “1” ?
Yes I try to set sensitivity to low.
Right now the sensor reacts way to often what really is annoying.
Sorted out on your side @beatpaul ?
Mine are still driving me nuts so I had to basically disable them completely. Better to get no notification at all than multiple false alarms every day.
Same for me, no progress
Although i have one sensore that works → i think sensitivity was set ages ago and i didnt change it, it keeps the setting
No chance for the other aqara sensor to set sensitivity… i turned it off 
What a pity. As mentioned, that was working totally fine in the past. A deCONZ update seems to have changed the behavior in a way as this issue did not appear in the past.
Too bad no one really cares.
Another device being unusable with deCONZ. The list is growing
If I read this topic correctly, the device acts oddly and the value needs to be set with the rest API rather than with deconz directly. @beatpaul isn’t familiar with the Api so he doesn’t know how.
Did you (@beatpaul ) in the end try with the rest API?
Hi everyone I took my sensor out of the box and did some tests to verify what is written to the device and what happens to API values.
There was indeed a bug in the DDF that prevented setting low sensitivity. Also the GUI cluster attribute view was wrong due a duplicated attribute.
The fixes are now in PR https://github.com/dresden-elektronik/deconz-rest-plugin/pull/8135
Related earlier issue to clarify the values https://github.com/dresden-elektronik/deconz-rest-plugin/pull/7208 and that Aqara hub is also just using values 1, 2, 3.
So with the new DDF the following values can be set via REST-API
0 low sensitivity
1 medium sensitivity
2 high sensitivity (default configuration)
Note that the sensitivity attribute (0xFF0D) on the device is written inverse. This can also be done via deCONZ GUI :
3 low sensitivity
2 medium sensitivity
1 high sensitivity
Any out of bound values will be corrected automatically.
2 Likes
Thx for the solution, i will give feedback as soon next stable release is published and changes are availible
Thx
Thanks, you can also install the new DDF with the fix in current versions by downloading following zip file https://github.com/dresden-elektronik/deconz-rest-plugin/actions/runs/13766572214/artifacts/2722631138
And upload it in the Phoscon App under “menu → Device integration”
(might need to restart deCONZ after that to make it pickup the new DDF)
Note once the new DDF is in place you need to set the sensitivity again either via REST-API or in the deCONZ GUI cluster view.
1 Like
Thx! i will try it as soon as i am home
It worked 
After importing the ddf and restart deconz
First it seemed to not read or write any values, after checking again after some time the new sensitivity value was set
Thx 
2 Likes