The Best Smart Plug That Doesn't Need the Cloud

Every smart plug promises the same thing on the box: turn any lamp or fan into something you can schedule and remote-control. Almost none of them tell you that the switch inside is entirely secondary to a cloud account you don’t own. Unplug the router, or have the manufacturer quietly shut down a backend — TP-Link retired several older Kasa cloud features this way, Belkin killed off a whole run of Wemo devices in 2023 by discontinuing app support outright — and a plug that cost £12 becomes a dumb switch you can no longer schedule, because the scheduling logic lived on a server in another country, not in the plug.

The alternative is a plug where the relay, the schedule and the power-metering logic all run locally: on the device itself, or on a hub sitting on your own network, with no dependency on an external service to keep working. That’s a genuinely different category of product, not just a marketing checkbox, and the difference shows up the day your internet goes down or the vendor pivots its business model.

What “local” actually means here

Three tiers exist, and they get conflated constantly.

Cloud-only is the majority of what’s on a supermarket shelf: the plug talks Wi-Fi directly to the manufacturer’s app, and every schedule, every “turn on at sunset” rule, and often the physical button itself route through that vendor’s servers. Kill the account, kill the feature. This is the Aqara vs Sonoff comparison’s cautionary baseline.

Local-API cloud is the middle tier: the plug still ships with a cloud app, but someone has reverse-engineered or the vendor has published a local control path — Tasmota and ESPHome firmware for the ESP8266/ESP32-based plugs, or Shelly’s documented local HTTP and MQTT API. The cloud account becomes optional rather than load-bearing.

True local-mesh is Zigbee or Thread plugs paired to a hub you control — Home Assistant with a Zigbee coordinator, an Aqara hub in local mode, or a Matter-over-Thread setup. The radio protocol itself has no internet dependency; only remote access (turning the lamp on from outside the house) needs anything beyond your own network, and that can be a self-hosted tunnel rather than the manufacturer’s relay.

The picks

Shelly Plus Plug S (~£15) is the strongest cloud-optional pick. It ships on Espressif’s ESP32 silicon, runs Shelly’s own firmware with a documented local HTTP/MQTT/CoIoT API out of the box — no third-party reflash required — and reports real-time power in watts down to roughly 0.1W resolution, which is accurate enough to catch a vampire-draw device. Point it at a local MQTT broker (the same one behind MQTT-based smart-home setups) and the cloud app becomes entirely optional; automations run through Home Assistant or Node-RED sitting on your own hardware. The catch is price: at roughly £15 it’s a premium over supermarket plugs, and the mounting shape is boxier than most sockets are used to sharing space with.

Aqara Smart Plug (Zigbee, ~£16) is the pick for houses already committed to a Zigbee mesh. It has no meaningful standalone Wi-Fi mode; it joins an existing Zigbee network — Aqara’s own hub, or a third-party coordinator like a SkyConnect or ConBee stick feeding Zigbee2MQTT — and once paired, control never leaves the local mesh unless you specifically ask for remote access. Power metering is present but coarser than the Shelly’s, reporting in roughly 1W steps rather than fractional watts, which is fine for “is this on” automations and less useful for measuring standby draw precisely.

Sonoff S26/S40 with Tasmota (~£10 after reflash) is the budget-local route, and the honest asterisk is the labour. The stock Sonoff firmware is cloud-dependent exactly like the plugs it’s competing against; the value only appears after flashing Tasmota or ESPHome onto the ESP8266 inside, which requires either a one-wire serial connection or (on some batches) an OTA-friendly stock firmware version that makes the swap possible without opening the case. Once flashed, it’s fully local, fully open-source, and roughly a third of the Shelly’s price — but you build it into a local plug yourself, starting from a cloud one.

Wyze Plug (~£15, avoid for this use case) is worth naming as the counter-example. Wyze markets itself on affordability and a broad device range, but the plug has no documented local API, and Wyze suffered a well-publicised 2022 camera vulnerability that took the company roughly three years to disclose — a track record that matters more for a company you’re trusting to keep a remote relay running indefinitely than the plug’s £15 price tag suggests.

The metering question nobody markets honestly

Power monitoring is the feature that turns a “smart” plug from a remote switch into something genuinely useful — spotting the appliance that draws 40W in standby, or the space heater still running three hours after you left the room — but the accuracy varies far more than the spec sheets admit. Shelly’s Plus Plug S uses a dedicated metering IC and reports current, voltage and power factor, letting it estimate real energy cost with reasonable confidence. Cheaper plugs, including most cloud-only supermarket units, often derive wattage from a simplified current sensor with no power-factor correction, which can overstate or understate draw on anything with a switching power supply — which is most modern electronics. If energy monitoring is the actual reason you’re buying the plug rather than remote scheduling, that’s worth reading the spec sheet for specifically; see the energy-monitoring smart plug piece for the maths on when the extra accuracy earns its keep.

Certification and the safety corner nobody skips for a good reason

A relay plug switching mains current is not a place to save money on certification, and this is where the “buy the cheapest local option” instinct needs a hard stop. UK sockets need a plug carrying the UKCA mark (or CE plus a UKCA sticker during the transition period), and the genuinely dangerous failure mode isn’t the smart features not working — it’s a relay rated for less current than the appliance actually draws, arcing under load, or the plastic housing being cheap enough that continuous use warms it past its rated temperature. Shelly and Aqara both publish independent test-lab certificates on request; a plug bought from a marketplace third-party seller with no visible certification mark and a price a third below the branded equivalent is the one to skip, no matter how good its local-API story looks in a forum post. This matters more for plugs than for most gadgets on this desk, because the failure mode isn’t “the app stops working” — it’s a socket getting warm behind a sofa.

Load rating is the other spec worth reading rather than assuming. Most smart plugs are rated to 13A (the UK socket standard), which comfortably covers lamps, small heaters and chargers, but a few budget imports are quietly rated lower — 10A or less — while still fitting a UK 13A socket without complaint. Running a 2kW space heater or an oil-filled radiator through an under-rated plug is the single most common way these things fail, and it’s a spec line that’s easy to skim past on a listing dominated by app-store screenshots.

Where Matter and Thread change the picture

The local-control argument used to mean picking a single ecosystem and living inside it — Zigbee locked you to a compatible hub, and a Wi-Fi cloud plug locked you to its own app. Matter is starting to loosen that, at least on paper: a Matter-certified plug can be added to Apple Home, Google Home or Home Assistant without a separate vendor app, and — critically for this guide — Matter’s specification requires local control over the local network as the baseline, with cloud relay as an optional extra rather than the only path. The honest caveat, covered at length in the two-years-on Matter review, is that the promise and the shipped reality still diverge: plenty of “Matter-enabled” plugs on shelves right now are Wi-Fi devices with a Matter bridge bolted on top of the same cloud-first architecture, not Thread-native devices with local control baked into the radio layer. Reading whether a specific plug is Matter-over-Wi-Fi or Matter-over-Thread — and whether Thread even matters here, since a plugged-in device doesn’t need Thread’s mesh-extension battery benefit the way a battery sensor does — is worth the extra thirty seconds on the product page before assuming “Matter” alone answers the local-control question.

Picks by use case

For a household starting from zero with no existing hub, the Shelly Plus Plug S is the sensible first purchase — local by default, no reflashing, and the local API means it slots into Home Assistant or a bare MQTT setup without extra work. For a house already running Zigbee2MQTT or a Home Assistant Zigbee coordinator, the Aqara plug is the cheaper, cleaner fit — one more device on a mesh that’s already local. For someone with a drawer of dead Sonoff plugs and a soldering iron, Tasmota reflashing turns sunk cost into a genuinely local fleet for less money than buying new — but budget an evening per device, not a weekend project you can rush.

What all three avoid is the actual risk this guide is about: a vendor’s cloud shutdown turning a working device into e-waste overnight. That’s not a hypothetical — it’s Wemo’s actual 2023 announcement, and it’s the reason “local” belongs on the spec sheet next to wattage and Wi-Fi standard, not buried in a forum thread after the fact.

Outdoor and higher-load exceptions

Everything above assumes an indoor socket switching a lamp or a charger, and the picks change once the use case is an outdoor string of fairy lights or a garden pump. IP-rated outdoor plugs are a much thinner market for local control specifically: Shelly’s outdoor-rated Plug S Gen3 exists and carries the same local API as the indoor version, but the outdoor Aqara and Sonoff equivalents are harder to find with confirmed local-mesh support, and a good number of “outdoor smart plugs” sold in multi-packs are simply an indoor relay in a weatherproof box, rated IP44 at best, meant for a covered porch rather than open exposure to rain. Checking the actual IP rating against where the socket will physically live — not just the “outdoor” word on the box — avoids a relay failing from moisture ingress within a season, which is a completely different failure mode from the cloud-dependency problem this guide is otherwise about, but ends the same way: a dead plug and a returns queue.

Higher-load appliances raise a second exception. A slow cooker, a window air-conditioning unit, or anything drawing close to a plug’s rated ceiling benefits from a plug with a genuinely reported temperature sensor, which the Shelly Plus Plug S includes and most budget plugs omit entirely. That temperature figure isn’t just a curiosity in the app — Shelly’s firmware uses it to auto-cut the relay if the internal temperature climbs past a safe threshold, an actual protective feature rather than a metering nicety, and one more reason the extra few pounds over a supermarket own-brand plug buys something more than an API.

Setting expectations on remote access

None of this guide’s local-first argument means giving up the ability to turn a lamp on from the office. It means that ability shouldn’t be the only path, and shouldn’t disappear the moment a vendor’s servers do. Home Assistant’s own remote-access options — a Nabu Casa subscription, or a self-hosted WireGuard tunnel back to the house — give the same “control it from anywhere” convenience a cloud plug promises, but the local automation keeps running on the LAN even if that remote path is down, which is precisely the failure mode a purely cloud-dependent plug can’t survive. It’s a slightly higher setup cost up front — an evening with Home Assistant rather than five minutes in an app store — for a system that doesn’t quietly stop working the day a company changes its roadmap.