stupid question. i have the original button and have updated my handler. it now registers single, double triple etc. however cant seem to get it to work in core / how to pick up the different presses in smartthings. pleases can someone let me know the right ‘instructions’ / app to use to take advantage of the now 5 options?
Hi Davey, please disregard my response. My wires got crossed and I thought I was responding to a question about double tapping on a GE Jasco switch. Sorry about that.
All the different press types for the model WXKG01LM Xiaomi button result in standard SmartThings button pushed events except for when the button is held. In that announcement post I included a chart showing that:
Action
SmartThings Event
Notes
Single press
button 1 pushed
Hold
button 1 held
Event comes after button is released ~
Double-click
button 2 pushed
Triple-click
button 3 pushed
Quadruple-click
button 4 pushed
Shizzle-click
button 5 pushed
5 or more multi-click
So the button number needs to be part of the piston’s conditional, something like:
if Device_Name's button #2 gets pushed
Something isn’t correct there. You should see another selection option for “Button Number”, like this:
The only thing I can think of that may be going on here is that your SmartThings Hub is not yet “aware” that the Xiaomi Button can send events for buttons #1-5.
In order for the hub to know how many buttons to make available to smart apps, a device handler has to send a numberOfButtons event.
All of the Xiaomi / Aqara button device handlers sends the numberOfButtons event when the button is paired, but if a user already paired a button and just changes from the old device handler to the new one, the number of buttons isn’t automatically updated.
To manually update the number of available buttons with the new driver, try opening the preference settings for the button in the SmartThings Classic mobile app, and then just press save:
First go into the IDE to check you have a Zigbee ID as well as a Device Network ID. The Zigbee ID will be something like 00158D000159EF43 and the Device Network ID will be a 4 character er Hex ID like BF0B. Having the Zigbee ID in there is what allows the device to re-attach and keep your settings/automations intact.
Take the sensor as close to the hub as you can.
Select My Hubs in the IDE, scroll down and click on List Events.
Now use the app to put the hub inclusion mode (add a thing) as though you are going to add a new device.
Start pressing the button on the sensor. I find it works best to press it, let go and then wait for the LED flashes. Count to 3 and then press again. You will see it start to add when the light sequence changes.
Now the really tricky bit. You need to continue the sequence of press pause press and at the same time refresh the hub events webpage until you see a Zigbee Join. You should also see in the app that your device was connected again.
When you have seen the Zigbee join you can stop pressing the button and save the devices.
Now leave the sensor by the hub for a few hours or at least until you see it report the battery.
i have done this a few times and this sequence seems to work quite reliably.
I have several buttons and open / close Xiaomi and all work fine. Used the IDE catchall method. I use the a4refill and bspranger DH.
Recently got some aqara motion sensors and am struggling a bit. I can seem to pair them on the a4 refills DH and all works ok however i really only want them for the lux reading which only bsprangers will report on. If i pair with the latter device handler it always drops off (offline) within a day. If i link it with a4 and then a few days later change it to bspringers it will then drop off in a day again.