
This device communicates via Zigbee through a Tasmota gateway. Make sure you have the Zigbee2Tasmota Gateway template imported and your device paired before proceeding.
The Aqara WSDCGQ11LM is a compact battery-powered Zigbee sensor that measures ambient temperature, relative humidity and atmospheric pressure. It communicates with TapHome over MQTT through a Zigbee2Tasmota gateway — the sensor sends periodic readings via the tele/{gateway}/SENSOR topic, and the template parses the ZbReceived JSON payload.
The sensor is powered by a CR2032 coin cell battery. The template monitors battery level and voltage via service attributes, warns when battery drops below 30%, and detects device offline states (warning after 12 hours, error after 24 hours).
Configuration
Pairing the sensor
- On the Zigbee2Tasmota gateway, enable Permit Join (via the gateway template switch in TapHome or Tasmota console command
ZbPermitJoin 1) - Press and hold the reset button on the Aqara sensor for approximately 5 seconds until the blue LED blinks
- Release the button — the sensor should pair within 60 seconds
- Note the assigned Device ID (e.g.,
0x1234) from the gateway’s service attributes or Tasmota console
Import parameters
After pairing, import the device template with these parameters:
| Parameter | Description | Example |
|---|---|---|
| MQTT Broker IP Address | IP of the MQTT broker | 192.168.1.10 |
| MQTT Broker Port | Broker port (default 1883) | 1883 |
| Gateway name | Tasmota MQTT topic (Configuration → MQTT → Topic) | tasmota_XXXXX |
| Device ID | Short Zigbee address from pairing | 0x1234 |
Aqara/Xiaomi Zigbee devices do not fully comply with the Zigbee standard and may experience connectivity issues with certain Zigbee routers. Known incompatible routers include Centralite, General Electric, OSRAM, Sylvania, SmartThings and Securifi. Use routers confirmed compatible with Xiaomi devices (e.g., IKEA TRADFRI).
Device capabilities
Temperature and humidity
The Temperature and Humidity device reads the Temperature and Humidity fields from the ZbReceived JSON payload. Temperature is reported in °C as a direct value. Humidity is reported as a raw integer (e.g., 4520 for 45.20%) and divided by 100 in the listener script to produce the ratio that TapHome displays as a percentage.
Both values update whenever the sensor transmits a SENSOR message — typically every few minutes or on significant change.
Atmospheric pressure
The Pressure device reads the Pressure field from the ZbReceived JSON payload. The value is reported in hPa (hectopascals) and mapped via ValueLogTypeConversion from raw type 62 to pressure type 25 with a 1:1 linear scale.
Atmospheric pressure can be used for weather trend monitoring or altitude-based automation rules.
Battery and device health
The module exposes several service attributes populated by the ZbInfo polling mechanism (1-hour interval via the ReadScript):
- Battery Percentage — estimated CR2032 battery level. A warning is raised when the level drops below 30%.
- Battery Voltage — current battery voltage in volts.
- Link Quality — Zigbee signal strength scaled from 0–254 to 0–100%.
- IEEEAddr, ModelId, Manufacturer, Endpoints, Config — device identification and Zigbee configuration metadata.
The template also tracks LastSeenEpoch from ZbInfo responses. If the sensor has not been seen for more than 12 hours, a warning is raised. After 24 hours, an error is raised — indicating the sensor may be offline, out of range, or its battery is depleted.
CR2032 battery updates from Zigbee devices can take up to 24 hours to refresh. A sudden drop does not necessarily mean the battery is failing — wait for the next reporting cycle.
Additional capabilities
The WSDCGQ11LM also supports per-sensor calibration offsets for temperature, humidity and pressure readings (available in zigbee2mqtt). The battery voltage is additionally exposed as a device-level entity in some Zigbee stacks. These capabilities can be added in a future template update.
Troubleshooting
Sensor not reporting data
- Verify the Zigbee2Tasmota gateway is connected to the MQTT broker and receiving messages (check
tele/{GWname}/SENSORin an MQTT client) - Confirm the Device ID in the template matches the short address assigned during pairing (e.g.,
0x1234) - Check the Link Quality service attribute — values below 20% indicate a weak Zigbee signal. Move the sensor closer to the gateway or add a compatible Zigbee router device
- Press the sensor button once to force a transmission and verify the gateway receives the message
Humidity reading appears incorrect
The template divides the raw Humidity value by 100 (e.g., 4520 becomes 0.4520, displayed as 45.20%). If the reading appears too low (e.g., 0.45% instead of 45%), verify the Zigbee2Tasmota firmware version — some firmware versions report humidity already in percentage format, making the division unnecessary.
Device shows offline warning
- Check the battery level — a depleted CR2032 will cause the sensor to stop transmitting
- The Aqara sensor is a Zigbee end device (not a router) and communicates through nearby Zigbee router devices. If a router goes offline, the sensor may become unreachable
- Try pressing the sensor button to wake it and force a re-association with the Zigbee network
- If the issue persists, re-pair the device by holding the reset button for 5 seconds until the blue LED blinks