Aqara Smart Hub M2 (2.4 GHz Wi-Fi Required), Smart Home Bridge for Alarm System, IR Remote Control, Home Automation, Supports Alexa, Google Assistant, Apple HomeKit and IFTTT
- Aqara Hub M2 requires 2.4 GHz Wi-Fi. One Aqara Hub M2 can connect up to 128 Aqara zigbee devices (Aqara Zigbee repeaters such as LED Strip T1, Smart Plug, Wall Switch(with neutre)are required). Hub M2 only support aqara zigbee child device but not aqara thread devices or zigbee devices from other brands.
- 360° Infrared Control: Control your existing IR devices such as fans, air conditioners, TVs from any part of your room by voice and via home automations (indoor use only).
- Ethernet RJ45 Port & USB Power: Wired connection via Ethernet RJ45 for extra stability and lower response time. More flexible installation with USB power (power bank with pass-through charging is advised).
- Home Automation and Alarm System: Works with all Aqara devices to create a comprehensive, smart home automation system. The Aqara Hub M2 is equipped with a built-in speaker that can be used in a variety of ways: security alerts, doorbell, alarm clock, and configurable ringtones (Aqara child devices are required).
- All-Round Compatibility: The Aqara Hub M2 ensures seamless integration of your Aqara devices with a variety of smart home ecosystems and voice assistants, including Apple HomeKit, Google Assistant, Alexa, IFTTT, and more (𝐞𝐧𝐬𝐮𝐫𝐞 𝐭𝐡𝐞 𝐌𝟐 𝐢𝐬 𝐮𝐩𝐝𝐚𝐭𝐞𝐝 𝐭𝐨 𝐭𝐡𝐞 𝐥𝐚𝐭𝐞𝐬𝐭 𝐟𝐢𝐫𝐦𝐰𝐚𝐫𝐞). For questions or support, feel free to contact us. Note: Compatibility varies by sub-device. Please check each device's specifications for platform support.
https://www.amazon.com/Aqara-Cont...YnRm&psc=1
Leave a Comment
3 Comments
Sign up for a Slickdeals account to remove this ad.
It's not perfect, but it expands the ecosystem massively, and it also means that customers of the "closed" vendors can move to the open ecosystem when they need more devices that their vendor doesn't make -- this is exactly what happened with me.
I was heavily invested in the Hue ecosystem, and they started making moves that made me less happy with staying with them, plus I wanted to start integrating certain sensors that Hue didn't make/were more economical from other vendors, so I bought a Zigbee hub to replace my Hue one, and the transition between the two hubs in Home Assistant was like, an afternoon's work of re-pairing and naming stuff. Rather than tearing stuff out and having to buy new stuff.
Now I have a mix of no-name, Aqara, Hue, ThirdReality, etc hardware on my network, and it is all operating pretty nicely together. If someone wanted to start investing in that system? I wouldn't even warn them off of going with a closed hub, to be honest, unless they were tech-minded enough that they were already in HomeAssistant; the advantages of the closed hub ecosystems is that they're more straightforward to set up and have a smooth onboarding UX, without even having to know what Zigbee is, frankly. If they outgrow it, they can start learning about the wider ecosystem options, without wasting any money on anything past the hub.
Because it's proven a pretty great way to get a lot of compatible devices in their ecosystem, to be honest. The hubs may end up proprietary, but device compatibility with other hubs running with something like Zigbee2MQTT is actually very good. Almost Aqara devices will operate in a "standard" network just fine (for their base features at least -- some implement very specific features by extending their capabilities with the Aqara hub/app).
It's not perfect, but it expands the ecosystem massively, and it also means that customers of the "closed" vendors can move to the open ecosystem when they need more devices that their vendor doesn't make -- this is exactly what happened with me.
I was heavily invested in the Hue ecosystem, and they started making moves that made me less happy with staying with them, plus I wanted to start integrating certain sensors that Hue didn't make/were more economical from other vendors, so I bought a Zigbee hub to replace my Hue one, and the transition between the two hubs in Home Assistant was like, an afternoon's work of re-pairing and naming stuff. Rather than tearing stuff out and having to buy new stuff.
Now I have a mix of no-name, Aqara, Hue, ThirdReality, etc hardware on my network, and it is all operating pretty nicely together. If someone wanted to start investing in that system? I wouldn't even warn them off of going with a closed hub, to be honest, unless they were tech-minded enough that they were already in HomeAssistant; the advantages of the closed hub ecosystems is that they're more straightforward to set up and have a smooth onboarding UX, without even having to know what Zigbee is, frankly. If they outgrow it, they can start learning about the wider ecosystem options, without wasting any money on anything past the hub.
I eventually moved to Home Assistant, and initially integrated the Aqara M2 hub and its associated devices with HA using the Apple Homekit Device integration, but found that a bit clunky and ended up retiring the Aqara hub in favor of a Nortek Zigbee/Z-Wave combo stick, and re-paired all the Aqara devices directly via ZHA - while ZHA does not offer the fine grain control that the Aqara hub/app does, it exposes enough of the Aqara devices entities for what I need to automate.
I recently set up an Aqara M2 hub in my brother's house, and paired a couple of no-neutral on/off Aqara switches in the shop area of his basement, as well as a TP-Link Kasa WiFi 3-way switch at the top of the basement stairs that controls lighting in the finished part of his basement - as both TP-Link and Aqara pair with Alexa, we were able to set up an automation whereby turning off the 3 way switch at the top of his stairs not only turns off the lights in the finished portion of the basement, it also turns off the Aqara on/offs in the shop area - no more having to go back down the stairs if forgetting to turn off shop lights. There's a ton of automating that can be done using Aqara's closed hub, as well as some cross-product automating when Alexa support is available.
Leave a Comment