Hello
Do you know any DH for the LLKZMK11LM ? Aqara Wireless Relay?
[OBSOLETE] Original & Aqara Xiaomi Zigbee Sensors (contact, temp, motion, button, outlet, leak, etc)
I donât. Itâs a very new device and I donât think anyoneâs developed a device handler for it yet.
Another user was able to use the device handler for the Aqara no-neutral wall switch with the Aqara Wireless Relay, but it didnât work 100%:
Best of luck!
I will try it. Thanks
Hi,
I have 6 Aqara sensors connected to my Hub - all through routers (Anchor Vetaar outlets which I added as generic Zigbee switches - they claim to be Zigbee 3.0 though). 4 of my sensors are temperature sensors and 2 are contact sensors. I used bsprangerâs repository to add all of them and the temperature sensors appear to be work - they were a bit glitchy immediately after I added them and only reported their battery but started working afterwards. They now report battery, temperature and humidity though they are not regular - when I use the graph function on the new ST app it only shows a 2-3 of entries for temp and humidity whereas thereâre literally dozens of check ins under the events tab and one would assume each check in event contained all the details. The contact sensors are the worst though - theyâve been stuck on open ever since I got them and I canât get them to update. Iâve there and tapped the reset button to manually get them to report and while each tap is reported under the check in tab on the app, the status does not update. Iâve googled around a fair bit and havenât found anything. Could someone please help me?
Thank you!
I have 2 of them running as âremoteâ ZigBee relays and therefore not using the switch inputsâŚ
They both have been very stable with that DTHâŚ
Xiaomi / Aqara devices are incompatible with the vast majority of ZigBee router/repeater devices. I have no experience with nor have heard any reports about whether they will work when connected through Anchor Vetaar outlets, so my assumption is that they wonât. The behaviors you describe with your Aqara Temp-Humidity and Contact Sensors match my experience with a couple of ZigBee router devices that I have tested - specifically, a Securifi Peanut Plug and a Sylvania SMART LED strip light.
While the issue with most repeater/router devices is that they drop their connection with Xiaomi / Aqara devices after 2 to 48 hours, in the case of the Peanut Plug and Sylvania SMART LED strip light, the they seem to randomly drop messages from Xiaomi / Aqara sensors and buttons.
To know whether Xiaomi / Aqara devices are incompatible with your Anchor Vetaar outlets, you probably should know what the expected behavior of your Aqara Temp-Humidity and Contact Sensors is, and then also it would help to turn on debug log messages to see what ZigBee messages are actually making it to the hub.
Assuming youâre using the bspranger device handlers, when Aqara devices are first paired to the ST hub, the battery level will not appear because a message including battery voltage is sent earlier in the process that the hub doesnât receive. Generally the battery level will be reported within the first two hours after pairing, as part of all Xiaomi / Aqara devicesâ regular 50-60 minute âcheck-inâ report messages sent to the hub.
However, on some Aqara devices, short-pressing the reset/pairing button will cause a special âcheck-inâ report message to be sent that includes battery data, and if received, the Aqara Temp-Humidity and Contact Sensor device handlers are coded to parse that battery data, and because of that itâs totally possible to see the battery level reported during pairing as the recommendation is to continue short-pressing the reset button until the device appears in the ST classic app ready to be renamed.
As soon as Xiaomi/Aqara Temp-Humidity sensors are paired they will start sending sensor reports, but itâs important to understand that the reporting is change-based and not time-based. The Aqara sensors are programmed to only report when they detect temperature changes over 0.5 degrees Celsius or more than 6% humidity change (source). When either of those have changed enough, three report messages are sent by the Aqara sensor (temp, humidity, & pressure) or two messages (temp & humidity) if itâs a Xiaomi sensor, even if only one of the values has actually changed.
On top of the fact that Xiaomi/Aqara Temp-Humidity sensors only report when the temperature / humidity changes, note that if the other value(s) remains the same, no hub event will be generated. This is because the default behavior of device handlers is to only create events when the attribute value has changed (in this case, attribute refers to temperature, humidity, or pressure). So you wonât see successive repeated values in the events history.
The bspranger device handlers also generate âcheckinâ events, and they appear any time any kind of message is received from the Xiaomi / Aqara sensor. So what can happen for example is that youâll see a checkin event for a reported temperature value, but you wonât see a temperature event because the value was unchanged.
The key to seeing whether your Aqara Temp-Humidity sensors are working as expected is to turn on debug log messages in the preferences for each sensor in the ST classic app. Then try blowing on them with your warm human breath. That should generate a lot of reports because both temperature and humidity will change. Look at whether all three reports are coming in each time (temp, humidity, & pressure).
This really sounds like a case where either the open/close messages arenât making through the Anchor Vetaar outlets to the hub, or the contact sensors connections have been dropped and the hub just isnât âawareâ of that yet.
The reset to open/close buttons in the ST app UI just create open / close events and do not affect the sensor itself in any way. Xiaomi / Aqara Contact Sensors do not accept any command messages whatsoever. Either they work, or they donât work. So if theyâre not working as expected, look outside the device handler / mobile app. It could be a router issue, connection issue, or low battery issue. If the router has dropped a contact sensorâs connection, you will see no check-in events. Since the sensorâs check-in report message is sent every 50-60 minutes, you should at least see one checkin event an hour.
2 Likes
Can we have the DTH updated for full compatibility with the new app? One example, the aqara temperature sensor in the new app the first thing that is displayed is humidity, to show temperature it must be changed to the Xiaomi temperature DTH, and the aqara in the new app only shows temperature and humidity, not pressure. Eventually we all must move to the new app and it would be nice if the DTH could be updated for full functionality in the new app.
It would be nice if SmartThings would publish the developer documentation necessary to know how to update custom DTHs to work with the new mobile app.
But they havenât.
I nor any of the users who worked on all the Xiaomi & Aqara DTHs receive any compensation for that work; we shared all of that freely with others.
For me personally, keeping in mind that I do this for free, it doesnât make sense spending a bunch of time trying to guess what needs to be changed to get the DTHs working in the new app.
Believe me, I am just as frustrated as you and many other users who have asked for this. But you should be directing your frustration at SmartThings, and asking that the new developer documentation for hub-connected devices be released.
Keep in mind that SmartThingsâ official stance at this time is that nobody has to switch to the new mobile app:
3 Likes
The strange thing is that the DTH works well but shows humidity first, if the aqara is changed to the Xiaomi DTH, then the temperature is showing first.
For the record I jumped ship to Hubitat, so I donât have any interest in maintaining code that I donât use and get no compensation to maintain.
1 Like
What will happen when the classic app stops working and we have to pair a new Xiaomi sensor or one goes offline? The new app cannot add this sensors. How can we ask Samsung smartthings to release the documentation for create dth for the new app, or for them to pick custom dth and add them natively to the new app?
Been using this handler for ages with Temp, buttons, door sensors all fine.
Canât figure out for the life of me how to connect a leak sensor, theres no button anywhere. Could someone point me in the right direction please
The top of the leak sensor is the button, try to push the top were the icon is. It should blink a led.
You switch to a home automation system that cares?
1 Like
perfect thank you 
Hello.
Iâve managed to pair the Xiaomi button on my ST Hub, but I donât know which firware my device has, so I picked the Handler for the latest version, and it seems to be working just fine. But I have a problem, the button wonât trigger individual devices (I have 3 meross smart plugs) it only triggers the Scenes I have configured on ST App. Is this suppose to be like this or did I chose the wrong firmware version?
P.S. I have Smartthings Hub V3 and the new app.
Any help please? Thanks.
What are you trying to use to create the rules/automations/actions to trigger individual devices?
Your problem is the new app. All of the Xiaomi / Aqara device handlers havenât been updated to work 100% with the new app. SmartThings has not yet published developer documentation on how to do this, so the best solution is to use the SmartThings âClassicâ mobile app for now.
1 Like
