Aqara Spotlight T2 (SSWQD03LM): Local Control via Zigbee2MQTT
If you’ve been following Chinese smart home renovation guides — the kind on Zhihu that plan out 全屋智能 (whole-house smart home) setups — you’ve almost certainly seen the Aqara Spotlight T2 listed as the go-to recessed ceiling light. It’s a solid fixture: Ra>90 CRI, a 2700K–6000K color temperature range, beam angles from 15° to 36°, and Zigbee 3.0. The installers love it, and the renovation threads on V2EX recommend it constantly. If you ended up with a ceiling full of them tied to an M2 gateway and the Aqara app, you’ve probably also discovered at least one of the friction points that eventually push people toward Zigbee2MQTT.
This guide covers how to get the SSWQD03LM paired to Zigbee2MQTT and Home Assistant, what’s actually exposed in HA, and how to build local color temperature automations — all without the Aqara hub in the loop. For the broader picture of running Aqara hardware this way, see our guide to Aqara Zigbee devices in Home Assistant without the Aqara hub.
What the Aqara Spotlight T2 (SSWQD03LM) is
The SSWQD03LM is a recessed ceiling downlight, not an E27 bulb. It’s designed for new builds and renovations where the fitting is cut into the ceiling, which is why it’s so common in the Zhihu renovation guides aimed at people building out a fresh apartment. Available beam angles are 15°, 24°, and 36°, covering everything from accent lighting to general room illumination.
On the technical side: Zigbee 3.0, Ra>90 CRI, color temperature adjustable from approximately 2700K (warm white) to 6000K (cool daylight). The Zigbee model identifier is lumi.light.acn026 — that’s what Z2M will identify it as once it’s paired.
T2 vs. T2 Pro — what’s different
Aqara has announced the Spotlight T2 Pro (SSWQD22LM, model ID lumi.light.acn040) with a bumped CRI of Ra96, built-in electricity metering, and additional cutout size options (55mm and 75mm versions). As of June 2026, the T2 Pro is in Z2M’s development changelog but not in a stable release. If you’re buying new, it’s worth checking whether stable Z2M support has landed by the time you read this. For now, the guide below applies to the SSWQD03LM, which has had stable Z2M support for a while.
Before you pair: the Bluetooth firmware step
This is the part that trips people up.
The T2 series spotlights ship with firmware designed to first pair via the Aqara app over Bluetooth, not via Zigbee. In practice that means: out of the box, putting the spotlight into pairing mode and waiting for Z2M to find it will not work. The device needs to go through a one-time Bluetooth provisioning step in the Aqara app to receive its Zigbee firmware before any Zigbee coordinator can see it.
I ran into this the first time I tried to add a T2 spotlight to my Z2M setup directly, cycling power five times and watching the Z2M permit-join screen sit empty. The Aqara forum thread documenting this for the T2 bulb series (lumi.light.agl003) describes a nearly identical setup sequence, and the T2 spotlight behaves the same way.
Why the Aqara app is required once (and only once)
After this initial Bluetooth and firmware step, you can remove the device from the Aqara app entirely. The spotlight retains its Zigbee capability. From this point on, it operates exactly like any other Zigbee 3.0 device — no Aqara account, no Aqara cloud, no hub required.
The Aqara app is a one-time bootstrap, not an ongoing dependency.
Step-by-step: the initial Aqara app setup
- Install the Aqara Home app (iOS or Android) and create an account if you don’t already have one. You won’t need this account again after this step.
- Power on the spotlight. It should start searching for Bluetooth devices automatically.
- In the Aqara app, add a new device. The app will detect the spotlight over Bluetooth.
- Follow the in-app steps. This triggers a firmware download and install onto the device over Bluetooth; the process takes 1–3 minutes. If the app asks you to choose a protocol, select Zigbee.
- Once firmware installation completes and the device shows as “added” in the app, delete it from the Aqara account.
- The spotlight is now ready for Zigbee pairing.
Note: Aqara documents this firmware flow for the T2 bulb (lumi.light.agl003) rather than the spotlight specifically, so the exact in-app wording may differ slightly on the SSWQD03LM. The shape of the process — Bluetooth provisioning, firmware install, then Zigbee — is the same across the T2 series.
Pairing to Zigbee2MQTT
Once the firmware step is done, pairing to Z2M is standard.
Power-cycle pairing procedure
The T2 spotlight enters pairing mode via power cycling:
- With the spotlight powered off at the wall switch or circuit breaker, restore power.
- Power cycle the light five times in quick succession (on, off, on, off… ending on). The light will flash briefly to indicate it’s entered pairing mode.
- In Z2M, open the web interface and enable “Permit join” — either globally or for a specific device as the joining router if you want to control mesh routing.
- The spotlight should appear in Z2M within 60 seconds.
If it doesn’t appear after two attempts, check that the firmware step above fully completed. A partially-flashed device sometimes ends up in a state where it doesn’t respond to either Bluetooth or Zigbee pairing mode correctly; power cycling it 10 times (instead of 5) has cleared this for some users in the Aqara forum threads.
What Z2M identifies it as
Once paired, Z2M will show the device as:
- Model: SSWQD03LM
- Vendor: Aqara
- Description: Spotlight T2
- Model ID: lumi.light.acn026
Verifying the device in the Z2M dashboard
After pairing, go to the Z2M web interface and open the device. You should see it listed under “Lights” with the controls for on/off, brightness, and color temperature visible. If you see the device but the controls are grey or the device shows as “unknown,” wait a few seconds — Z2M is still reading the device’s capability cluster. A refresh usually resolves it.
What Home Assistant exposes
Z2M publishes the SSWQD03LM’s state to MQTT, and the HA MQTT integration (via Z2M’s HA auto-discovery) picks it up as a light entity. Here’s what you get.
On/off and brightness
Standard light entity controls. Brightness runs 0–254 in the Z2M payload, mapped to 0–100% in the HA UI. It works reliably; I haven’t seen any state-sync issues with this device.
Color temperature
This is where the T2 spotlight gets interesting for anyone running circadian lighting setups.
Z2M exposes color temperature in mired (153–370 mired), which maps to roughly 6500K–2700K in more recognizable terms. HA’s light entity accepts color_temp in mired directly when you call light.turn_on with the color_temp attribute.
Z2M also surfaces preset labels (coolest, cool, neutral, warmest), accessible via the color_temp_startup attribute. These match the marketing labels Aqara uses in the app, but in HA you’re better off working with mired values directly for automation precision.
The full range from 2700K to 6000K (or 6500K depending on which spec sheet you look at — the Z2M device page lists 153 mired, which rounds to about 6536K) covers everything from warm bedside reading light to bright task lighting. For most living space automations, 2700K–4000K is the practically useful range.
OTA updates via Z2M
Once the device is paired, firmware updates can be pushed via Z2M’s OTA mechanism, with no Aqara app needed. You’ll see an “OTA” tab in the Z2M device page for this device. Whether Aqara’s OTA server has new firmware at any given time varies; check the Z2M OTA docs for how the update poll is triggered.
Building local lighting automations
The main reason to put these spotlights through the Z2M path rather than leaving them on the Aqara hub is automation flexibility. Here’s what works well in practice.
Simple scene: warm at night, cool in the morning
The most useful automation for adjustable color temperature lights is matching color temperature to time of day. A basic version in Home Assistant:
automation:
- alias: "Spotlights — morning cool"
trigger:
- platform: time
at: "07:00:00"
action:
- service: light.turn_on
target:
entity_id: light.spotlight_living_room
data:
color_temp: 233 # ~4300K — neutral-cool
brightness: 200
- alias: "Spotlights — evening warm"
trigger:
- platform: time
at: "20:00:00"
action:
- service: light.turn_on
target:
entity_id: light.spotlight_living_room
data:
color_temp: 333 # ~3000K — warm
brightness: 128
This is the local alternative to Apple Home’s Adaptive Lighting feature: no iCloud dependency, no hub gateway mode quirks, runs entirely on your HA instance.
Circadian lighting with the adaptive_lighting integration
For a smoother circadian implementation, HA’s adaptive_lighting integration (most commonly installed as a HACS custom component) can automatically adjust both brightness and color temperature throughout the day based on your location’s sunrise and sunset. The SSWQD03LM responds to these adjustments without any special configuration — it’s a standard light entity from HA’s perspective. Check the integration’s own docs for the current install method and minimum HA version, since that’s where the up-to-date compatibility notes live.
The Chinese community discussion I came across on V2EX described this as 日夜节律 (circadian rhythm) lighting, and the practical verdict from renovation users is consistent: the color temperature range on the T2 spotlights is wide enough to make a noticeable difference, particularly for the 6000K-to-2700K shift between work hours and winding-down hours.
Light groups for multiple spotlights
If you have several spotlights in a room — the common renovation install, since a single T2 spotlight isn’t enough to light a whole room — HA’s light group feature lets you control them as one entity:
light:
- platform: group
name: "Living Room Spotlights"
entities:
- light.spotlight_t2_1
- light.spotlight_t2_2
- light.spotlight_t2_3
- light.spotlight_t2_4
Once grouped, the color temperature and brightness controls apply to all four simultaneously. Dimming one dims all. This is the setup that makes circadian automations scale to a full installation without writing per-device automation entries.
Why Z2M beats the Aqara hub path for these spotlights
Honestly, this is my main argument for the Z2M path with ceiling-installed mains-powered lights: the failure modes are different, and the Aqara hub path has some specific failure modes that are hard to recover from once you’re up on the ladder.
No gateway mode confusion
The V2EX thread I mentioned earlier (t/1034387) documented a frustrating recurring problem. After a power outage, Aqara spotlights bound to an M2 gateway disappeared from HomeKit. Investigation traced the root cause to the M2’s gateway mode: the Aqara app can inadvertently switch the hub between Mijia mode and Aqara mode after a reset, which breaks HomeKit sync. Some users reported that not all devices returned to HomeKit even after rebinding.
In the Z2M path, there is no gateway mode. The spotlights talk directly to the Z2M coordinator. HomeKit integration is handled by HA’s HomeKit Bridge integration if you use HomeKit at all, and that’s independent of whether the lights lose power. After a power cut, they come back, Z2M sees them, HA state updates. No manual rebinding to an Aqara hub, no gateway mode to check.
Mesh router bonus
Because the SSWQD03LM is mains-powered, Z2M treats it as a Zigbee router that extends the mesh. A ceiling installation with four or five spotlights is essentially a Zigbee router cluster that improves coverage for battery-powered devices (sensors, switches) throughout the room. This is an incidental benefit of the Z2M path that you don’t get from the Aqara hub approach, where devices on the Aqara mesh don’t contribute to your Z2M mesh.
No app required after setup
Once paired via Z2M, the Aqara app is genuinely off the table. Firmware updates go through Z2M. Control goes through HA. There’s no periodic re-authentication, no account required, no cloud sync. For lighting that’s wired into the ceiling and expected to last years, that steady-state simplicity matters. This is the same local-resilience argument we make in does Aqara work without internet.
A note on the T2 Pro for future readers
If you’re doing a new installation and reading this after June 2026, check the Z2M device database for the SSWQD22LM (T2 Pro, model ID lumi.light.acn040) before buying. The Ra96 CRI and electricity metering are genuine upgrades: the higher CRI is noticeable in rooms where color accuracy matters (kitchens, artwork lighting), and per-fixture power monitoring is useful for spotting dimmers or wiring issues early. The guide above will apply to the T2 Pro as well, assuming stable Z2M support has landed by then.
For related lighting setups on the same local path, see our guides to the Aqara LED Bulb T2 and the Aqara Ceiling Light T1M (CL-L02D). If you’d rather keep a hub in the loop for Matter bridging, the Aqara Hub M3 Matter bridge guide covers that path.
Whether the T2 Pro becomes the standard recommendation for new installs once it has stable Z2M support is worth watching — the CRI bump alone is meaningful for rooms where lighting quality actually matters.