After connecting the device and installing the driver I can access my new device.
The first “Test” command works, after a while the battery status (100%) is shown, and even my push on the little button of my device raised a smoke=“testing…” event in Hubitat.
Great! But…
I’ve noticed that the log is now flooded with “Parse START” messages; The lastClear state is set 10 to 20 times a minute! I fear that the battery will be fast drained...
Unfortunately, you can't with these drivers. The smarthings contact sensor is much more sensitive but is no longer available. (It can be done if you're using zigbee2mqtt or deconz platforms but that's another story altogether.)
Thanks for the reply....Oh man I just got these.... is there way to set the sensitivity when connected to Mi home and have it "stick" when connected to Hubitat? I was avoiding mi-connector...maybe you can point me the direction of zigbee2mqtt
If you search for deconz you should be able to find similar resources quite easily. Both these solutions will require a middleman (eg raspberry pi) and additional zigbee sticks which may be overkill.
I don't know although it "may" be possible if the sensitivity is set within the device. I guess you can test this with the app.
Otherwise look for a used smartthings contact sensor somewhere or another brand device. Suggest you open a new thread asking for advice on such sensors to get a wider audience.
Thank you for the direction.... I may have to return these... I do have an RPI running Hoobs....have to weigh whether this is worth the effort....
I keep beating on Hubitat and Homekit solutions for washer/dryer notifications...I am using a smartthings plug and an eve plug with power metering but I was hoping a couple vibration sensors would make it easier.....
There are a couple of community apps written to use power plugs for washing machine notification if you haven't already seen them. You might want to check those out.
Thanks I have a couple of Shelly plugs I preordered that should ship soon by recommendation on here but did not know about the apps.... I will check those out thanks for the tip...but I had high hopes for these things for even a mailbox or dishwasher but they aren’t even playing well with rules when they do trigger so I might play with it a bit more till I get my Shellys.... and if I don’t find good use I’ll return them.
@X-RayVision I use the drivers that were originally written by Marcus. They are no longer maintained but it does allow to set the sensitivity of the Aqara vibration sensor. Note it can be a bit fiddly. You set it in the driver but it may not change until you reset the device.
I don’t how I could not find it b4. Thanks! Just switching to this already seems more sensitive ... so once set, the sensitivity actually shows in current states? When it says to push the reset button it means the button on the actual sensor I assume tried that a couple times and did a disconnect and sensitivity didn’t seem to show up... I’ll keep fiddling.
Yes it can be a bit of a pain. I think last time I changed it, it had to delete the device and the search for it again. Also found that Aqara devices connect better we really close to the hub.
I have some Aqara without neutral switch 1 and 2 button and work OK. Now I buy another 1 and look new designs and my V1 button is not working, if I press manually is working but from the application NO.
This is the difference
I too have the same issue where there is no wet/dry status shown in the "Current States" section Hubitat.
4 out of 6 new water leak sensors are not reporting wet/dry status like this.
I have the aqara outlet and I would like to know if there is a way of having a power-off memory in the case of an electrical cut-off. Thanks for any help!
It seems like I should be able to assign button numbers to the various actions, but I haven't found anything I can put in the fields that it will save. The buttons appear to be working without anything in the fields...I created a simple automation rule to key in on button 1, which is the button press. Anyone know if/how I can utilize double presses, holds, etc?
What you're looking at is the "Commands" section of the device page, which is useful for manually running commands on the device, which might be helpful to test automations you've set up (elsewhere) that trigger based on those events or for devices--not so much these--that accept commands to see if the device responds as expected. In the case of buttons, most buttons really just send messages to the hub and don't accept commands (consider this in contrast to a switch, where "On" and "Off" are commands you might be able to send from the hub). The "Push," "Hold," etc. buttons you see on this page should just simulate a "virtual" button press (again, telling any apps/automations you have that look for these events that these events happened), but unless you've configured an automation somewhere, it won't do much.
Beyond that, these drivers likely have another oddity; they have apparently been abandoned, and Hubitat's button model requirements have slightly changed since they were introduced. It's possible they don't actually implement these commands (they're new-ish) and will just error out in the log instead. This isn't crucial unless you plan on "virtually" generating these events instead of actually pressing the button. (A quick glance at the code for one suggests it actually does implement it but will log a message to the effect of "LOL, this doesn't make sense," which is also kind of true...but unlike convention, it won't generate an event.)
Long story short, what I suspect you're looking for is an app like Button Controller or any of other various built-in or community options to create automations based on actual button events. On Hubitat, automations are created via so-called "apps," so you'll find these under "Apps" on the left-side menu (and Add Built-In App or Add User App, depending on what you have installed or not, etc.).
On Hubitat, automations are created via so-called "apps," so you'll find these under "Apps" on the left-side menu (and Add Built-In App or Add User App, depending on what you have installed or not, etc.).
