Aqara vibration sensor DJT11LM not paired correctly anymore, reports incorrect state

[Finne75]

Describe the bug

After upgrade to 2.15.3, my two Aqara vibration sensors stopped working correctly. The first one I re-paired, the second I left in the network. Following observations:

• Both always report "vibration": true on API level
• The re-paired one is missing cluster attributes, specifically the Xiaomi-specific ones (Xiaomi Sensitivity, Xiaomi Disconnect, and also Xiaomi Special attributes on 0101 Door Lock cluster)
• Both still report vibration strength, tilt angle, and battery correctly
• Creating a new DDF for the newly paired sensor does not work because I cannot bind the Xiaomi-specific attributes.
• I tried various options in the control panel (with all DDF, without, hybrid, ...) but no effect.

Steps to reproduce the behavior

1. Update to deCONZ 2.15.3
2. Get API output
3. "vibration": true is always reported
4. Re-pair vibration sensor
5. Click on Basic (0000) or Door Lock (0101) Cluster
6. Several Attributes are either missing (Basic Cluster) or greyed out (Door Lock Cluster)

Expected behavior

Vibration detection should behave like expected.

Screenshots

Basic Cluster of the newly paired sensor. Xiaomi-specific attributes are missing:

Xiaomi-specific attributes are greyed out in Door Lock Cluster:

Environment

• Host system: Raspberry Pi)
• Running method: Home Assistent deCONZ Add-on
• Firmware version: 26720700
• deCONZ version: 2.15.03
• 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

Additional context

[Finne75]

It works again. I think the following happend: the newly paired sensor was not fully paired (weird - I used all the usual "Xiaomi-tricks"). After some time, the missing cluster attributes appeared, but the sensor still didn't work as expected. I assume that the reason for the malfunction was is that I activated "Bronze" DDFs because I did some tests with some other devices, and as a consequence this incomplete DDF aq1_vibration_sensor.json was used. After de-activating Bronze DDFs, the devices seem to behave as expected again.

Lesson learned: do not submit bug reports before not excluding all possible other reasons. I think this can be closed.