Well thank you for all of the log output! It’s helpful and appears to correspond to information I have found from various sources online (including the two links I listed above).
I have decided to buy two of the Aqara Vibration sensors, but of course since they are shipping via e-Packet from China to me in Oregon, U.S.A., it will probably take 2-4 weeks.
After reading all of the current information people have discovered about this sensor (and not all aspects have been determined), it’s quite clear that I will need to have one that I can connect to my SmartThings hub to do testing and debugging. If anyone is interested in loaning me one of theirs while I wait for mine to arrive, it would help speed up the process of developing a DTH! If you cover shipping to me I will pay for return shipping!
This is an important thing to decide about the DTH. The people on the deCONZ plugin GitHub discussion thread (in the link I gave previously) are also talking about how to implement the 3 different functions of the sensor.
On the SmartThings platform, in the device handler (DTH) the functions of any device have to be linked to one or more SmartThings Capabilities. Sometimes it’s pretty obvious: A button’s functions are linked to the Button Capability. A smart bulb is linked to the Bulb Capability. Then when something happens with that device that lead to the DTH receiving a message, the DTH generates an Event linked to the Capability. Almost all SmartApps (with the notable exception of WebCoRE) only recognize Events associated with official SmartThings Capabilities.
So in the case of this sensor, the vibration function could be linked to the Acceleration or Motion Capabilities – or possibly allow either, chosen by the user, as the Vison Shock Sensor DTH does (but that is quite complex and I’d need permission from the author to use some of his code).
If the vibration function is linked to the Motion Capability, then it would make sense to link the tilt function to the Acceleration Capability, and (if usable) also assign the X, Y, Z values the sensor sends to the 3-Axis Capability (though this Capability is only supported by the SmartThings Classic app, and there’s no information on whether it will be supported when custom DTHs are supported by the new SmartThings app.)
Finally, the fall/drop detection function needs to be linked to yet another Capability. This is tricky because there isn’t any obvious Capability for that type of event. I’d suggest linking it to the Button Capability, because it works just fine as a trigger in SmartApps.
These are just suggestions of what Capabilities to link to the three functions of the sensor, though. The button Capability could be linked to both fall/drop and tilt events, since the Button Capability allows for multiple button numbers on a device (e.g., tilt = button 1 pushed, and fall/drop = button 2 pushed).
There’s no guarantee it will work for that use case. It’s going to take a while to build a finished DTH and then you’ll just have to try it…