Improved support for the Aqara DJT11LM vibration sensor

[gaetanb76]

Hello everyone,

I just bought this sensor and am encountering issues with value reporting: some information doesn’t match and other data are not integrated into Gladys.
The « Button click » information returns 3 values:

• Vibration

[pierre-gilles]

@gaetanb76

Which does not correspond to a Button click. It says « Action » here:

We call that « Button click » because indeed until now only buttons returned an « action » attribute

I don’t know if there’s any indication in the payload that would allow us to distinguish this sensor and know that « action » means something else in this case. @cicoub13 @_Will_71 any idea about this?

@gaetanb76

It would be nice to be able to adjust the sensitivity and the frequency of the vibrations directly in Gladys.

For now we’ve chosen not to put the settings in Gladys. Is that really necessary? Do you change these settings often?

[mutmut]

For my part, I’ve never used the « button click » nor needed to change the parameters anywhere else other than in z2m once. The sensor is mounted on my garage door to see if it opens, closes, or to try to retrieve a specific position (with the xyz), so I don’t need anything more.

@gaetanb76 what types of applications do you use it for?

[gaetanb76]

Opening of the mailbox by vibration detection.

@pierre-gilles

For the moment we’ve chosen not to put the settings in Gladys. Is it really necessary? Do you change those settings often?

No, I configure them at the beginning based on usage.

However, it’s not stated anywhere in Gladys’s documentation on Zigbee2mqtt that you can access the raw Zigbee2mqtt interface via the port. Which means the average user doesn’t know they can configure their hardware more finely.

And that’s understandable since Gladys is designed to be user-friendly.

That’s why being able to change the settings in Gladys would be a plus. It would avoid having to get your hands dirty.

[pierre-gilles]

@gaetanb76

However, nowhere in Gladys’ documentation on Zigbee2mqtt does it say that you can access the plain Zigbee2mqtt interface via the port. Which means that the average user doesn’t know they can configure their hardware more finely.

Yet it’s right there in the interface, accessible in one click :

@gaetanb76

That’s why being able to change the settings in Gladys would be a plus. It would avoid having to get your hands dirty.

I agree that it could be a plus; however, it’s work, and that work must be weighed against other requests.

Also, if you want, create a feature request

[_Will_71]

@pierre-gilles

I don’t know if there is any indication in the payload that would allow us to distinguish this sensor and know that « action » means something else in this case. @cicoub13 @_Will_71 any idea about this?

No, I don’t see anything that could help us in the payload returned by this sensor.

And in the doc there is only the info below

Here’s what one of my sensors returns:

Topic: zigbee2mqtt/Détection boîte aux lettresQoS: 0
{
  "action": "tilt",
  "angle": 62,
  "angle_x": null,
  "angle_x_absolute": null,
  "angle_y": null,
  "angle_y_absolute": null,
  "angle_z": null,
  "battery": 77,
  "device_temperature": 28,
  "last_seen": "2025-01-31T17:40:15.979Z",
  "linkquality": 72,
  "power_outage_count": 4264,
  "sensitivity": "low",
  "strength": 46,
  "vibration": true,
  "voltage": 2965,
  "x_axis": 0,
  "y_axis": 0,
  "z_axis": 0
}