The single most useful thing to understand before you buy either of these is that they are not really competitors. Both have "hub" on the box, both cost real money, and both show up in the same search - but the SwitchBot Hub 2 and the Aqara Hub M3 answer completely different questions. One is a sensor and a universal remote that happens to bridge SwitchBot's own gear into the big assistants. The other is a genuine multi-protocol controller that can run a house full of mixed-brand devices. Cross-shopping them as if they were rivals is how people end up with a hub that cannot see the sensors they just bought. Let us make sure that is not you.
What each box actually is
The Aqara Hub M3 is a whole-home brain. It is a Matter controller, a Thread border router and a Zigbee hub all in one, and it exposes the devices it runs to Apple HomeKit, Alexa and SmartThings. In plain terms, it can host third-party Zigbee sensors, provide the Thread border routing that Matter-over-Thread devices need, and act as the piece that ties a mixed-brand home together. Its only notable gap is Z-Wave. If you are assembling a smart home from more than one brand and want a single box to make them cooperate, this is that box, and the full Aqara Hub M3 review goes deep on exactly what it can host.
The SwitchBot Hub 2 is something else entirely, and its own listing is honest about it. It is a temperature, humidity and light sensor, an IR blaster that can control legacy TVs, fans and air conditioners, and a Matter bridge for SwitchBot's own accessories - pulling SwitchBot devices into Alexa, Google Home and Apple Home. What it is not is a Zigbee, Thread or Z-Wave hub. It has none of those mesh radios, so it cannot see or run third-party sensors. It is a clever, useful, inexpensive gadget with a specific job, not a whole-home controller - the point the SwitchBot Hub 2 review makes at length.
The question that decides it: what are you connecting?
Forget price for a moment and answer one thing: what devices do you need this hub to talk to? If the answer includes third-party Zigbee or Thread sensors, or the words "tie my different brands together," the Hub 2 is immediately ruled out - it does not have the radios, and no amount of setup will give it them. You need the M3 (or another multi-protocol hub). If the answer is "I mostly have SwitchBot stuff," or "I want to smarten my old air conditioner and get room temperature into my routines," the M3 is overkill and the Hub 2 is precisely designed for you. This is not a better/worse comparison; it is a right-tool comparison.
A concrete example makes it click. Say you want cheap Zigbee door and motion sensors around the house, feeding automations that also touch a Matter light and an old Thread-based gadget. Only the M3 can host that - Zigbee radio for the sensors, Thread border routing for the new stuff, Matter to expose it all. Now say instead you want to read your bedroom's temperature and humidity, have the smart home turn on a dumb window AC by learning its remote, and control a few SwitchBot curtains by voice. The M3 does none of the temperature-sensing or IR out of a matching purpose; the Hub 2 does all three in one cheap unit. Same category name, opposite jobs.
Where they briefly overlap - and why it is a trap
The one place these two seem to meet is Matter, and it is worth being precise so the overlap does not mislead you. Both can put devices into Alexa, Google and Apple Home via Matter - but the M3 is a Matter controller that can run and bridge a broad range of devices, while the Hub 2 is a Matter bridgefor SwitchBot's own accessories only. So "both do Matter" is true and misleading at the same time. If you read that as "the Hub 2 can bridge my non-SwitchBot Zigbee sensors to Matter," you will be disappointed - it cannot, because it has no Zigbee radio to hear them in the first place. Understanding that distinction is most of what separates a happy hub purchase from a returned one; our Matter vs Thread vs Zigbee guide unpacks why a bridge and a controller are not the same thing.
Cost, and the honest recommendation
Price tracks the class difference: the Hub 2 is the cheaper device, because it does less, and the M3 costs more because it is a proper controller with multiple radios. But price should be the last thing you weigh here, not the first - a cheap Hub 2 is no bargain if it cannot see the devices you want to run, and an M3 is money wasted if all you needed was a temperature reading and an IR blaster. Buy on capability first, price second.
So the recommendation is unusually clean. Buy the Aqara Hub M3 if you are building a mixed-brand smart home and need real Matter, Thread and Zigbee support in one box - it is our top hub pick and the right foundation for a growing setup. Buy the SwitchBot Hub 2if you own SwitchBot gear, want a built-in room sensor, or need to smarten a legacy IR appliance, and you do not need to host third-party mesh devices - it is excellent at that, and cheap. If you genuinely need both jobs done, they coexist happily: the M3 runs the mesh, the Hub 2 adds sensing and IR. The mistake to avoid is buying the Hub 2 expecting the M3's job. If you are still unsure whether you need a hub at all, start with do I need a smart home hub?
The usual honest caveat: we did not bench these two side by side. We read each device's own Amazon listing and manufacturer documentation for its radios, roles and ecosystem support, and compared them straight, crediting no capability a listing does not claim. The full method is on the methodology page.
