Aqara vibration sensor resets sensitivity

Smanar · June 27, 2024, 4:24pm

You are using deconz ?
If you try to awake the device in same time, same result ?

manup · June 28, 2024, 10:47am

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.

beatpaul · June 30, 2024, 11:51am

Hi @manup and @Smanar

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

Smanar · June 30, 2024, 2:27pm

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” ?

beatpaul · June 30, 2024, 3:44pm

Yes I try to set sensitivity to low.
Right now the sensor reacts way to often what really is annoying.

bcutter · March 9, 2025, 1:11pm

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.

beatpaul · March 10, 2025, 6:17am

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

bcutter · March 10, 2025, 11:10am

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

Mimiix · March 10, 2025, 11:19am

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?

manup · March 10, 2025, 2:18pm

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.

beatpaul · March 12, 2025, 6:14am

Thx for the solution, i will give feedback as soon next stable release is published and changes are availible

Thx

manup · March 13, 2025, 10:47am

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.

beatpaul · March 13, 2025, 11:48am

Thx! i will try it as soon as i am home

beatpaul · March 14, 2025, 10:28pm

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

bcutter · April 8, 2025, 1:15pm

Imported the DDF now too and set the sentitivity using the API (by a service call from Home Assistant, as usual), checked with Phoscon /pwa/debug-api.html. For now:

the sensitivity level shown is the one set → interesting if this really finally is permanent now
I also discovered all deCONZ provided entities in HA rendered unavailable and slowly come back, known behaviour for every deCONZ addon restart (likely triggered by the DDF import via Phoscon, which I used for the first time)

Maybe @beatpaul can return back if this is permanently solved now.

Edit: Not sure if this is really solved. A few hours later (had the Phoscon API tab still opened) I refreshed the sensor and well… where there was a "sensitivity": 0, before, now there’s (again) a…

I did not restart deCONZ yet.

beatpaul · April 9, 2025, 7:54pm

For me the changes work
Althoug it took serveral tries to wake up the sensor and st the sensitivity

bcutter · April 17, 2025, 10:48am

For me it did not. I set the sensitivity, confirm the new one is accepted checking via API Information and trigger the vibration sensor (I don’t need to push the physical button on the sensor right?). Later on (don’t know how long it takes, e. g. I set it yesterday evening and checked it now): back to normal:

I set it to 0, now it’s 2 again. For me nothing has changed after importing the DDF.

When checking the DDF vor a affected vibration sensor, I get this:

Does the filename (/bundles/................ddb) match the manually imported DDF file? That’s the first thing I wanted to check.

bcutter · April 24, 2025, 9:09pm

Updated deCONZ to latest v2.29.5 yesterday and therefore restarted the addon/container. Sensitivity seems to be stable now (finally accepted the DDF I guess, shipped with stable).

BUT now…: