Which Aqara Hub Should You Buy? M100 vs M200 vs M2 vs M3

All four models can coordinate compatible Aqara Zigbee devices and bridge supported functions into household platforms. The newer M100, M200 and M3 add Thread border-router and Matter-controller roles. A Thread border router connects a Thread mesh to the home's IP network; a Matter controller commissions and controls Matter accessories. Those jobs are separate from bridging existing Aqara Zigbee devices into Matter.

The M2 remains useful when the requirement is conventional Aqara Zigbee, Ethernet and 360-degree infrared control. It does not become obsolete simply because it lacks Thread. A home made mainly from Aqara Zigbee switches, sensors and curtains can continue to work well on an M2.

The M100 is powered through an adjustable USB-A plug. It can sit on a USB power adaptor, power bank or a suitable powered USB port without a separate cable. That makes it easy to place in a bedroom, study or a part of the home where a larger hub would be conspicuous.

It combines an Aqara Zigbee hub, Thread border router, Matter controller and Matter bridge. It is therefore more capable than its small enclosure suggests. It can commission supported Matter devices in Aqara Home, connect Thread devices to the local IP network and expose supported Aqara child devices to other Matter ecosystems.

Its limitation is infrastructure rather than protocol. The M100 has no Ethernet, PoE, infrared blaster or built-in alarm speaker. It also depends on the quality and position of the Wi-Fi and USB power source. Do not hide it behind a metal cabinet or place it at one extreme of a large layout merely because the plug is convenient.

The M200 is the broadest current general-purpose option. It combines Aqara Zigbee, a Thread border router, Matter controller and Matter bridge with dual-band Wi-Fi 6, PoE, USB-C power, a 90 dB speaker and 360-degree infrared control. One Ethernet cable can provide both data and power when the network switch or injector supports PoE.

Its infrared system is useful in Singapore because many split air-conditioners still rely on handheld IR remotes. The M200 can transmit commands, detect supported remote-control changes and expose one IR air-conditioner through a thermostat-like Matter mapping when paired with an Aqara climate sensor. An IR hub still needs line of sight within the same room; it is not a whole-home IR transmitter through walls.

The M200 also runs supported automations locally. Notifications, remote access and cloud integrations can still need internet, but a local sensor-to-light or climate routine need not stop simply because the broadband connection is unavailable.

The M2 is a mature Zigbee 3.0 hub with Wi-Fi, 10/100 Ethernet, a built-in speaker and 360-degree IR transmission. Aqara rates it for up to 128 compatible child devices, although real network design should leave capacity for growth and account for radio coverage rather than treating the headline number as a target.

It suits an existing installation that already works around Aqara Zigbee products and does not need the hub itself to act as a Thread border router or Matter controller. Ethernet is valuable when the router or network switch is nearby, and its IR blaster remains useful for air-conditioners, televisions and fans in the same room.

For a brand-new project, compare its price with the M200 before deciding. The newer model adds Thread, fuller Matter roles, dual-band Wi-Fi, PoE and updated IR feedback. Keeping an existing M2 is often sensible; buying one new is a more specific value decision.

The M3 was designed as an edge hub for larger Aqara systems. In addition to Zigbee, Thread and Matter roles, it can coordinate supported automations across other Aqara hubs. That matters when a sensor belongs to one hub and the controlled device belongs to another: supported cross-hub routines can be kept on the local system instead of depending on a cloud round trip.

It supports Ethernet with PoE, dual-band Wi-Fi and USB-C power. Its 360-degree IR blaster can learn and control compatible appliances, and the built-in speaker can handle alarms and custom sounds. It has no camera or microphone; Aqara stores configuration and supported automation data locally on the hub.

A single-flat installation does not automatically need an M3. Its case is strongest where several existing Aqara hubs must be brought under one local coordinator, where the M3's particular edge functions are wanted, or where a proven M3 design is already in place. For a new general-purpose purchase, compare it directly with the newer M200 rather than assuming the higher model number settles the choice.

Hub placement has four possible constraints. Zigbee and Thread are low-power 2.4 GHz meshes; Wi-Fi or Ethernet connects the hub to the router; IR requires open same-room coverage; and every hub needs dependable power. A position that is ideal for the air-conditioner may not be central to every sensor, while a network cabinet may be poor for radio and IR propagation.

Start in an open, reasonably central position away from a large metal enclosure, dense electrical equipment and the immediate side of a Wi-Fi access point. Mains-powered Zigbee routers can extend a Zigbee mesh, but most battery sensors do not repeat traffic. Thread has its own mesh and border-router roles; it does not use Zigbee repeaters.

For PoE models, plan the cable endpoint before carpentry closes. For IR, keep the hub visible to the appliance receiver. For USB-powered models, avoid switched sockets that occupants may turn off accidentally.

The home's router assigns network connectivity and carries IP traffic. An Aqara hub coordinates compatible Aqara child devices and translates supported functions between protocols and platforms. Buying a larger Aqara hub does not repair weak Wi-Fi coverage, replace a router or create Ethernet where none exists.

Likewise, a Thread border router is not the household internet router. It provides a path between a Thread mesh and the IP network. A home may have several Thread border routers from different platforms, but commissioning, credentials and platform support still determine which devices are visible where.

Separate these layers during troubleshooting. If the hub is online but a distant Zigbee sensor drops out, investigate the Zigbee path. If every IP device loses remote access, inspect the router or internet connection. If an IR command fails only from one position, inspect line of sight.

Most flats should begin with one well-positioned hub. Add a second only when the layout, radio measurements, device count, floor separation or room-specific IR requirement justifies it. More hubs create more placement options, but also more device ownership and automation boundaries to document.

A large or multi-storey home may need more than one coordinator. A compact M100 can also be used where a second Zigbee or Thread position is useful without duplicating IR and speaker hardware. The right expansion is based on the weak link observed in the actual home, not a fixed number of hubs per bedroom.