Aqara T2 bulb Zigbee2MQTT & Home Assistant integration - A How To

After getting my T2 bulbs and trying to get them working in Home Assistant I was a little disappointed to find they weren’t supported by Zigbee2MQTT yet, however it is possible to get them working fully with a little modification.

  1. If you haven’t yet installed the Zigbee firmware on the bulb, pair them via Bluetooth to the Aqara app on your phone, and install the firmware.
  2. In your ZigbeeMQTT installation, create the directory zigbee2mqtt/data/external_converters if it doesn’t exist already.
  3. In that folder, create the file aqara_t2_cct.js containing the linked code: prototype z2m aqara t2 converter · GitHub
  4. Restart ZigbeeMQTT
  5. Put ZigbeeMQTT into Permit Join mode.
  6. Turn the bulb on/off 5 times to put it into pairing mode, the light will slowly pulse.
  7. It should then be discovered by ZigbeeMQTT and appear in the dashboard.
  8. The bulb should now appear as a device in Home Assistant.

More discussions on the bulb’s compatibility with ZigbeeMQTT can be found on its Github:

Hopefully out of the box support will be added to ZigbeeMQTT in the future.

14 Likes

Adding a screenshot showing the device recognised in Home Assistant via Zigbee2MQTT.

3 Likes

@absentcinema Thanks you :+1:t2:
This will be useful for many.

2 Likes

Thank you for this post. I have to try that right away.

3 Likes

thanks for this and the link to the thread - looks like support will be officially out next month?

1 Like

Yes, out of the box support should be in the next release which will come out at the start of next month. It’s already in the dev branch if you want to use that.

2 Likes

I have a new Zigbee2MQTT converter for the RGB T2 for testing. It implements the RGB dynamic effects (with a few caveats).

Dynamic RGB Effects have the following properties:

  1. Effect Type: Breathing, Candlelight, Fading, Flash.
  2. Brightness: 1% - 100%
  3. Speed: 1% - 100%
  4. Colours: Between 1 and 8 colours can be set for each effect, the bulb cycles through the colours in order. The colour slots are defined by a comma seperated list of RGB hex values, e.g. #ff0000,#00ff00,#0000ff for a red, green, blue cycle.
2 Likes

Hi. Is this converter still needed now? Wouldn’t it be better to implement it directly in Zigbee2MQTT?
TIA.

I’ll get it merged into Z2M once I have the T1M and T1 Strip converters with effects and segment control ready, they share some routines and I need to make sure those work across all three properly.

Basic functions of the bulb already work in Z2M.

1 Like

Transition curves, transition initial brightness, dimming range, and on/off dimming timings will be in 2.6.4 1st December release. RGB dynamic effects should be in the release after that.

1 Like

I have seen your Pull Request. Thank you!

My T2 RGB bulb just arrived today, and I’ve tried this external converter.
However, when I adjust the “RGB effect” and “RGB effect speed,” the bulb doesn’t produce any light. I need to send the “RGB effect colors” again for it to work.
This behavior is different when adjusting the “RGB effect brightness,” where the effect still works.

There’ll be a Home Assistant blueprint to activate the effects soon. The converter isn’t finished yet, hence it isn’t merged into Z2M. The T2 needs a specific order for the effects: effect type, colours, speed.

1 Like

Added a Home Assistant script blueprint for creating and activating custom RGB dynamic effects for the T2 bulb, along with a set of examples based on the presets in the Aqara app, and an example dashboard card for activating effects. It’s capable of targeting multiple bulbs with a single effect pattern.

1 Like

The full features of the T2 bulb converter will be included on the January 2.7.2 release of Zigbee2MQTT.

Coming in 2026 I’ll be releasing a Home Assistant HACS integration to get the most out of the Aqara T2 bulb, T1M Ceiling Light and T1 LED Strip.

2 Likes

Wish I would have seen this before trying mine in thread and ultimately tossing them.

Personally, I’m not a big fan of the limited nature of Thread/Matter features and products. Whilst it might be good for simple integrations between “big tech” eco systems it still has a long way to go, demonstrated by the reduced feature sets of a lot of products when used in that mode.

I think they fixed it. All I had to do was to change the connection of the bulb via Aqara App.