Aqara vibration sensor resets sensitivity

Berger · September 22, 2023, 11:20am

Hello,

I’m using the Aqara vibration sensor (DJT11LM) on my windows to detect possible glass breaking. The sensors will then trigger my alarmsystem. To connect my Zigbee devices, I use the Raspbee II with the newest firmware/version.

After I discovered that some of my sensors generate false/positives, I adjusted the sensitivity using the REST-API with following command:

curl -H 'Content-Type: application/json' -X PUT -d '{"sensitivity": 1}' http://myIP/api/myAPIKey/sensors/3/config

When I check the sensitivity right after I’ve done the change using

curl -X GET http://myIP/api/myAPIKey/sensors/3

I get a sensitivity of 1 back. However, after a few days some of the sensors simply reset their sensitivity back to the default value (2 = very sensitiv). After a restart of my Raspbee II Gateway or my whole Raspberry Pi, every sensor gets resetted to the default value.

I read about the need to keep the Aqara vibration sensors awake by pressing the pair button before, while and after you change the sensitivity. I did that as well but it doesn’t seem to change anything.

I also noticed that whenever I use the deConz GUI via RealVNC Viewer, all my devices are missing in Home Assistant. They’re still available in Phoscon but they’re missing (greyed out) in Home Assistant.

Has anyone an idea on how to fix this problem?

Thanks for the help in advance!

Greetigns,
Berger

Smanar · September 25, 2023, 7:07am

Thee was a recent chnages on them Fix sensitivity for lumi_vibration_aq1 by ebaauw · Pull Request #7208 · dresden-elektronik/deconz-rest-plugin · GitHub, what is your deconz version ?

I read about the need to keep the Aqara vibration sensors awake by pressing the pair button before, while and after you change the sensitivity. I did that as well but it doesn’t seem to change anything.

Yes if you use the GUI, as you are using the API, it’s no a problem, deconz just wait for the device be awake.

I also noticed that whenever I use the deConz GUI via RealVNC Viewer, all my devices are missing in Home Assistant. They’re still available in Phoscon but they’re missing (greyed out) in Home Assistant

This is not normal, phoscon and HA are using the same API, so if the device is working on one, it need to work on the second one ?
When you say all your devices, routers too ?

bcutter · March 9, 2024, 7:13pm

Exactly the same for me. I have one lumi.vibration.aq1 with many false positives.

On 2024-03-03 I set the sensitivity to 0 (which is the lowest according to lumi.vibration.aq1). Two days later on 2024-03-06 the false positives are back. Since than many many ANNOYINGLY MANY false positives.

Now I checked the settings using a RESTClient:

  "96": {
    "config": {
      "battery": 92,
      "duration": 65,
      "on": true,
      "reachable": true,
      "sensitivity": 2,
      "sensitivitymax": 2,
      "temperature": 1500
    },
    "ep": 1,
...
    "lastannounced": "2024-02-23T17:38:36Z",
    "lastseen": "2024-03-09T18:46Z",
    "manufacturername": "LUMI",
    "modelid": "lumi.vibration.aq1",
...

What the… is going on here? This really bothers me on an every day basis - even multiple times a day. The vibration sensor triggers things which create real issues in case of false positives.

Vibration sensor 1:

  "61": {
    "config": {
      "battery": 98,
      "duration": 65,
      "on": true,
      "reachable": true,
      "sensitivity": -8,

Vibration sensor 2:

  "96": {
    "config": {
      "battery": 92,
      "duration": 65,
      "on": true,
      "reachable": true,
      "sensitivity": 2,

Vibration sensor 3:

  "97": {
    "config": {
      "battery": 95,
      "duration": 65,
      "on": true,
      "reachable": true,
      "sensitivity": 2,

I now did the same like I did on 2024-03-03: set sensitivity to 0 for all of them using below’s Home Assistant service [*1]. Let’s see how long this value will exist, currently according to the API all three are set to 0.

[*1]

service: deconz.configure
data:
  entity: binary_sensor.vibration_name
  data:
    config:
      sensitivity: 0

@Smanar: Shall we raise this as issue @ GitHub?

bcutter · March 9, 2024, 10:08pm

…aaaaand all of them have been reset. To their former values. Discovered using the API as one had a falsely trigger vibration just right now. It’s been only few hours! Less then 3 to be a bit more precisely.

What the hell…

Smanar · March 10, 2024, 2:11pm

There is a PR about negative value Fix negative value for sensitivity for Aqara/Xiaomi vibration sensor by Smanar · Pull Request #7618 · dresden-elektronik/deconz-rest-plugin · GitHub

And they are sleeper, so when you change a value in the API, can take long time for the device awake and deconz send the request.

You haven’t error message when (trying to) changing the value to 0 ?

If youi have the GUI you can too take a look direclty on the device

           "cluster": "0x0000",
           "attribute": "0xFF0D",

bcutter · March 10, 2024, 5:12pm

No error message. No idea if the issue is in deCONZ or the devices, but as this was working for years and I suspect recent update (deCONZ 2.25.3), I put my bets on deCONZ.

github.com/dresden-elektronik/deconz-rest-plugin

Sensitivity settings reset (not persistent) for lumi.vibration.aq1 after few hours

opened 05:10PM - 10 Mar 24 UTC

bcutter

Bug report

### Does the issue really belong here? - [X] I definitively want to report a bu…g within deCONZ or its REST-API ### Is there already an existing issue for this? - [X] I have searched the existing issues and there is none for the bug at hand ### Describe the bug After setting `sensitivity` and checking it has been set (using the API), after only few hours the `sensitivity` is reset. Not sure if it is related to https://github.com/dresden-elektronik/deconz-rest-plugin/pull/7208. This issue was likely introduced somewhere after deCONZ v2.22.2 (updated to v2.25.3 on 2024-02-10). ### Steps to reproduce the behavior 1. Set 'sensitivity' (using the API or the deCONZ service in Home Assistant) to e. g. `0` after it was `2` or `-8` before 2. Check it is actually stored using the API 3. Wait few hours (2 to 3) 4. Check sensitivity again and discover it has been reset to the previous value (like `2` or `-8`) ### Expected behavior Set `sensitivity` is persistent. ### Screenshots _No response_ ### Environment - Host system: Raspberry Pi - Running method: Home Assistent deCONZ Add-on - Firmware version: (26720700) - deCONZ version (not Home assistant Addon version!): (2.25.3) - Device: ConBee II - Do you use an USB extension cable: yes - Is there any other USB or serial devices connected to the host system? If so: Which? ### deCONZ Logs _No response_ ### Additional context See https://forum.phoscon.de/t/aqara-vibration-sensor-resets-sensitivity/3971

eweriuer · March 13, 2024, 10:58am

also I was wondering, is it normal that these Aqara vibration sensors are seen as “locks”? I see locks related tabs in deconz, see image attached

Smanar · March 13, 2024, 2:26pm

This is an information from the device firmware, you can found tuya covering described as smart plug.

bcutter · May 10, 2024, 5:44pm

Still no progress on this. This really sucks. Plenty of false alarms driving me nuts from time to time. How to persistently set the damn sensitivity of those devices with deCONZ ?!?

beatpaul · May 21, 2024, 6:18pm

I have the same problem with the vibration sensor, are there any workarounds available?
Thx
Paul

eweriuer · May 22, 2024, 10:36am

it’s one of the last outstanding issues for 2.27.0-beta release, based on the info that is in github: v2.27.0-beta Milestone · GitHub

but I am not sure this really means it’s going to be looked at.

eweriuer · May 28, 2024, 7:58pm

well now there’s a newer milestone, 2.27.3-beta, when 2.27.0-beta is still open with outstanding issues so I guess the use of milestones here is like the jungle and shouldn’t be trusted too much.

Mimiix · May 29, 2024, 3:50pm

There’s more pressing issues atm. There’s a issue with ddf loading causing it not to work.

I’ll let manup know the above so it doesn’t get forgotten.

bcutter · June 8, 2024, 5:58pm

Well, certainly, if your smart homes drives you crazy due to regular false alarms multiple times a day, you might have a different view on “pressing issues”.

Looking forward to see a fix, which will arrive in Home Assistant deCONZ addon until Christmas (2024, if lucky).

Mimiix · June 8, 2024, 6:54pm

Mine works like a charm

bcutter · June 8, 2024, 7:07pm

Lucky you. Wanna swap smart homes?

Not funny at all, really. You deCONZ guys break stuff with shipped updates - and afterwards don’t do anything to fix the broken stuff. Everything was running fine before. Freaking annoying!

Mimiix · June 8, 2024, 7:12pm

Its open source, feel free to contribute.

I do want to remind you to stay civil and constructive. Negativity doesn’t add anything to the conversation at hand

Other than pinging @de_employees there’s nothing I can do.

bcutter · June 8, 2024, 7:41pm

Yes, my PR would look like this: undo everything after v2.22.2 which was shipped with v2.25.3 and is related to this device.

If you’d know what issues that single issue creates in everyday real-life, you’d consider my behaviour as very civil and constructive.

So let’s sit and wait. I put my bets on Christmas. Prove us wrong. Please. Thanks.

manup · June 10, 2024, 10:23pm

Interesting case, when I read the code right. A 0 is written to the device when the sensitivity is set to 3. In which case 3 - 3 = 0 will be written. When the value is read back for validation it is set to 3 - deviceValue (0) which again verifies the 3.

So if I understand right the problem here might be that the value is exactly inverted from what one expects 3,2,1,0 instead of 0,1,2,3.

Given by the logic from current DDF:

Sensitivity (API)	Device value
3	0
2	1
1	2
0	3

beatpaul · June 26, 2024, 9:08pm

Hi Manu!
I cannot read nor write the sensitivity value in deconz with the attribute editor
It says „reading fails“ or „writing fauls“

The sensor in general works fine, just the high sensitivity is really anoying.

Thx for your support!!