[OBSOLETE] Xiaomi Sensors and Button (beta)

[florinangelescu]

Hi,

I want to use the button with webCoRE in the end, but this “troubleshooting” that I was doing was directly in ST app.
I am using version 1.2 by bspranger.
It is also possible that I got lost in the topic at some point and maybe I am not interfering where I should. These topics tend to get very long in a very short amount of time.

Thanks.

[cowboysdude (John Wade)]

Yeah they can be tricky little devils to get working… wish they sold them in the US…ordering from over seas is rough. I’d like to get about 4 more of these.

[Edward_Niedziejko]

What’s the rough part? Waiting the month for the container shipment to arrive?

[Niklas_svensson]

Did u get the WXKG11LM to work properly?

[toch]

what is the catchall log, and how to find it

[veeceeoh (Keith G)]

@Niklas_svensson

Did u get the WXKG11LM to work properly?

There is already a working device handler for the Aqara Button model WXKG11LM, available from the bspranger/Xiaomi Github repository (see this forum thread for more information.)

In fact, I’ve been working on an update that will work with both Aqara Button models (WXKG11LM & WXKG12LM), and the pre-release device handler code can be grabbed from here.

Please note that with the Aqara Button model WXKG11LM, there is no possible way to implement a hold function. A hold function is only available with the round “original” Xiaomi button, or the Aqara Button model WXKG12LM.

[Niklas_svensson]

Thanks for the replay.

I have that device handler. My problem is that a press on the button does nothing but a checkin, a second press about 5 secubds later registers as a press.

[veeceeoh (Keith G)]

@Niklas_svensson

I have that device handler. My problem is that a press on the button does nothing but a checkin, a second press about 5 secubds later registers as a press.

So you used pre-release device handler code that I gave the link to?

I think I can help solve your problem, but please do the following steps:

1. Download and install my pre-release Aqara Button DH code again (I have updated it since yesterday) from here.

2. Viewing the button in the SmartThings mobile app, open up preferences, scroll to the bottom, and make sure the display of both info and debug log messages is turned on, like this:
   

   

3. Open the Live Logging window of the SmartThings IDE for your hub.

4. Press the button of your WXKG11LM a few times

5. Isolate the log messages that are just for that button by clicking on it’s name in the Live Logging window

6. Take a screenshot showing the log messages that happened when you pressed the button, like this:
   

   

Based on those log messages I should be able to know what is happening.

[Asmegin (Jon)]

Everytime I have a power/internet outage (which is not infrequent), all my Xiaomi sensors stop responding once the power is back. I have a huge mixture of smart devices and these are the only ones that do not reconnect (Keen Smart Vents have an issue with going into a ‘sleep mode’ that requires pushing the sync button to activate, but only after power being off for at least a day).

I can easily get the Xiaomi Aqara devices operable by pressing the button on them a few times, but I don’t always have access and it’s a becoming a pain. I can see any way to do this remotely within the IDE or the app.

Any ideas?

[Blair_Pollard]

Does the Xiaomi button support double press and long press also can it be used to say turn a light on and off toggle with say a single press?

[siwilson (Simon)]

The button supports pressed and held. You can set a routine to have it control anything you want.

[Gert_Koolwijk]

I have tried to set the single (short) press to turn on a light and the long press feature of the Aqara button to ‘turn off’ a light. Turning on the light is working but the long press to turn off the light is’t functioning after I made a rule and assigned the long press feature. What am I doing wrong?

[siwilson (Simon)]

Can you see the held event under the “recently” tab for the button?

[Gert_Koolwijk]

No, only “button was pushed”. Nothing else. Could it be this function is missing in the the device handler (bspranger v1.2)?

[veeceeoh (Keith G)]

@Gert_Koolwijk

No, only “button was pushed”. Nothing else. Could it be this function is missing in the the device handler (bspranger v1.2)?

There are currently 5 different types of Xiaomi branded buttons devices. Each one has different functions available in SmartThings.

Which model number of button are you using?

[Gert_Koolwijk]

Hi Keith,

Sorry for responing a bit late on your question. I currently have 3 model WXKG11LM buttons. Recently I ordered a new 12LM version. Have read somewhere it might be a hardware issue. The 11LM version does not support the hold function. The 12LM version should support this. I hope

[siwilson (Simon)]

I have 2 of the G01LM buttons and I am using the original A4refillpad DTH. If I switch to the newer BSpranger DTH I lose the held function.

[veeceeoh (Keith G)]

@Gert_Koolwijk

Sorry for responing a bit late on your question. I currently have 3 model WXKG11LM buttons. Recently I ordered a new 12LM version. Have read somewhere it might be a hardware issue.

It’s not a hardware issue. The Aqara button model WXKG11LM simply doesn’t provide any way in the hardware to implement a hold function. However, the Aqara model WXKG12LM does support it. If you look at the header information section of the Aqara Button device handler code, there is a detailed explanation of the capabilities of each model when used in SmartThings:

Notes on capabilities of the different models:
Models WXKG11LM, WXKG02LM, WXKG03LM

• Only single press is supported, sent as button 1 “pushed” event
• The 2-button Aqara Smart Light Switch model WXKG02LM is only recognized as ONE button.
  This is because the SmartThings API ignores the data that distinguishes between left, right, or both-button presses.

Model WXKG12LM

• Single click results in button 1 pushed event
• Hold for longer than 400ms results in button 1 held event
• Double click results in button 2 pushed event
• Shaking the button results in button 3 pushed event
• Single or double click results in custom lastPressedCoRE event for webCoRE use
• Release of button results in lastReleasedCoRE event for webCoRE use

For more information, see my announcement post about v1.2 of the Aqara Button device handler here.

---

@siwilson

I have 2 of the G01LM buttons and I am using the original A4refillpad DTH. If I switch to the newer BSpranger DTH I lose the held function.

Which version of the bspranger DTH are you using?

Version 1.2, which I worked on and was extensively tested, does have button hold function, and improves on it. It was announced on the Original & Aqara Xiaomi Zigbee Sensors (contact, temp, motion, button, outlet, leak, etc…. thread four weeks ago:

[UPDATE] “original” Xiaomi Button device hander to v1.2

Available immediately on the bspranger/Xiaomi GitHub repository. The updated code can be copied from this direct link.

New features

• Button hold, which can set in preferences to send either a button 1 held or button 2 pushed event
• Button status correctly displayed in main tile of mobile app UI, with a new custom icon
• Live logging preference settings, with toggles for display of info (“plain” English) and/or debug (technical) log messages. As a default, info log messages are displayed.
• Improved webCoRE support

Important Notes

• The minimum time required for held can be changed in the preference settings. The default based on extensive beta testing is 2.0 seconds, and decimal values are allowed. Note that shorter times may result in greatly reduced reliability (see note about SmartThings cloud execution limitations, below)
• webCoRE users can make use of a number of custom attributes, some of which have been renamed from the previous version of the device handler:
  • lastCheckinCoRE - updated on every single message received from the button
  • lastPressedCoRE - updated when the button is physically pressed
  • lastReleasedCoRE - updated when the button is physically released
  • lastButtonMssg - updated every time the button is either physically pressed or released
• Because the button held feature is not hardware-based, no events are sent until the button is physically released. This means that even if the minimum time to held setting is 2 seconds, if you hold the button for 10 seconds, the held event is sent at the 10 second point, not 2 seconds after the press started.
• The device handler no longer sends button 1 released events. This is because SmartThings’ button capability only supports pushed and held events.
• The toggle mode option has been removed, because SmartThings’ button capability doesn’t support button released events and also because most Smart Apps that work with buttons offer a toggle switch option already.
• The SmartThings app UI display of button “pushed” or “held” event lasts for about 1 second, and then will reset back to “released”.
• Limitation of cloud execution: During beta testing, I and the beta testers found the accuracy of the device handler registering pushed versus held correctly to be well over 90%, as long as the minimum held time was not too short. The problem is that because the code is “cloud” executed every time a message is received from the button, sometimes the delays result in the release message being processed before the pressed message. The device handler decides whether a long press is a hold by comparing the press start time and release time, so if there are delays in the code execution, then even though you may hold the button long enough, the calculated time difference could be too short. There is really nothing that can be done to fix this other than physically holding the button for a longer time to compensate. However, I have made changes to the method used in the original a4refillpad device handler that improves on the level of reliability.

Screenshots:

[siwilson (Simon)]

It was a while ago, so not this newest version you show above. I may give that another go them as it looks quite clean. FTW the original A4refillpad one has never missed a beat in the last year and a bit I have been using it.

[SpruceCurrent]

My Xiaomi Agara Temperature / Humidity sensor shows up on the SmartThings IDE in My Devices and on the SmartThings app on my Android, but when I select the device I get a pop-up ‘Can’t connect to device. Check device and try again’.
I am using the bspranger : Xiaomi Aqara Temperature Humidity Sensor Device Handler.
The IDE events list shows continuous temp & humidity readings.
Any help would be appreciated.