“Aqara Smart Plug” isn’t one device. It’s at least three, sold under nearly identical names in different regions, with different model numbers printed in small text on the box: SP-EUC01 in Europe, ZNCZ12LM in the US, and ZNCZ15LM (marketed as the “T1”) in China. All three pair to Zigbee2MQTT, all three do power monitoring, and all three look similar enough in photos that a reader following a setup guide written for one variant can easily end up staring at a Zigbee2MQTT device page that doesn’t match what they’re seeing.
This is a side-by-side of what each variant actually exposes — and, where it matters, which of those exposed settings other people have found don’t work. It’s sourced from the three official Zigbee2MQTT device pages, Aqara’s regional spec pages and this site’s own setup guide for each model, not from marketing copy.
Why there are three of these
Aqara sells region-locked hardware variants rather than one global SKU, and the smart plug line is a clear example. SP-EUC01 targets EU mains and EU retail channels, ZNCZ12LM is the US part, and ZNCZ15LM is the newer “T1” generation sold in China. The model-number-to-generation naming isn’t obvious from the outside — if you want the general pattern behind Aqara’s model codes and generation labels, that’s covered separately in the model naming convention guide; this article sticks to what’s specific to the smart plug line.
All three variants pair to Zigbee2MQTT and run fully local — none of the differences below affect whether the plug works without Aqara’s cloud, only which features are available once it’s paired.
Identifying which one you have
The model number is the source of truth — not the box art, not the app listing, not the color. Two reliable places to check:
- The label on the plug itself. SP-EUC01, ZNCZ12LM, and ZNCZ15LM are printed on a small sticker on the plug body, usually on the side facing away from the outlet.
- The Zigbee2MQTT device page, once paired. Z2M matches your unit to a device definition and links to that model’s page — the same three pages the comparison below is built from.
If a setup guide’s screenshots or exposed-entity list don’t match what’s showing up in your Zigbee2MQTT instance, that’s usually the first sign you have a different regional variant than the guide assumes — not a bug.
Feature comparison: what each variant exposes
All three share the same core power-monitoring capability. Where they diverge is in two convenience features: auto_off, which switches the socket off by itself once the attached load has stayed under 2W for 20 minutes, and button_lock, which disables the plug’s physical button so it can’t be toggled by hand.
| Model | Region | Electrical rating | auto_off | button_lock |
|---|---|---|---|---|
| SP-EUC01 | EU | 250V AC, 50/60Hz, 10A, max 2300W | Yes | Yes |
| ZNCZ12LM | US | 100–125V AC, 60Hz, 15A, max 1875W | Exposed, reported broken | No |
| ZNCZ15LM (T1) | CN | 220–240V AC (Chinese mains); Z2M overload cutoff settable to 2500W | No | Yes |
SP-EUC01 exposes both settings. ZNCZ12LM exposes auto_off but not button_lock. ZNCZ15LM exposes button_lock but not auto_off. If you were expecting a button lock on a US-region plug, or a standby cutoff on the CN/T1 variant, that entity genuinely isn’t in the device definition for your model — it isn’t a setting hiding somewhere in your install.
Exposed is not the same as working
On the ZNCZ12LM (US), three of the exposed settings — auto_off, led_disabled_night and overload_protection — are widely reported not to take effect. Writes come back as an UNSUPPORTED_ATTRIBUTE error in the Zigbee2MQTT log (tracker issue #20430, “Supported features not working”). The controls appear in the interface either way, so an automation built on them can look configured and do nothing.
That matters for this comparison specifically, because auto_off is the ZNCZ12LM’s only feature advantage over the T1 — and on the reports available it’s the one you can’t rely on. Our full ZNCZ12LM setup guide covers the workarounds; the practical substitute is a Home Assistant automation watching the power sensor and switching the plug off below a threshold, which behaves the same on all three variants.
No equivalent reports surfaced for the SP-EUC01 or the ZNCZ15LM in the sources checked here. That’s not confirmation that every exposed setting writes cleanly on those two — only that nobody has filed it.
What’s identical across all three
The core power-monitoring exposes are consistent across the whole line: switch (state), power, energy, voltage, current, device_temperature and power_outage_memory. All three also list led_disabled_night, consumer_connected and overload_protection, with the ZNCZ12LM caveat above attached to two of those.
Nothing in the regional split changes which power-related data you get or how it’s reported. If you’re troubleshooting power-monitoring readings specifically — values not updating, registering zero, or looking wrong — that’s a separate failure mode already covered in the power monitoring troubleshooting guide; this comparison doesn’t re-cover that ground.
The region-swap caveat
The three variants have genuinely different electrical ratings — this isn’t just a Zigbee pairing question. SP-EUC01 is rated 250V AC / 10A / 2300W max; ZNCZ12LM is rated 100–125V AC / 60Hz / 15A / 1875W max; ZNCZ15LM is built for 220–240V Chinese mains. Ordering the wrong-region variant for your local mains supply is an electrical-rating mismatch, not something Zigbee2MQTT configuration can work around.
If you’re buying rather than identifying a plug you already own, match the variant to your region’s mains voltage first. A plug rated for one mains voltage range doesn’t become safe for another just because it pairs successfully to Zigbee2MQTT.
Known friction: SP-EUC01 self-toggle reports
A community-reported issue on the Zigbee2MQTT tracker (issue #13903, opened 2022-09-07 and since closed without an official fix) describes SP-EUC01 units toggling on or off with no command sent, after an OTA update to firmware v42, in setups where the plug was also routing Zigbee traffic for other devices. The reported trigger is IKEA remotes — the E1812 shortcut button and E1743 on/off switch — whose frames pass through the plug as a mesh hop. The workaround discussed in the thread is downgrading to v32, which needs a modified firmware header to get past Aqara’s downgrade block; our SP-EUC01 setup guide covers that procedure and the firmware situation since.
Treat this as a firmware-specific community report tied to one generation of hardware, not a universal defect across all SP-EUC01 units or all firmware versions. No equivalent report surfaced for ZNCZ12LM or ZNCZ15LM in the sources checked for this article.
Frequently asked questions
How do I tell which Aqara smart plug model I have? Check the model number printed on the plug body (SP-EUC01, ZNCZ12LM, or ZNCZ15LM), or pair it to Zigbee2MQTT and check which device page it resolves to.
Is the Aqara Smart Plug EU the same as the US version? No. SP-EUC01 (EU) and ZNCZ12LM (US) are different model numbers with different electrical ratings and a different feature split — SP-EUC01 exposes both auto_off and button_lock; ZNCZ12LM exposes auto_off only, and that setting is widely reported not to work on it.
Why doesn’t auto_off do anything on my ZNCZ12LM? Because on that model it’s a known problem, not a configuration mistake. Writes to auto_off, led_disabled_night and overload_protection are reported to fail with UNSUPPORTED_ATTRIBUTE on the ZNCZ12LM. Use a Home Assistant automation on the power sensor instead.
Does the Aqara smart plug T1 (CN) work outside China? It pairs to Zigbee2MQTT the same as the other two, but it’s built for 220–240V Chinese mains — an electrical fit for regions on that voltage range, and wrong for 100–125V ones. Check your mains voltage and socket type before using it outside its target market.
Which Aqara smart plug supports a physical button lock? SP-EUC01 (EU) and ZNCZ15LM/T1 (CN) both expose button_lock. ZNCZ12LM (US) does not.
Can I use an EU Aqara smart plug in the US (or vice versa)? Not safely without checking the electrical ratings — SP-EUC01 and ZNCZ12LM are rated for different voltage ranges and maximum loads. This is a mains-electrical question independent of Zigbee pairing.
What this verified, what stays local, and what to check yourself
This comparison is research-synthesis from the three variants’ official Zigbee2MQTT device pages (SP-EUC01, ZNCZ12LM, ZNCZ15LM), Aqara’s EU and US regional spec pages, and this site’s own published setup guide for each model. No claim here depends on hardware this site owns, and nothing is presented as hands-on tested.
Verified against those sources: the exposes list for each variant, the auto_off/button_lock split, the EU and US electrical ratings as published on Aqara’s own regional spec pages, and the ZNCZ15LM’s 220–240V CN mains target with an overload cutoff settable up to 2500W in its Zigbee2MQTT definition. Aqara publishes no English spec page for the CN T1, so its exact amperage and maximum wattage are worth reading off the label on your own unit. The auto_off failure on the ZNCZ12LM is sourced to community reports and this site’s earlier guide, not to any Aqara acknowledgement — no vendor statement or firmware fix exists for it. The self-toggle report is sourced to a GitHub issue with a confirmed opened date; its exact last-activity date wasn’t verifiable here, so nothing in this article rests on when it was last touched.
What stays local: all three pair to and are controllable through Zigbee2MQTT with no Aqara account and no cloud connection once paired. The ZNCZ12LM’s non-functional settings are a firmware limitation, not a cloud dependency — nothing about them improves by adding Aqara’s hub.
What to check for your own unit: confirm your exact model number from the label or your paired Zigbee2MQTT device page before assuming any feature in this comparison applies to your hardware, then follow the matching full setup guide — SP-EUC01 (EU), ZNCZ12LM (US), or ZNCZ15LM/T1 (CN) — for pairing steps and entity configuration specific to your variant.