NOTE: Although many users have had great success using them, Xiaomi / Aqara ZigBee devices are NOT officially supported or guaranteed to work on the Hubitat Elevation platform.
Why new drivers?
I wanted to write my own and since @veeceeoh isn't here to support his I thought I'd release mine. I haven't yet published drivers for all types of devices from Xiaomi/Aqara, but will add the rest as I find the time. With this said, a big thank you goes to @veeceeoh for his drivers that were where it all began for me
Many things, these are a COMPLETE rewrite, they don't share any code with the old drivers. They have been tested by a few people and been found to make the devices more stable and responsive. Yes you read that right, if you want to know more about how that is done, look at the code.
- Xiaomi/Aqara/Opple Button/Switch/Remote (works with models WXKG01LM, WXKG11LM (2015 & 2018), WXKG12LM, WXKG02LM (2016 & 2018), WXKG03LM (2016 & 2018), WXCJKG11LM, WXCJKG12LM & WXCJKG13LM) - Import URL
- Xiaomi/Aqara Contact Sensor (works with model MCCGQ01LM & MCCGQ11LM) - Import URL
- Xiaomi/Aqara Motion Sensor (works with model RTCGQ01LM & RTCGQ11LM) - Import URL
- Xiaomi/Aqara Temperature & Humidity Sensor (works with model WSDCGQ01LM & WSDCGQ11LM) - Import URL
- Xiaomi Mijia Smart Light Sensor - Zigbee 3.0 (works with model GZCGQ01LM) - Import URL
- Aqara Water Leak Sensor (works with model SJCGQ11LM) - Import URL
- Aqara Smart Curtain Motor (works with models ZNCLDJ11LM & ZNCLDJ12LM) - Import URL
Which driver should I use?
All drivers are as combined as they can be, the list above should make it clear which driver go with which model.
It is perfectly fine to replace the driver of a currently installed device with these drivers, no need to pair them again, in general. There are exceptions, most notably the Opple remotes and most Aqara Button devices. They need to have some settings sent to them which can only be sent when pairing. More details in a future post below.
There may be errors in the logs during the first 3 hours when switching drivers, just ignore those. It will settle and get back to normal.
A good and stable mesh is needed for any Zigbee devices, not just Xiaomi/Aqara devices, but they can be more demanding at times. For more information regarding that:
All drivers have the Presence capability, if the device doesn't report in for over 3 hours it will be set as not present. This makes it easy to see that all devices are online at a glance in a Dashboard, or to monitor any change in Presence using RM or a custom App.
Post about it in this thread and maybe it will make it into a Github Issue and eventually taken care of
There may still be some excessive logging, that will be removed shortly, this is mostly so that it will be easier to debug any early issues not caught during beta testing.
Post about it somewhere else which seems appropriate. Not in this thread.
- "Your idea is stupid and slow and I don't like it" - Don't use the code
- "Your app/driver is crashing my Hub. I submitted a support ticket" - Don't do that, the fine folks at Hubitat Inc. do NOT maintain this code. This software is given free of charge with no support, implied or otherwise. I may still help...
- "The latest update broke it, FIX IT" - I do this for fun, please don't make it un-fun.
- "I have a great idea for a feature" - Go ahead and post it, I might get around to it...
- "You ignored my great idea" - See #2
- "I hate you for getting my hopes up, your app/driver is awful/buggy/stupid" - Ok, please write a better one so I can use it
- "Please fix your code, it's broken" - I write this because I enjoy coding. I will continue to support and provide updates as long as that remains the case.
- "I stole your code and made it soooo much better" - Thanks. Please post it so I can start using it.
"You are awfully sarcastic, I don't like you" - That's ok, I don't need you to
(thank you @thomas.c.howard for the original FAQ this one was based on)