Yes. There was no sense in building a beta device handler for both platforms simultaneously, but now that the one for ST is working quite well, I will work on porting it over to Hubitat.
Sorry for not having the video done. Had some family issues that happened. . Hope to have the videos up soon.
Just received my Aqara vibration sensor. Pairing with a V2 hub was fairly easy, took a few tries. Paired as a “Thing” the first time. Connection stable over the last week. I am really impressed with the beta driver (0.91b). Interesting, I did not get the “Sensitivity Level” reading until today. Did something change? Also, there is no “Battery Level” reading, but that’s fine. Thanks for all the hard work, guys! Still thinking of ways to use the device, which is really neat for the price. I also have several Temperature and Humidity sensors. Would love if the two sensors could be combined.
If the Device Handler (DTH) was installed before pairing the sensor, then it should have been automatically recognized and not have appeared as a Thing. Did you install the DTH first? If not, I’d be very interested in knowing your sensors device data and raw description, which can be found in your hub’s SmartThings Groovy IDE, by navigating to the My Devices page, and then clicking on the name of your Vibration Sensor in the Display Name column. For example, the Data and Raw Description for my vibration sensors looks like this:
I still have not been able to get the sensitivity level command working. Because the sensor does not send the current hardware value of the sensitivity level when requested, the device handler has no way of knowing what it is set to. So what I did was to send the command to set the sensitivity level to “low” when the sensor is paired. But because your sensor paired as a “Thing” that did no get set up correctly. It is also supposed to check if it’s not yet set up when the “save” button in the preference settings window for the sensor in the SmartThings Classic mobile app, so perhaps that’s what you did to get the setting to appear in the UI.
Either way, it doesn’t matter much, because the sensor doesn’t seem to be receiving the command to change the sensitivity level anyhow. I am not sure if this is an issue with the SmartThings platform, and it’s especially difficult to troubleshoot without any confirmation message sent back from the sensor.
I’m not sure why this would happen. I would need to see a few hours of debug log output from your sensor to figure out why. To do this you’d need to enable the display of info and debug log messages in the preference settings for the sensor in the SmartThings Classic mobile app, and then leave open the Live Logging page of the IDE for a few hours. Finally click on the name of the vibration sensor at the top of the Live Logging page to filter just the log output for it, and copy the log output you see to paste here.
Here’s a screenshot and text of log output for the check in / battery voltage message received from one of my vibration sensors:
Log output (click arrow to reveal)
132e6b88-91c8-4337-a2c1-3db4d166dc04 9:48:00 AM: debug Aqara Vibration Sensor 1: Creating event [name:battery, value:100, unit:%, isStateChange:true, descriptionText:Aqara Vibration Sensor 1: Battery at 100% (3.025 Volts)]
132e6b88-91c8-4337-a2c1-3db4d166dc04 9:48:00 AM: info Aqara Vibration Sensor 1: Battery at 100% (3.025 Volts)
132e6b88-91c8-4337-a2c1-3db4d166dc04 9:48:00 AM: debug Aqara Vibration Sensor 1: SmartShield(text: null, manufacturerId: 0x115f, direction: 0x01, data: [0x01, 0xff, 0x42, 0x2e, 0x01, 0x21, 0xd1, 0x0b, 0x03, 0x28, 0x15, 0x04, 0x21, 0xa8, 0x13, 0x05, 0x21, 0x1d, 0x00, 0x06, 0x24, 0x01, 0x00, 0x00, 0x00, 0x00, 0x08, 0x21, 0x08, 0x03, 0x0a, 0x21, 0x00, 0x00, 0x98, 0x21, 0x14, 0x00, 0x99, 0x21, 0x0f, 0x00, 0x9a, 0x25, 0x03, 0x00, 0xdd, 0xff, 0x98, 0x04], number: null, isManufacturerSpecific: true, messageType: 0x00, senderShortId: 0xb8a0, isClusterSpecific: false, sourceEndpoint: 0x01, profileId: 0x0104, command: 0x0a, clusterId: 0x0000, destinationEndpoint: 0x01, options: 0x0100)
132e6b88-91c8-4337-a2c1-3db4d166dc04 9:48:00 AM: debug Aqara Vibration Sensor 1: Parsing ‘catchall: 0104 0000 01 01 0100 00 B8A0 00 01 115F 0A 01 01FF422E0121D10B0328150421A81305211D0006240100000000082108030A2100009821140099210F009A250300DDFF9804’
132e6b88-91c8-4337-a2c1-3db4d166dc04 9:21:56 AM: debug Aqara Vibration Sensor 1: Debug message logging enabled
132e6b88-91c8-4337-a2c1-3db4d166dc04 9:21:56 AM: info Aqara Vibration Sensor 1: Info message logging enabled
132e6b88-91c8-4337-a2c1-3db4d166dc04 9:21:56 AM: info Aqara Vibration Sensor 1: Set health checkInterval when preferences updated
132e6b88-91c8-4337-a2c1-3db4d166dc04 9:21:56 AM: info Aqara Vibration Sensor 1: Refreshing UI display
132e6b88-91c8-4337-a2c1-3db4d166dc04 9:21:56 AM: info Aqara Vibration Sensor 1: Updating preference settings
You mean combine the hardware of the two sensors? Only Lumi United, who manufactures Aqara devices, would be able to do that.
I will try to answer the various parts.
Pairing as Thing.
Yes, the DTH was installed first. All I did was delete the item when it paired as a “Thing”, and re-paired it, and it was recognised as the correct object. I had to pair it several times, so I am not exactly sure when it first paired, or when it successfully paired. But it’s working fine now. I will look for the data, and post it once I find.
Not Seeing the Sensitivity Level
This is a bit funny. It take a week for the Sensitivity Level to show up in the GUI of the Classical app. Not sure why, but, as you say, not too important.
Not Seeing the Battery Level.
I checked in the IDE web site, the sensor is sending the information, but it is not showing up in the GUI of the Classical App. Should it?
I understand only the manufacture can do this. Just thinking out loud. But it would be a killer sensor.
Thanks for your reply and your insight.
Guys anybody having issues with getting push notifications for this vibration sensor, got it at all setup and its picking up vibration with no issues at all but for the life of me I cannot get any push notiifications at all. Tried the exact same way on my original samsung sensor and gives me push notifications with no issues at all.
Is there a way to adjust the level at which the vibration sensor triggers an alert? Currently, a much higher activity level than I desire is required to trigger an alert using a custom rule in the Smart Home Monitor, which monitors for vibration.
If this belongs in another thread, please direct me to it if you know which thread is appropriate.
There is a way to change the sensitivity level, but I have only just figured out how to implement it in SmartThings and need to rework the code of the SmartThings device handler I created. Are you using that device handler (DTH), which is part of the bspranger/Xiaomi GitHub repository?
The current version of the DTH displays a tile with the sensitivity level that is changed when pressed, but it’s not yet implemented. Basically, what needs to happen is a correctly formatted message to change the sensitivity level is sent to the Vibration Sensor, and then the user must short-press the reset button for the level change request to complete. Finally the Vibration Sensor sends a confirmation message. I am working on new code to handle all of that in a graceful way.
If you are using my DTH or any others in the bspranger/Xiaomi collection, then it would be better to post in this thread.
If you’re not using my DTH, then what are you using? I could direct you to the right thread to ask.
Just saw this post. Mine doesn’t trigger push notifications either. All other sensors do. Have you gotten this to work?
I’m set up with a Xiaomi Hub, latest firmware for Europe.
Just checking on whether the current version of DTH is working well? If yes, would be great if someone could provide the link to the latest version. Thank you.
I use bspranger DTH mentioned above, works well for me.
In the app, go to the device and just press on the sensitivity level box. It will cycle through low/medium/high.
Can you share the dth that can be used to change the sensitivity level brute force,the way you described it (plus additional instructions)?
Has anyone been able to get push notifications to work with these aqara vibration sensors? I also can’t get it to show up in webcore as device either. Vibration sensor has worked fine for past 6 months but would like to get push notification or Alexa voice via echo speaks action if possible.
Is this sensor available on Amazon?
If so, which?
I’m curious how well this might work to sense vibrations on a patio door sliding screen? I have a cat that recently took up residence with us, and her preferred method of signaling she would like to come inside, is to climb the screen just off the living room.
I could accomplish two things with this device or maybe something better suited, if anyone has any ideas.
I’m thinking I could have an alert that would let me know she is touching the screen, and maybe another that would distract her from climbing on it, and ultimately aiding me in not having to replace the screen.
I believe it would work for that. We have used it in the pram when the baby was sleeping outside. It was easy to spot via push message when he woke up and started to move.
Now it is glued on a lid of a box we don’t want the kids to access, it is not possible to open the box without triggering the vibration sensor.