Last day if anyone is curious. This is one of those "I really don't need this" buys, but even if it's only good as a doorbell or siren, it's a good deal at $40. My Xiaomi devices are working excellent on HE with the IKEA Trådfri outlets in place, but for people that are looking for a budget option, and the simplicity of HomeKit, this is a game changer. I don't think it's possible for a consumer that is only comfortable with HomeKit to have access to so many cool little inexpensive devices any other way.
Their window/door sensors are also on sale: $9.99 (US) is a great price for those sensors.
I've never used Xiaomi devices, but if they are as good as other people say they are...
(I just ordered a whole pile of them...)
I'm really liking them. Very reliable once you get the Trådfri Outlets and/or repeaters in place with them. Prior to that, they are hit and miss. Can really understand why people would call them unreliable since, without the repeaters deployed, they would randomly drop off. But with the Trådfri outlets as repeaters, I've had no drops. Very solid.
This is a really interesting device. I spent the last 24 hours getting familiar with what's possible and what isn't.
What it is:
By far the least expensive and most comprehensive official HomeKit hub so far. The Xiaomi Mijia and Aqara devices are very good quality for the price, and pairing them to an actual Xiaomi Aqara hub is a breeze. The devices literally pair within seconds, every time. No need to tap the pairing button to keep them awake, as is necessary with ST and HE. I found that even though the devices have an infamous reputation with developers that have suffered the significant variations from one Xiaomi device to another, the Aqara Hub doesn't care. It paired both Aqara and Mijia branded devices with great ease.
The Hub is small (roughly the size of a hockey puck and about 1/3 thicker). Although I had hoped to have received one with a North American plug, I did not, and instead a free plug adapter to go from the three prong Chinese plug to a non-polarized North American plug was included in the shipping envelope. The hub has a lighted ring that can be used to display just about any color you want, or it can be turned off via HomeKit. The speaker for the alarm has selectable sounds, custom sounds (android app required for uploading MP3 files), and by assigning a Xiaomi trigger device, it can be used as a doorbell too.
What it is not:
The hub can be accessed via app only. You have a choice of the Xiaomi Mi Home app or the Aqara Home app. The Mi Home app allows the most control over the device, but it is not pretty and not properly formatted for large modern screens. There are significant anomalies in the UI that make the use of the Mi Home app very frustrating, not to mention the weak UX. The Aqara app on the other hand is nicely designed and has no such display issues, but it's confusing that when you switch the location from United States, to Europe, the UI and capabilities significantly change in the same app. When the app is set to Europe, it is a full HomeKit app. This has advantages if you want to use HomeKit for automations, but that's the rub. You can only create HomeKit automations and HomeKit Scenes to their full extent when the app location is set to Europe. When set to United States, Mainland China or Other Region, you have IF-THEN automation capability right in the app allowing more control over what the hub does. Unfortunately, those automations are restricted to Xiaomi devices and the hub. The only way to automate between other non-Xiaomi devices and Xiaomi devices attached to the Aqara Hub is via HomeKit automations.
While it's possible to set the alarm and doorbell sound and level, that functionality isn't available in the Aqara Home app. This presents a minor problem if you decide you want to change it after you have everything setup in HomeKit. The Mi Home and Aqara Home apps cannot access the hub at the same time. So it is necessary to reset the HomeKit pairing so the Mi Home app can connect to the hub. This does allow the hub to still be exposed to HomeKit, but in a more limited fashion. For example, there isn't an alarm arm and disarm capability in the HomeKIt layer that is exposed via the Mi Home app, but it is there, only it's tied together with the light ring settings in HomeKit for some reason. Getting things to work in HomeKit with the Mi Home app I found to be very challenging.
So once you change to the Mi Home app and set your sounds and volume levels, you can switch back to the Aqara Home app with little issue. It has a "Bind Hub" function that seems to work fairly well. Only failed once, and I just repeated it with success. But, this means your HomeKit automations will all be broken or will disappear when you have to reset the HomeKit settings to pair with the Mi Home app. That part is a real mess, and I do hope that is resolved in later app and firmware updates.
So I had three things in mind when I bought this hub, but I think I'm probably going to get more than I expected in the long run.
I wanted to play with a new toy that would make me look at HomeKit differently.
I wanted to use this as a doorbell. This I thought (hoped) might be possible by triggering a virtual switch exposed to HomeKit. No such luck. While you can turn other HomeKit devices on/off from an Aqara scene, you can only trigger an event on the Aqara Hub by way of another Xiaomi device paired with the hub. For me, this wasn't such a big deal, since I was already triggering my doorbell sounds via an Aqara contact sensor, where I soldered two leads to the reed switch and then attached them to wire running up to a standard doorbell button.
I wanted to use this as a supplemental alarm siren if possible. But, how was I going to trigger the alarm if only Xiaomi devices directly paired to the hub were able to do that? I thought about using the second Xiaomi dual relay I have on the way. Once it's exposed to HomeKit, I would simply have to operate it to trigger the siren, but not only did that seem like a waste of a decent dual relay, it would still leave me with the problem of triggering a remote siren from my closed platform iSmartAlarm system.
The answer was to remove my Xiaomi Mijia door/window sensors from Hubitat Elevation and pair them directly with the Aqara Hub. This is where that decision is a controversial one. In order for HE to be able to still use the contact sensors for my door announcements, prevention of locking when the door is open, etc., it was necessary to go back to using HomeKit automations to link contact sensors with HE virtual switches exposed via Homebridge.
Now I had done this in the past and the results were very unreliable, and down right frustrating. This time it's very different though. @dan.t 's version of the Homebridge app via Maker API is so fast and reliable, that I think it's going to workout just fine this time around. So I have a Mijia button hidden away for emergency disarm, and door/window sensors paired directly with the Aqara Hub, then synced with virtual switches in HE via HomeKit automations. The results are quite impressive. I cannot tell the difference from when the door/window sensors were paired directly with HE. Hopefully it stays that way and this little experiment is a success.
Note of interest- The great work done with the Xiaomi button driver for HE actually exposes 3 addtional button presses that the Aqara Home app does not. They support one-click, two-clicks and long-click only*.*
I'm giving the Aqara Hub HomeKit edition a for its ease of use (for non-technical HomeKit only users), but it definitely needs to be further simplified, and the missing sound and alert volume settings really need to be added to the Aqara Home app. For the $40 US I paid, I'm quite happy with this, and I hopefully will not have to deal with any connection issues like some of the Z-Wave doorbells seem to have. Having this function as a supplemental siren is a nice bonus considering the low price. However, Android-only users will have a significantly more difficult time integrating this with HE, and if I didn't already own an Apple TV 4, then the cost savings would be more than eaten up in purchasing one, just so I could run HomeKit automations.
Apparently Xiaomi Aquara is coming out with Zigbee 3.0 very soon. Hopefully with similar price point. I have only a few old temp/humid Aquara sensors but love the look and quality.
Yes I read that post. That's a welcome change. The current device are working very well for me, so I have no compelling reason to upgrade, but this may bring integrated support to HE. I know @mike.maxwell is a fan of the design, but non-compliance with the Zigbee protocol is preventing any official driver development from happening.
Please excuse the simple question.
I assume that when they move to Zigbee 3.0, then they will also be "backwards compatible", so that the standard Zigbee HA drivers the HE has, will be applicable to the new devices? Is that correct?
Yes. Zigbee 3.0 is backward compatible. Also can (but not nessecarily does) allow Zigbee HA devices to fall back to Zigbee LL.
I also have one of these hubs. To understand how you have managed some HomeKit automations, have you just exposed a HE virtual switch to HomeKit to turn on/off via automations corresponding with the state of a native HomeKit device (such as a contact sensor) and then you have automated anything more complex using HE?
Originally I was thinking about mirroring a HomeKit temperature sensor to a HE virtual temperature sensor, but even with Controller or Devices to expand HomeKit automations it doesn’t seem as if that is possible unless you create a HE virtual switch that corresponds to every possible (likely) temperature reading for the HomeKit device. Does that seem right or am I missing something about HomeKit automation capabilities?
BTW, thanks for your frequent informative posts!
Correct. I just use HomeKit automations to sync virtual switches to HomeKit only devices. In my case with the Xiaomi Aqara hub, that includes Xiaomi Zigbee devices that are paired to the Aqara Gateway.
I do all my automations in Rule Machine or one of the HE apps. I used to use a mix, but that became a pain to manage since I would sometimes have to rebuild the HomeKit automations if something became corrupted and I lost them. These days with Controller Pro for HomeKit, that’s less of an issue sunce I can backup HomeKit with it, and Homebridge is also now very stable. But I still prefer automating everything in HE and only using HomeKit to sync with virtual switches.
For HomeKit temp/humidity devices, there’s no way to use them with comparison to another device’s measurement, You can only compare against a set value in HomeKit. I know of no way to sync a HomeKit temp/humidity device to a virtual temp/humidity device. For that reason, I keep my Xiaomi Temp/Humidity/Barometric Pressure sensor directly paired to HE, so I can compare humidity against a reference device for my bathroom exhaust fan.
I don’t understand the point of this. Wouldn’t maker api and homebridge do the same?
I don't understand your question. This thread is referring MakerAPI and Homebridge. What is it you're asking?
This hub essentially makes zigbee things homekit capable? Atleast the new one. For example, pair a aquaria button with h.e then maker api it?
The hub tends to drop Xiaomi devices because their version of Zigbee is non-compliant. But pair a Xiaomi device to a Xiaomi hub and it never drops. So the idea here is to pair Xiaomi devices to the Xioami hub so they won't drop. But then how do you get them to interact with HE? Enter HomeKit.
You expose virtual devices (like switches) to HomeKit from HE using MakeAPI Homebridge. The Aqara hub is already HomeKit compliant thus, its devices will show up in HomeKit. The Xiaomi devices, and the HE virtual devices are then both in HomeKit, but not connected. So then you create a HomeKit automation that ties them together.
Example HomeKit automation:
Xiaomi contact sensor opens -> Turn ON corresponding HE virtual switch
Xiaomi contact sensor closes -> Turn OFF corresponding HE virtual switch
Then in your HE Rule Machine rules, instead of the contact sensor as the trigger, you choose the corresponding virtual switch. The net result is identical to a Xiaomi device that is paired directly to HE, except these are actually paired to the Xiaomi Aqara HomeKit hub, so they never drop.