Aqara vs Sonoff: The Honest Budget Smart-Home Ecosystem

Aqara and Sonoff sell to the same buyer: someone who wants a house full of sensors and switches without paying Philips Hue or Ecobee prices for each one. A door sensor from either brand runs about £10-£15, a fifth of what some premium ecosystems charge for the same magnet-and-reed-switch idea. Both companies got there the same way — high-volume Chinese manufacturing, thin margins, aggressive sales cadence on AliExpress and Amazon — but the two ecosystems solve the hub problem completely differently, and that difference is the actual decision, not the sensor price list.

What each company actually is

Aqara (a Lumi United Technology brand) builds a genuinely coherent ecosystem: hubs, sensors, switches, curtain motors, and locks that are all designed to work together, with a companion app that’s noticeably more polished than most budget-tier competitors and a hub lineup — the M1S, M2, M3 — that speaks Zigbee, and increasingly Matter over Thread on the newer hubs. Sonoff (a brand under Itead) is broader and messier: a huge catalogue spanning Wi-Fi relays, Zigbee sensors, a Zigbee bridge (the Sonoff Zigbee Bridge Pro), and its own NSPanel touch controllers, but with far less design coherence between product lines — some Sonoff devices are Wi-Fi-only, some are Zigbee, and knowing which is which requires reading the product page rather than trusting the brand name.

The hub strategy is the real fork in the road

Aqara’s hub is the more locked but more finished product. The M2 and M3 run Aqara’s own firmware, support Zigbee 3.0 and (M3) Thread/Matter, and integrate cleanly with Apple HomeKit, Google Home and Amazon Alexa through certified bridges — genuinely good multi-platform support for a budget brand. The catch is the ecosystem boundary: Aqara’s hub works best, and sometimes only works fully, with Aqara-branded sensors; third-party Zigbee devices pair inconsistently, and Aqara has occasionally tightened hub firmware in ways that broke community integrations, most notably restricting local API access on some hub generations in past firmware updates — a pattern that’s improved since but hasn’t fully gone away.

Sonoff’s approach is more fragmented but ultimately more open where it counts. The Sonoff Zigbee Bridge Pro can run stock firmware (Sonoff’s own eWeLink cloud ecosystem) or be reflashed to Zigbee2MQTT-compatible coordinator firmware, at which point it stops being a “Sonoff hub” at all and becomes a generic Zigbee coordinator feeding Home Assistant directly — the same open path covered in the Zigbee vs Wi-Fi comparison. That flexibility is Sonoff’s actual advantage: buy the hardware once, and the ecosystem lock-in is optional rather than structural.

Sensor range and build quality

Aqara’s sensor lineup is deeper and more specialised: door/window sensors, a genuinely well-regarded presence sensor (the FP2, using mmWave radar rather than passive infrared, which detects stillness — someone sitting reading — that a PIR sensor misses entirely), vibration sensors, and a smart lock line that’s rare at this price point. Build quality is consistently tidy — small, low-profile plastic housings, batteries rated for one to two years on the door sensors, and a matte finish that reads more premium than the ecosystem’s budget pricing suggests.

Sonoff’s catalogue is wider but shallower per category — door sensors and motion sensors that do the basic job reliably, but nothing matching Aqara’s FP2 presence sensor or its curtain-motor precision. Where Sonoff wins is raw category breadth: relays, dimmers, temperature/humidity sensors, and a genuinely useful line of DIY-friendly modules (the Sonoff Basic and Mini series) aimed squarely at the ESPHome and Tasmota crowd, letting a competent tinkerer wire a Sonoff relay into an existing light switch circuit for a fraction of what a retrofit smart switch from a bigger brand costs.

The housings themselves tell a similar materials story to the sensors inside them. Aqara’s plastic shells use a slightly heavier-gauge ABS with tighter tolerances at the seams — pick one up and there’s less flex, less rattle from the battery compartment, and a matte texture that resists fingerprints better than a glossy finish would. Sonoff’s sensor housings are functionally identical in concept but noticeably lighter and thinner-walled, with visible seam lines on some batches and a battery door that requires a firmer press to seat properly. Neither is going to fail from normal handling, but the tactile difference is the kind of thing a materials-eye read is for: Aqara spent marginally more on the plastic, and it shows in a small way every time the battery door gets opened.

Battery life is a category where the two brands diverge in a way spec sheets rarely make obvious. Aqara’s door and motion sensors typically ship with a CR2032 coin cell rated for one to two years of reported use, and community reports on Home Assistant forums broadly confirm that figure in practice, helped by Aqara’s sensors reporting on a longer default interval than some competitors. Sonoff’s equivalent sensors use similar coin cells but with a wider reported spread — some users report over a year, others report batteries dying within a few months, which tracks with Sonoff’s broader manufacturing base across product revisions meaning less consistency batch to batch than Aqara’s tighter, more centrally designed catalogue.

Cloud dependency and the local-control question

Both companies default to cloud accounts, and both let you route around it with different amounts of effort. Aqara’s hub retains some local processing for automations already configured, but full functionality and remote access assume Aqara’s cloud is reachable, and Aqara’s official Home Assistant integration has historically lagged behind community-maintained alternatives in exposing local control. Sonoff’s cloud (eWeLink) is more thoroughly optional: once a bridge is reflashed to a Zigbee2MQTT-compatible coordinator, or a Sonoff Wi-Fi device is reflashed to Tasmota, the eWeLink account is no longer in the loop for anything, which mirrors the local-first case made in the cloud-free smart plug guide.

Price and total ecosystem cost

Aqara’s individual sensors run £10-£25 depending on category, with the hub itself around £45-£70 for the M2/M3. Sonoff’s Zigbee sensors are comparably priced, generally £8-£20, but the bridge is cheaper — the Zigbee Bridge Pro runs around £20-£25, roughly half Aqara’s hub cost — and the DIY Wi-Fi relay line (Basic, Mini) starts under £10 per unit, undercutting anything in Aqara’s catalogue for a simple on/off switch. Fitting out a five-room house with door sensors, a couple of motion sensors and a hub lands within about £10-£15 of each other across the two ecosystems; the price gap that matters is at the DIY/relay end, where Sonoff is meaningfully cheaper for anyone willing to wire a module into an existing switch.

Sale timing moves both brands more than most gadget categories. Aqara and Sonoff both run frequent AliExpress and Amazon promotional events — the November sales period in particular routinely drops sensor prices by 30-40% below list — which matters more here than on a phone or a pair of headphones, because a full sensor rollout for a house is ten-plus individual purchases rather than one. Buying the hub at full price and timing the sensor purchases around a sale event is a genuinely effective strategy either ecosystem rewards, in a way that a single higher-ticket device rarely does.

App experience and the day-to-day gap

The polish difference shows up most clearly in the apps, not the hardware. Aqara’s app groups devices by room, supports scene automations with a genuinely usable visual builder, and surfaces battery levels and signal strength per device without digging through submenus — the kind of software investment a company makes when it’s betting on the ecosystem being the product, not just the sensors. Sonoff’s eWeLink app covers the same ground functionally but with a rougher interface, inconsistent naming conventions between device families (a hangover from acquiring and rebranding product lines rather than designing them together), and automation options that feel bolted on rather than native. Neither app matters much once a household has moved everything into Home Assistant, which is where both ecosystems end up for anyone serious about automation depth, but for someone staying inside the manufacturer app, Aqara’s is simply the nicer piece of software to live with day to day.

Matter and where both brands are heading

Both companies are moving toward Matter, but from different starting points. Aqara’s M3 hub already bridges Zigbee devices to Matter controllers (Apple Home, Google Home, Amazon Alexa) over Thread, meaning older Aqara sensors gain Matter compatibility without replacement — a genuinely useful migration path, since the sensor hardware doesn’t need to change, only the hub translating it. Sonoff has been slower to commit hub hardware to Matter specifically, leaning instead on the fact that a Zigbee2MQTT-flashed bridge feeding Home Assistant sidesteps the Matter question entirely, since Home Assistant itself increasingly acts as the Matter controller. Neither path is wrong, but they reveal the same philosophical split as the local-control question: Aqara is building a finished, branded product that adopts new standards from the top down; Sonoff’s ecosystem gets there by being open enough that the standard question becomes moot once Home Assistant is in the loop.

Mixing the two in one house

The realistic scenario for most budget-conscious households ends up as a mix of both brands rather than one picked exclusively, because a bargain during a sale event doesn’t respect brand loyalty. This actually works better than either company’s marketing implies, provided the hub layer is neutral. Running both Aqara and Sonoff Zigbee sensors through a single third-party coordinator — a SkyConnect, a ConBee II, or a Sonoff bridge reflashed away from its stock firmware — under Zigbee2MQTT means neither brand’s app is in the loop, and device compatibility comes down to standard Zigbee clusters rather than brand pairing quirks. The friction only appears when trying to keep both manufacturers’ own hubs running side by side, each with its own app, its own automation engine and its own idea of what a “scene” is — workable, but it duplicates effort a single Home Assistant instance would otherwise absorb, and it’s the scenario where the ecosystem-lock-in argument against branded hubs bites hardest.

The verdict

Buy either, depending on which trade-off actually matters in your house — this is a genuine split decision rather than one ecosystem beating the other outright. Choose Aqara if the priority is a coherent, better-finished sensor range with genuinely useful specialised hardware (the FP2 presence sensor has no real Sonoff equivalent) and you’re comfortable with a hub that’s more locked to its own brand. Choose Sonoff if the priority is minimising lock-in and cost, especially if there’s any appetite for reflashing bridges and relays to open firmware — the eventual system ends up more portable and cheaper per device, at the cost of a less polished starting experience and a catalogue that requires reading each product page rather than trusting the brand.

Price-wise, Aqara is worth its premium at full retail only if the FP2 sensor or the smart-lock line is actually wanted — for plain door/motion sensors, the price gap over Sonoff isn’t buying much extra function. Sonoff is worth buying at full retail for the DIY relay line specifically; the sensor range is fine but unremarkable next to Aqara’s. Skip either brand’s hub entirely, and go straight to a dedicated Zigbee coordinator (a SkyConnect, a ConBee II) running Zigbee2MQTT under Home Assistant, if the household already has the appetite to run its own hub software — at that point both companies’ sensors work fine as parts, and neither company’s hub adds anything a generic coordinator doesn’t do better.