[ST Edge] Aqara Power Plug H2 EU RGB / SP-P05D / lumi.plug.aeu005 Zigbee Driver

Devices & Integrations Community Created Drivers
1

The Aqara Power Plug H2 EU (RGB) is one of Aqara’s newer dual-protocol smart plugs for the European market. It can operate either as a Matter-over-Thread device or as a Zigbee 3.0 device, and the RGB version combines a 16 A smart plug with energy monitoring, protection features and a fully controllable RGB indicator ring.

aqara-_01_c9adc9ed-f27f-4dbf-9c7c-1523369d0cd1
aqara-_01_c9adc9ed-f27f-4dbf-9c7c-1523369d0cd11024×1024 26.7 KB

The relevant device identifiers are:

  • Product: Aqara Power Plug H2 EU (RGB)
  • Retail model: SP-P05D
  • Zigbee model: lumi.plug.aeu005
  • Wireless protocols: Thread, Zigbee and BLE
  • Electrical rating: 100–240 VAC, 50/60 Hz, up to 16 A
  • Maximum resistive load: 3680 W at 230 V
  • Socket: Type E/F
  • Network role: Zigbee router or Thread router, depending on the selected protocol

Aqara also offers a non-RGB version, the SP-P05E. Current production firmware information identifies that model as lumi.plug.aeu004, while the RGB SP-P05D uses lumi.plug.aeu005.

In addition to normal on/off control, the SP-P05D monitors electrical consumption, provides overload and overheat protection, supports charging protection and a child lock, and includes an RGB indicator that can be used either as a normal colored light or as a visual representation of energy consumption.

Matter or Zigbee?

The H2 EU RGB can be connected directly to SmartThings through Matter over Thread, so a custom driver is not required for basic integration. Current H2 firmware also supports the Matter energy-measurement clusters introduced with Matter 1.3, and SmartThings can display Matter energy data.

Zigbee becomes interesting when the Aqara-specific configuration options are wanted. Aqara documents several functions as Zigbee-only, including the configurable load limit, advanced indicator behavior and the RGB energy-visualization modes. This Edge driver accesses those Zigbee functions directly from a SmartThings Hub, without requiring an Aqara hub after the plug has been placed in Zigbee mode.

The table below compares the practical SmartThings experience rather than every internal capability of the hardware:

Feature in SmartThings Matter over Thread Zigbee with this Edge driver
Socket on/off Yes Yes
Local operation Yes Yes
Direct SmartThings integration without an Aqara hub Yes Yes
Required mesh infrastructure Matter Controller + Thread Border Router SmartThings Hub with Zigbee
Mesh-router role Thread router Zigbee router
Real-time power Yes, with current Matter firmware Yes
Accumulated energy Yes, with current Matter firmware Yes
Current measurement Yes, with current Matter firmware Yes
Voltage measurement Yes, with current Matter firmware Not currently exposed
RGB indicator exposed as a separate light Yes Yes
RGB brightness / color control Yes Yes
Color temperature Platform/device presentation may vary Yes
Child-lock setting exposed in SmartThings Not a standard Matter plug control Yes
Charging-protection setting exposed in SmartThings Not a standard Matter plug control Yes
Configurable overload limit Aqara documents this as Zigbee-only Yes
Reverse / flip indicator behavior Aqara documents this as Zigbee-only Yes
RGB visualization of live power No Yes
RGB visualization of daily energy No Yes
RGB visualization of monthly energy No Yes
Configurable RGB power/energy gradient limits No Yes
Matter Multi-Admin / cross-platform sharing Yes No, not for a directly paired Zigbee device
Aqara accidental-removal protection No Device supports it in Zigbee mode; not implemented in this driver yet

For users who primarily want standardized interoperability and Multi-Admin, Matter is an entirely reasonable choice. The main reason for using this Zigbee driver is access to the richer Aqara-specific feature set and direct control over how those functions are represented in SmartThings.

Aqara officially supports Zigbee mode with Aqara hubs. Direct Zigbee pairing to SmartThings using this community Edge driver is therefore not an Aqara-supported configuration.

The RGB indicator

The RGB ring is more than a conventional status LED. It can be controlled as a light, with on/off state, brightness, color and color temperature, but it can also visualize the plug’s own energy data.

The available indicator modes are:

  • Fixed color
  • Current power consumption
  • Daily energy consumption
  • Monthly energy consumption

In the consumption modes, the plug maps the measured value onto a color gradient. The upper end of that gradient can be configured separately for instantaneous power and accumulated energy.

This allows the indicator to show, for example, whether a connected appliance is drawing little or a lot of power without opening the SmartThings app. In fixed-color mode, it can instead be used as a general SmartThings status light for routines, alerts or reminders.

Driver features

The Edge driver represents the plug as two logical SmartThings components so that the electrical outlet and RGB indicator can be used independently.

Main component

plug1
plug11080×2400 170 KB

The main component represents the actual socket and provides:

  • On/off control
  • Real-time power measurement
  • Accumulated energy consumption
  • Current measurement
  • Refresh

LED component

plug2
plug2921×2048 71.7 KB

The separate LED component represents the RGB indicator and provides:

  • On/off control
  • Brightness
  • RGB color
  • Color temperature

This arrangement makes the device useful in routines without tying the indicator to the electrical state of the socket. A washing machine can remain powered, for example, while the RGB ring turns green when a cycle has completed, or the indicator can show an unrelated SmartThings status without changing the connected appliance.

Driver settings

plug3
plug31080×2400 176 KB

The following Aqara-specific settings are currently available directly in the SmartThings device settings.

Child lock

Disables normal operation of the physical button while remote control through SmartThings and routines remains available.

The physical button can still be used for network or factory reset. Aqara provides a stronger accidental-removal protection in Zigbee mode, but that function is not yet exposed by this driver because its Zigbee attribute mapping has not been verified.

Charging protection

When enabled, the plug automatically switches off after the connected load remains below approximately 3 W for 30 minutes.

Unlike the older Aqara H2 wall outlet, the SP-P05D does not appear to expose an adjustable low-power charging threshold; the 3 W / 30 minute behavior is defined by the device.

Power-on behavior

Controls the outlet state after mains power has been interrupted and restored.

Available options are:

  • On
  • Off
  • Previous state
  • Inverted/opposite state

Overload protection

Sets the maximum permitted load before the plug’s protection logic switches the outlet off.

The driver deliberately limits the SmartThings setting to 3680 W, matching the rated maximum resistive load of the EU product.

Flip indicator behavior

Reverses the normal relationship between the socket state and indicator behavior.

RGB indicator mode

Selects whether the RGB ring uses a fixed color or represents energy consumption:

  • Fixed color
  • Current power consumption
  • Energy consumption per day
  • Energy consumption per month

RGB power scale maximum

Defines the upper end of the RGB gradient when the indicator represents instantaneous power.

For example, with a value of 2000 W, the complete color range corresponds approximately to 0–2000 W.

RGB energy scale maximum

Defines the equivalent upper value for the daily or monthly accumulated-energy visualization.

Example SmartThings routines

Because the plug combines metering and a separately controllable RGB indicator, several useful routines can be implemented with a single physical device.

Washing machine finished

A routine can monitor the live power value and, once consumption remains below a chosen threshold for several minutes, send a notification and set the RGB indicator to green. The appliance remains connected while the indicator provides an immediate visual confirmation.

High-load warning

If the measured power rises above a selected value, SmartThings can turn the RGB indicator red while leaving the socket itself on. This provides a visible warning before the configured hardware overload threshold is reached.

Standby shutdown

For televisions, computers, chargers or other appliances with recognizable standby consumption, a routine can turn the socket off after power remains below a specified level for a chosen period.

General status indicator

The RGB component does not have to represent the plug at all. It can be used to indicate SmartThings Home Monitor state, an open door, an alarm condition or any other routine state while leaving the socket untouched.

Installation

The driver is available through my SmartThings Edge Driver channel:

SmartThings Edge Driver channel invitation

  1. Open the channel invitation and sign in with the Samsung account associated with the SmartThings location.
  2. Enroll the SmartThings Hub that should receive the driver.
  3. Open Available Drivers and install Aqara H2 Power Plug EU RGB.
  4. Make sure the SP-P05D is already operating in Zigbee mode.
  5. Start Zigbee pairing mode. A rapidly flashing purple indicator means Zigbee pairing; blue indicates Thread/Matter mode.
  6. In the SmartThings app, select Add device and start a nearby-device scan.
  7. With the driver installed before pairing, a production SP-P05D identifying as lumi.plug.aeu005 should be matched automatically.

The H2 family ships in Thread/Matter mode on first setup. Aqara’s documented protocol-switching process is performed during setup in the Aqara Home app. The exact Aqara-side workflow can depend on the app and hub combination, but for direct SmartThings Zigbee pairing the important point is that the plug must already be in Zigbee mode and flashing purple before SmartThings scans for it.

For reference, the documented button operations include:

  • Double press, then hold for approximately 5 seconds: reset and enter pairing mode
  • 10 consecutive presses: factory reset and enter pairing mode
  • Purple rapid flashing: Zigbee pairing
  • Blue rapid flashing: Thread/Matter pairing
  • Single press: toggle the relay
  • Triple press: identify / locate the device

If the plug has previously been paired through Matter or with another Zigbee driver, a clean reset and re-pair is recommended.

Current status

Hardware validation with a production SP-P05D is in progress.

The first release is intentionally conservative. Features are included only where there is sufficiently strong evidence for their Zigbee implementation; voltage and internal device temperature, for example, are not exposed merely because related Aqara devices support them.

The initial hardware tests are intended to confirm:

  • automatic lumi.plug.aeu005 fingerprint matching
  • socket relay control
  • live power, energy and current values
  • manufacturer-specific settings
  • RGB on/off, brightness, color and color-temperature behavior
  • RGB energy-visualization modes
  • complete isolation between RGB commands and the mains relay

This section will be updated with confirmed test results once hardware validation is complete.

Technical details

Click here

The SP-P05D is considerably more unusual internally than its appearance suggests. The main reason a dedicated driver is useful is that the electrical outlet and RGB indicator are logically separate devices even though the relevant Zigbee functions share the same physical endpoint.

Device identity

Current production firmware information identifies the RGB model as:

Manufacturer: Aqara / LUMI
Model:        lumi.plug.aeu005
Retail model: SP-P05D
Manufacturer code: 0x115F

The non-RGB SP-P05E is listed separately as lumi.plug.aeu004.

Some early information identified an RGB H2 EU as lumi.plug.aeu004. A pre-production Zigbee interview appears to be the source of that conflict. Current firmware records distinguish the production devices clearly, so this driver fingerprints only:

Aqara / lumi.plug.aeu005
LUMI  / lumi.plug.aeu005

Adding aeu004 would risk claiming production non-RGB plugs.

Endpoint and cluster architecture

Current implementation evidence places the main functions on endpoint 1.

Relevant clusters include:

Cluster Function
0x0006 On/Off
0x0300 Color Control
0x0B04 Electrical Measurement
0xFCC0 Aqara manufacturer-specific

The unusual part is that the mains relay and RGB indicator share endpoint 1.

Normal Zigbee lighting logic often assumes that On/Off, Level Control and Color Control belong to the same logical light. That assumption is unsafe on the SP-P05D because the standard 0x0006 On/Off cluster controls the electrical outlet.

For example, a normal light implementation may use MoveToLevelWithOnOff, where setting brightness to zero can generate an implicit Off operation. On this plug that behavior can affect the mains relay.

The Edge driver therefore applies a strict separation:

main.switch
    -> endpoint 1 / OnOff 0x0006
    -> mains relay

led.switch
    -> endpoint 1 / Aqara 0xFCC0 attribute 0x0203
    -> RGB indicator

led.switchLevel
    -> MoveToLevel
    -> never MoveToLevelWithOnOff

led.colorControl
    -> Color Control / CIE XY

led.colorTemperature
    -> Color Control / color temperature

The LED handlers do not invoke SmartThings’ generic Zigbee switch defaults, and an unknown component command is never allowed to fall through to the mains relay.

This relay/LED collision is also handled explicitly by the recent Zigbee2MQTT H2 RGB converter, which disables the normal level-with-OnOff behavior for the same reason.

Electrical measurements

Instantaneous active power is obtained through the standard Zigbee Electrical Measurement cluster:

Cluster:   0x0B04
Attribute: ActivePower / 0x050B

Current H2 RGB implementation evidence indicates that ActivePower is reported directly in whole watts. The driver therefore uses a 1:1 multiplier/divisor rather than importing the /10 scaling used by some older Aqara plug implementations.

Energy and current are supplied through Aqara’s manufacturer-specific aggregate report:

Cluster:   0xFCC0
Attribute: 0x00F7

The relevant Aqara TLV tags are:

Tag Meaning Driver interpretation
0x95 Accumulated energy kWh
0x97 Current mA converted to A
0x98 Power Secondary/fallback power value
0x96 Voltage on some Aqara devices Not currently observed/exposed for this model

The driver uses 0x0B04 ActivePower as the primary power source and treats tag 0x98 as a fallback. A general Aqara TLV decoder is used instead of relying on fixed byte offsets, so aggregate packets remain parseable when tags are omitted, reordered or supplemented.

The current Zigbee implementation does not expose voltage or internal device temperature in SmartThings. The recent H2 RGB Zigbee2MQTT implementation likewise removes voltage and device-temperature exposes for this device.

The driver also avoids depending on Endpoint 21, Analog Input or Simple Metering. Those appeared in an early pre-production interview, while the current aeu005 implementation obtains live power from Electrical Measurement and energy/current from the Aqara aggregate.

Aqara manufacturer-specific attributes

The advanced settings are carried through Aqara’s manufacturer-specific cluster:

Cluster:           0xFCC0
Manufacturer code: 0x115F

The driver currently implements:

Attribute Type Function
0x00F0 UInt8 Flip / reverse indicator behavior
0x0202 Boolean Charging protection
0x0203 Boolean RGB indicator on/off
0x020B Float Overload threshold
0x0285 UInt8 Child lock
0x02DF UInt8 RGB indicator mode
0x02E0 Float RGB power-gradient maximum
0x02E1 Float RGB energy-gradient maximum
0x0517 UInt8 Power-on behavior
0x00F7 Aggregate Measurement data

The RGB indicator-mode mapping is:

Value Mode
0 Fixed color
1 Current power consumption
2 Energy consumption per day
3 Energy consumption per month

Several settings use IEEE-754 single-precision floating-point values instead of ordinary integer Zigbee attributes. The driver therefore includes explicit Aqara manufacturer-specific read/write helpers and float handling.

Settings are not overwritten automatically when the device joins SmartThings. The existing physical configuration is read first, and manufacturer-specific writes are performed only after the corresponding SmartThings preference is changed. Writes are followed by readback verification.

RGB color implementation

The H2 RGB Zigbee implementation uses CIE XY color.

SmartThings normally represents color as hue and saturation, so the driver converts between the two representations:

SmartThings HSV
    -> CIE XY
    -> Zigbee Color Control

Incoming reports are converted in the opposite direction:

Zigbee CurrentX / CurrentY
    -> HSV
    -> SmartThings colorControl

Rapidly arriving hue and saturation commands are briefly coalesced before the final XY command is transmitted. This prevents intermediate color changes caused by combining a new hue with the previous saturation value, or vice versa.

Color temperature is handled independently through the Zigbee Color Control cluster. The driver uses the reported physical color-temperature range where available and falls back to approximately 2700–6500 K.

Reporting and configuration

Automatic Zigbee configuration is deliberately conservative.

Some recent Aqara devices expose standard clusters while omitting attributes that generic integrations normally expect. The H2 RGB has been reported to return UNSUPPORTED_ATTRIBUTE for several normal Electrical Measurement multiplier/divisor attributes, and probing all of them can interrupt configuration in other Zigbee integrations.

The driver therefore configures reporting only for the standard values known to be useful:

  • Outlet On/Off state
  • Active power

Manufacturer-specific settings are handled through explicit reads, unsolicited reports and read-after-write verification rather than assuming that Configure Reporting will work reliably for every 0xFCC0 attribute.

Sources and related work

The implementation and this post are based on several independent sources. The most important references are:

The driver also reuses design principles and proven implementation ideas from previous Aqara SmartThings Edge work, especially the Aqara H2 Wall Outlet, Aqara H2 Wall Switch and Aqara LED Bulb T2 drivers. The H2 Wall Outlet provided the basis for manufacturer-specific reads/writes and Aqara aggregate parsing, while the T2 bulb provided the established CIE XY color-conversion approach.

Known limitations

  • Hardware validation of the first SmartThings build is still in progress.
  • The driver currently targets production lumi.plug.aeu005 only.
  • Voltage is intentionally not exposed in Zigbee mode because no reliable production aeu005 Zigbee source has been confirmed.
  • Internal device temperature is not exposed as a SmartThings capability.
  • Aqara accidental-removal protection is not implemented until its Zigbee attribute mapping is verified.
  • OTA firmware updating is not implemented by this community driver.
  • Aqara does not officially support direct Zigbee pairing of this device to SmartThings; this is a community-created Edge integration.

Disclaimer

This is a community-created SmartThings Edge driver. It is not an official SmartThings or Aqara release and is not maintained, reviewed or supported by either company.

As with any smart plug controlling mains-powered equipment, automations should be tested carefully, particularly when controlling unattended loads or devices where an unexpected switch operation could have safety consequences.

3 Likes
Aqara smart plug features with Aeotec Smart home hub