ZNCZ11LM (lumi.plug.aq1): `state` becomes OFF by itself while the relay stays on and power remains ~30W

What happened?

ZNCZ11LM (lumi.plug.aq1): state becomes OFF by itself while the relay stays on and power remains ~30W

Environment

Item	Value
Zigbee2MQTT	2.13.0
Coordinator	SLZB-06MU, ember, firmware 8.0.2 [GA]
Serial	tcp://<coordinator>:6638
Model	Aqara ZNCZ11LM
Zigbee model	lumi.plug.aq1
Hardware	hw 18 (no OTA)
Device page	https://www.zigbee2mqtt.io/devices/ZNCZ11LM.html
Definition	source: native, description: Smart plug
Load	~30W display / appliance. The relay stays closed; the load stays powered.

I have three plugs of this same model on the same network:

Name in this report	IEEE
Plug 1	0x00158d0001de0b09
Plug 2	0x00158d0001de0a86
Plug 3	0x00158d0001de0a40

The detailed logs below are from Plug 3 (0x00158d0001de0a40) on the stock official definition. Plug 1 and Plug 2 show the same behavior when they also use the official converter.

---

What happens

The plug is physically on. The load is drawing power. power keeps reporting 30–33W, and device_temperature rises.

With no one touching the UI or the button, state changes to OFF by itself.

This is not a stale power value after a real turn-off. After state becomes OFF, power still updates, and temperature keeps going up.

All three plugs do this when they use the official converter. It is not one broken unit.

---

How to reproduce

1. Pair ZNCZ11LM with the official definition (no external converter).
2. Turn the relay on (physical button or a successful set) and connect a ~30W load.
3. Confirm MQTT once shows state: ON and power ≈ 30.
4. Do not send any further commands. Wait for the next device reports (usually within a few minutes).
5. state changes to OFF by itself. In the capture below, power stayed 32.93 in that same report.

---

Timeline (2026-08-21, UTC+8)

Device: Plug 3 / 0x00158d0001de0a40, official native definition.
I turned the plug on at 10:53:06 and did not touch it afterwards.

Time	state	power	device_temperature	Notes
10:53:06	ON	32.93 W	56°C	I turned it on
10:56:54	ON	32.93 W	57°C	Heartbeat still correct
11:00:37	OFF	32.93 W	57°C	No user action. Same MQTT report.
11:00:46	OFF	32.93 W	57°C	Home Assistant followed MQTT

The relay did not open. The load stayed powered.

---

MQTT payloads

After I turned it on (10:56:54):

{
  "auto_off": null,
  "consumption": 0.14410196244716644,
  "device_temperature": 57,
  "energy": 0.14,
  "led_disabled_night": null,
  "linkquality": 176,
  "power": 32.93,
  "power_outage_count": 2,
  "power_outage_memory": null,
  "state": "ON",
  "voltage": 233.1
}

About 4 minutes later, no command sent (11:00:37). state became OFF. power was still 32.93 in the same report:

{
  "auto_off": null,
  "consumption": 0.14410196244716644,
  "device_temperature": 57,
  "energy": 0.14,
  "led_disabled_night": null,
  "linkquality": 172,
  "power": 32.93,
  "power_outage_count": 2,
  "power_outage_memory": null,
  "state": "OFF",
  "voltage": 233.1
}

---

Extra info

• Zigbee2MQTT: 2.13.0
• Coordinator: ember / 8.0.2 [GA]
• Device: ZNCZ11LM / lumi.plug.aq1 / 0x00158d0001de0a40
• Frontend: definition.source = native

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.13.0

Adapter firmware version

EmberZNet 0x540f57fffec1f5aa Revision: 8.0.2 [GA]

Adapter

SLZB-06MU, ember, firmware 8.0.2 [GA]

Setup

Add-on on Home Assistant OS on Intel NUC

Device database.db entry

No response

Debug log

ZNCZ11LM_plug3_debug.log

I captured this log again; I didn't record the log described earlier, but this one also reflects the status.

Notes

No response

Start with the attached ZNCZ11LM_plug3_debug.log and the native ZNCZ11LM device definition linked in the report. Trace the incoming status report containing power 32.93 W and determine why its state is published as OFF; done means reproducing the report with the relay still on and preserving the correct ON state.