If you’ve explored the smart home world, you know that Zigbee devices often get a bad reputation for reliability issues. This stems partly from Zigbee’s open-source nature, which I covered in my Zigbee vs Z-Wave comparison.
Aqara creates many compelling Zigbee devices – motion sensors, locks, buttons, and more. I’ve experienced mixed results with their products, but appreciate their design, price points, and functionality.
My Current Aqara Devices
In my smart home, you’ll find:
- Wireless Mini Switches – Lifesavers! Perfect for spots where little ones can’t reach standard light switches
- Presence Sensor FP1 – Amazing for precise presence detection in specific rooms
- Motion P1 – Problematic with Zigbee2MQTT or ZHA in Home Assistant, constantly losing connection
Enter the Aqara M100 Hub
Why add another hub? I was intrigued by its promise to handle both Aqara Zigbee devices and Thread devices, exposing them over Matter+WiFi to Home Assistant. Given my struggles with the Motion P1 and Thread devices, the current price point made it worth trying. The USB-powered hub doesn’t need to sit near my Home Assistant box, giving me flexibility to extend my network closer to problematic devices.
If you’re new to Thread and Matter, stay tuned for my upcoming write-up!
Setup Process
Step 1: Unboxing and Initial Setup
The M100 arrives without a power supply, requiring a USB-A power adapter. My first attempt to pair directly with Home Assistant showed the device but provided limited functionality.
Remember: The hub requires 2.4GHz WiFi. I blocked internet access AFTER the setup to ensure a cloud-free setup; but after a power outage the hub goes offline due to lack of internet access I have to investigate this further.
Since direct Home Assistant pairing proved ineffective, I installed the Aqara app (yes, account signup required). Setup was simple – just hold the button for a few seconds until it appeared in the app.
Step 2: Adding Devices
Within the app, selecting the hub and navigating to “Child Devices” allows adding devices. I paired the troublesome Motion P1 by following the manual device addition steps – completely pain-free! The motion sensor appeared in the Aqara app with impressively accurate detection. The app also offers options to scan QR codes, add Matter devices, and integrate third-party devices like Tesla and Sonos.
Step 3: Adding to Home Assistant as a Matter Device
This part seems confusing but is actually straightforward:
- In the Aqara app, select the M100 Hub
- Find “Third Party Matter Ecosystems”
- Select “Matter Pairing Code”
- Open the Home Assistant Companion app (important: must use the Companion app)
- Navigate to “Add Integration” and select “Add Matter Device”
- Choose “No, it’s New”
- Scan the QR code (I used a separate device) or select “Set up without QR Code” to manually enter the pairing code
Just like that, both the hub and motion sensor appeared in Home Assistant! The motion sensor has been running flawlessly for two days.
Step 4: Adding Thread/Matter Devices
The M100 Hub is marketed as a Thread border router and Matter controller, theoretically allowing direct integration of Thread-based Matter devices.
I’ve attempted to incorporate several Nanoleaf Essential Matter bulbs through the hub’s “Add Matter Device” option, but haven’t been successful despite trying:
- Factory resets
- Moving devices closer together
- Both QR code and manual pairing methods
Curiously, I’ve faced similar challenges pairing these bulbs with other Thread border routers, suggesting potential compatibility issues with either the bulbs or current Thread/Matter implementations.
I’ll continue testing as firmware updates become available and share findings in future updates.
Final Thoughts
After several days of testing the Aqara M100 Hub, I’m genuinely impressed with how it’s addressed my Zigbee reliability issues. The Motion P1 sensor that was practically unusable through direct Zigbee integration now works flawlessly when connected through this hub.
While the Thread/Matter integration hasn’t been as smooth sailing with my Nanoleaf bulbs, the primary use case of rescuing problematic Zigbee devices has been solved brilliantly. For anyone struggling with Aqara device reliability in Home Assistant, this hub offers a compelling solution that keeps everything local while providing the flexibility to position it optimally within your home.
The necessity of creating an Aqara account is a minor inconvenience, but with internet access blocked, the hub operates completely locally. At its current price point (around $50), it’s a worthwhile investment if you have Aqara devices that aren’t playing nicely with your direct Zigbee integration.
