SmartThings Community

Original & Aqara Xiaomi Zigbee Sensors (contact, temp, motion, button, outlet, leak, etc)

not sure if this helps - but data from the single wired switch is

Data * application: 12

  • endpointId: 01
  • manufacturer: LUMI
  • model: lumi.ctrl_neutral1
    Raw Description 01 0104 0006 02 06 0000 0003 0001 0002 0019 000A 03 0000 000A 0019

Thank you very much!
But it seems that the Temperature isn’t correct? On my outlet it show 160 degrees. That would melt the outlet if it was in Celcius and True :wink:

1 Like

Hi. I have quite a number of aqara door/windows sensor to add to ST. Prior to firmware update, pairing was flawless. After the recent firmware update, I can’t pair this sensor anymore.

Anyone else having this problem?

You can add support for Alexa to read the temperature of the aqara sensor changing the device type in the DH. Change to ‘smartsense multi sensor 2’. The smartthings app continues reading all parameters and Alexa can read now the temperature.

Thank you so much for your efforts on getting this to work - apologies for the possible misplaced post, but I’m not sure where to post this question.

I’ve just received a QBKG04LM (not currently support if I read correctly) which is registering in ST as

  • application: 16
  • endpointId: 01
  • manufacturer: LUMI
  • model: lumi.ctrl_neutral2

NB: I am using the latest SmartThings firmware on a v2 Hub 000.025.00026

The signals are being sent through to ST, but the buttons seem to be registering incorrectly, and specifically recording as 2 presses on each button. See the logs below:
I pressed the LEFT button, paused a few secs and then the RIGHT button.
It seems to be registering
(Button 5 pushed) then ((Button 3) pushed for LEFT as well as a ‘BOTH’ signal
(Button 4 pushed) then ((Button 2) pushed for RIGHT

Is there anything I can do about this, or can I possibly help in providing feedback to update the DH if this unit isn’t yet supported? Happy to do whatever I can to move this forward as it’s a great unit for the UK.

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 9:00:25 AM: debug Thomas wall switch: Creating event [name:button, value:pushed, data:[buttonNumber:5], descriptionText:null pushed (Button 5 pushed), isStateChange:true]

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 9:00:25 AM: info Thomas wall switch: null pushed (Button 5 pushed)

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 9:00:25 AM: debug Thomas wall switch: Setting Last Pressed to current date/time

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 9:00:25 AM: debug Thomas wall switch: Parsing ‘read attr - raw: B80B050006100000100000001001, dni: B80B, endpoint: 05, cluster: 0006, size: 16, attrId: 0000, result: success, encoding: 10, value: 0110000000’

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 9:00:25 AM: debug Thomas wall switch: Creating event [name:button, value:pushed, data:[buttonNumber:3], descriptionText:Both buttons were pushed (Button 3 pushed), isStateChange:true]

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 9:00:25 AM: info Thomas wall switch: Both buttons were pushed (Button 3 pushed)

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 9:00:25 AM: debug Thomas wall switch: Setting Last Pressed to current date/time

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 9:00:25 AM: debug Thomas wall switch: Parsing ‘read attr - raw: B80B030006160000100000F023000BB803, dni: B80B, endpoint: 03, cluster: 0006, size: 22, attrId: 0000, result: success, encoding: 10, value: 03b80b0023f00000’

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 9:00:11 AM: debug Thomas wall switch: Creating event [name:battery, value:100, unit:%, isStateChange:true, descriptionText:Thomas wall switch Battery at 100% (3.3 Volts)]

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 9:00:11 AM: info Thomas wall switch: Battery at 100% (3.3 Volts)

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 9:00:11 AM: debug Thomas wall switch: Parsing ‘catchall: 0104 0000 01 01 0000 00 B80B 00 01 115F 0A 01 01FF42296410006510016E20006F20020121E40C03281705210700082116260A2100009923000000009B210000’

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 8:59:57 AM: debug Thomas wall switch: Creating event [name:button, value:pushed, data:[buttonNumber:4], descriptionText:null pushed (Button 4 pushed), isStateChange:true]

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 8:59:57 AM: info Thomas wall switch: null pushed (Button 4 pushed)

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 8:59:57 AM: debug Thomas wall switch: Setting Last Pressed to current date/time

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 8:59:57 AM: debug Thomas wall switch: Parsing ‘read attr - raw: B80B040006100000100000001001, dni: B80B, endpoint: 04, cluster: 0006, size: 16, attrId: 0000, result: success, encoding: 10, value: 0110000000’

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 8:59:57 AM: debug Thomas wall switch: Creating event [name:button, value:pushed, data:[buttonNumber:2], descriptionText:Right button was pushed (Button 2 pushed), isStateChange:true]

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 8:59:57 AM: info Thomas wall switch: Right button was pushed (Button 2 pushed)

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 8:59:57 AM: debug Thomas wall switch: Setting Last Pressed to current date/time

1c9650b7-c58d-42cb-a4cb-41ce569a7b97 8:59:57 AM: debug Thomas wall switch: Parsing ‘read attr - raw: B80B020006160000100000F023000BB803, dni: B80B, endpoint: 02, cluster: 0006, size: 22, attrId: 0000, result: success, encoding: 10, value: 03b80b0023f00000’

Can you please send me a PM with some log output showing some debug log messages for the Smart Plug when the temperature reports are received? With that information I should be able to troubleshoot the incorrect readings, thanks.



There is a known issue with custom device handlers (DTHs) going “stale”, which leads to difficulty in pairing devices using that custom DTH. It’s not an issue that started with the newest firmware, but I have seen it happen to me more often recently.

The way to “fix” it is to view the custom DTHs in your hub’s IDE and (re) publish them.

I have also seen a related issue where the pairing doesn’t complete, the device never shows up in the device list, but the live logging window shows that it’s paired. I call this the “ghost device” issue, and the only way to get the device to show up on the hub’s device list is to look for it’s Device Network ID (DNI) which would be found in the Hub’s events list (not device events, but hub events), similar to the “catchall” method some people need to use to get Xiaomi / Aqara devices paired.

Here’s more information on the “stale” DTH issue:



Temperature and Humidity reports may work with the ‘smartsense multi sensor 2’ device handler, but atmospheric pressure and battery level reports will not work.

I will investigate how to get Alexa compatibility for the Xiaomi / Aqara Temp-Humidity device handler when the device is linked through the SmartThings Alexa Skill.



Thanks for all the information and log entries.

Because I don’t have any of the Aqara Wired Smart Wall Switches, it is quite difficult to create a device handler (or modify the existing one for the Wireless switches).

Although the device handler for the Aqara Wireless might seem like it should work, it is not actually designed for use with the Wired switches.

I’m looking into it, but it will take time. I will post here when I have something worth testing.

1 Like

This would be great!

I have discovered that this can be done changing the device type as I said before or adding a new line : capability “Contact Sensor” and Alexa can detect it and read the temperature, like it does with the original Samsung smartsense multi sensor that I have.

Congratulations for your amazing work!!!

1 Like

This is the only solution I found as well.

Before changing the device handler to include that line in the code, I just want to make sure that adding the Contact Sensor capability won’t cause any issues, because the temp-humidity sensor doesn’t actually have that capability.

After some help. I have sensor a few round the house all working fine. I had a spare one that I just added to SmartThings, found it added all ok. But when I open the sensor it doesn’t detect it’s open. And if I force it open it’s fine, but when I put them back together it still says it closed unless I force it close.
I have removed them a few times and re-Installed it and still same issue.

Anyone got any advise on how I can get it to work correctly. Don’t understand why it’s being like this!?

Hi @veeceeoh, thanks for your great work. I have a WXKG11LM button (aq2 version), using your latest DTH (1.42b) on V2 hub (25.26 FW). When i press the button the action doesn’t show in the tile, instead, shows in the last event section. Am i doing something wrong?

Hi guys, are there any known Device Handlers for the Xiaomi Aqara Air Conditioning Companion ?
https://www.gearbest.com/living-appliances/pp_416094.html

I have Smartthings Hub v1, and have 30 odd Xiaomi devices added to this setup using the a4refillpad DTH - they all work great. I am now trying to add two additional Aqara Motion Sensors to the setup but i cannot for the life of me get them connected. I have followed all the helps topics, hold for 3 seconds, wait press again - replaced batteries, but still nothing showing up in CatchAll.

Would you know how i could troubleshoot this?

I too have temp reading as 190 degrees. May be I am sending this from hell! :wink:
I have shifted to THIS DTH and it is working perfect.

I just wanted to let you know that I am working on changing the virtual app tile button behavior in the Xiaomi Button WXKG01LM device handler to match the other button device handlers.

All three device handlers will display “App Pressed” in the main tile when the virtual button is pressed in the SmartThings “Classic” mobile app, and generate a button 1 pushed event.

ALSO, the update to all three device handlers will allow the virtual button to be pressed as often as liked, with no need to wait for the display to clear to “Released”.

AND, the method for the timer to automatically clear the app tile display to “Released” will be changed to function that hopefully fixes the issues you’ve experienced with it taking 15-30 seconds to clear to “Released”.

It’s really important to understand that for physical button interactions the tile display is only giving the user visual feedback. Many button device handlers don’t show anything in the mobile app tile display when the button is pressed, but these Xiaomi / Aqara device handlers include a mechanism to give visual feedback which is completely separate from the events that are generated for different physical button interactions.

So even if the UI tile display isn’t working 100% due to cloud execution timing issues, the events to use for automations will still work as expected.



Please see my explanation above. The SmartThings “Classic” mobile app tile display for different types of button actions is separate from the generation of events. Some users have been reporting issues with the tile display, and I suspect it is related to the code being run “in the cloud.” The most important thing is that the events will still work as expected, based on all my testing.

I am currently working on an update to all the button device handlers which should hopefully help reduce or eliminate the issues with the button status tile display.



There are a number of reasons why this could be happening. To help troubleshoot, I have some questions:

  • How far is the problematic door/window sensor from your SmartThings Hub?
  • How many ZigBee devices are connected to your hub?
  • Are you using any ZigBee devices which are mains-powered, not battery-powered (i.e., ZigBee devices that plug into the wall)?


No. That is a Wi-Fi device, so there won’t be any device handlers released in this thread, which only focuses on Xiaomi / Aqara ZigBee devices. There is only one solution I know of which allows use of Xiaomi / Aqara WiFi devices with SmartThings, called Mi Connector.



I this same question elsewhere in your own thread and also the FAQ on ZigBee direct connection thread, and the best answer I can give is the same as you got on that thread:

SmartThings v2 and v3 hubs have a limit of 32 ZigBee end devices, and very likely the v1 hub is the same. The only way to get past that limit is to use ZigBee routers (also known as "repeaters) which are most mains-powered ZigBee devices (except some ZigBee bulbs).

Unfortunately, the vast majority of ZigBee router devices are incompatible with Xiaomi / Aqara devices, either resulting in them dropping off the network or messages not getting passed on to the hub. However, IKEA sells a Trådfri Smart Outlet which has been confirmed to work just fine with Xiaomi / Aqara devices. In fact I use one myself, with no issues. That said, to my knowledge, nobody with a v1 hub has tried using a Trådfri Smart Outlet with Xiaomi / Aqara devices, so I can’t make any promises!



I have seen that DTH and plan to examine how it parses the temperature report data to improve the DTH available in the GitHub/bspranger/Xiaomi DTH collection.

1 Like

Thanks. Btw, it was by no means meant to ridicule, rather in a lighter vein. Your work is really appreciated and the Button’s dth (new one with multiple button#s) is working great.

1 Like

Thanks for the reply. As for the questions you asked:

  • is on the first Floor where my hub is on the ground floor it’s right above and 2 meters across. But I have another sensor a foot away which works ok.

  • when you say how many. Not sure what you would count as a few handlers that allow me to control ring doorbell, Kasa plugs, and some other but then I had sensors in questions and hue lights. So sorry to sure what the answer to this is.

  • most of mine are batteries bar one which is main powered. But I have checks the battery with it though.

Even though the non-working sensor is a foot away from working one, I have read reports from people that have had similar troubles, and fixed them by adding a ZigBee device that can act as a router (or “repeater”). ZigBee routers act similar to a WiFi extender, allowing end devices to connect to the hub via the router instead of directly to the hub, which might have a weaker signal due to distance / interference. Another reason why ZigBee routers can be useful is that SmartThings hubs have a limit of 32 ZigBee end devices connected directly to the hub. This is why I asked how many ZigBee devices you are using.

Most mains-powered ZigBee devices (except some ZigBee bulbs, like Sengled bulbs), which is why I asked if you have any mains-powered ZigBee devices. However, the vast majority of ZigBee router devices are incompatible with Xiaomi / Aqara devices, either resulting in them dropping off the network or messages not getting passed on to the hub. IKEA sells a Trådfri Smart Outlet ($10 US if bought at an IKEA store) which has been confirmed to work just fine with Xiaomi / Aqara devices.

It is also possible that the problematic sensor is defective. I would suggest moving it to the same room as the hub and test if it’s working in that location. Also if you do find that you have any ZigBee router devices, try pairing it again in the same room as the hub, because just moving it won’t necessarily force it’s connection to move from the router to directly to the hub.

Thanks for the information and it’s quite handy having a read what you said. For the IKEA outlet sounds a easy thing to get round but just don’t want to add another brand to the house but I’ll keep that idea in my back pocket if I need it down the line.
As you said it might be a duff sensor which after everything you said I’m thinking the same as I took right next to the hub and reinstalled it again and still no joy when it opens. So I have added a few more sensors for a project I was going to do. So I’ll nab one of those and see if it works where it needs to go. If the same happens there then I may have to bite the bullet and by the Ikea outlet to help. Thanks again for the help. Always good to know someone there to help when need

1 Like

It never hurts to try a fresh battery. Especially if you didnt install the last one yourself recently.

Tired the new battery and it worked. But I did notice the housing for the battery was lose. Managed to tighten it up and boom. Sensor works now when open and closed. So something simple sorted it out.

Just got to sort out aqara humidity sensor that just appears like this:

1 Like