[New device support]: Aqara LED Bulb T2

[ai]

Link

https://eu.aqara.com/en-eu/products/aqara-led-bulb-t2-e27

Database entry

{"id":40,"type":"Router","ieeeAddr":"0x54ef4410010fcfc5","nwkAddr":34789,"manufId":4447,"manufName":"Aqara","powerSource":"DC Source","modelId":"lumi.light.agl003","epList":[1,21],"endpoints":{"1":{"profId":260,"epId":1,"devId":258,"inClusterList":[5,4,3,0,768,8,6,2820,1794,64704],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"modelId":"lumi.light.agl003","manufacturerName":"Aqara","powerSource":4,"zclVersion":3,"appVersion":27,"stackVersion":27,"hwVersion":1,"dateCode":"20250113"}}},"binds":[],"configuredReportings":[],"meta":{}},"21":{"profId":260,"epId":21,"devId":0,"inClusterList":[12],"outClusterList":[],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":27,"stackVersion":27,"hwVersion":1,"dateCode":"20250113","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1738692849080}

Zigbee2MQTT version

2.1.0

Comments

It supports both Zigbee and Thread. User will need Aqara Home app to switch lamp mode to Zigbee.

External definition

Autogenerated:


const m = require('zigbee-herdsman-converters/lib/modernExtend');

const definition = {
    zigbeeModel: ['lumi.light.agl003'],
    model: 'lumi.light.agl003',
    vendor: 'Aqara',
    description: 'Automatically generated definition',
    extend: [m.deviceEndpoints({"endpoints":{"1":1,"21":21}}), m.light({"colorTemp":{"range":[111,500]},"color":true}), m.electricityMeter()],
    meta: {"multiEndpoint":true},
};

module.exports = definition;

What does/doesn't work with the external definition?

Works: I can turn off/on, change color and brightness

Don't work: can’t change Power-on behavior and Power/Voltage/etc shows zero.

[coldridj]

TL;DR UPDATE

please give the prototype external converter a go and report any issues or missing functionality

• if unsure what to do with this file see how to add an external converter

--

I have some of these bulbs as well - there are several variants depending on which market you are in (I am EU) and whether they support CCT or CCT + RGB

Mine report as lumi.light.agl004 rather than agl003 as yours do.

I had a go at extending the converter using some of the available functions from the lumi library and have the power on behaviour working and device temperature reporting in addition to state, brightness and cct.

Power measurement did not work with either of the existing metering functions from this library, and I am most interested in exposing the power on/off fade timeout. I can see relevant looking nodes in the database so will investigate these more thoroughly.

const { lumiModernExtend } = require('zigbee-herdsman-converters/lib/lumi');

const definition = {
    zigbeeModel: ['lumi.light.agl004'],
    model: 'T2 E27 CCT',
    vendor: 'Aqara',
    description: 'LED Bulb T2 CCT',
    extend: [
        lumiModernExtend.lumiLight({colorTemp: true, powerOutageMemory: false}),
        lumiModernExtend.lumiZigbeeOTA(),
        lumiModernExtend.lumiPowerOnBehavior(),
};

module.exports = definition;

My database entry appears to contain substantially more than yours:

{"id":64,"type":"Router","ieeeAddr":"0x54ef441000efefcf","nwkAddr":18013,"manufId":4447,"manufName":"Aqara","powerSource":"DC Source","modelId":"lumi.light.agl004","epList":[1,21],"endpoints":{"1":{"profId":260,"epId":1,"devId":258,"inClusterList":[5,4,3,0,768,8,6,2820,1794,64704],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"61441":0,"modelId":"lumi.light.agl004","manufacturerName":"Aqara","powerSource":4,"zclVersion":3,"appVersion":27,"stackVersion":27,"hwVersion":1,"dateCode":"20250113"}},"lightingColorCtrl":{"attributes":{"245":4611445,"colorCapabilities":16,"colorTempPhysicalMin":153,"colorTempPhysicalMax":370,"colorTemperature":290,"colorMode":2}},"haElectricalMeasurement":{"attributes":{"acPowerDivisor":10,"acPowerMultiplier":1}},"manuSpecificLumi":{"attributes":{"22":"56DD9AEEF565CEBA1B8788CBD72C5F1EEC93C749B04FD827BF0E6B8FFC3A7E1D","223":{"type":"Buffer","data":[19,33,0,0,20,33,0,0,22,33,0,0,23,33,0,0,12,33,0,0,24,33,115,4]},"229":{"type":"Buffer","data":[23,15,8,149,192,37,89,67,193,37,0,127,204,37,50,193,221,37,84,82,235,37,40,173,240,37,88,201,244,37,102,167,249,37,86]},"230":0,"247":{"type":"Buffer","data":[3,40,33,5,33,2,0,8,33,27,1,9,33,0,23,10,33,0,0,11,32,0,12,32,10,160,32,1,154,32,0,100,32,1,101,32,154,102,33,34,1,106,35,140,10,100,25,105,32,0,113,32,1]},"1301":1,"1302":100,"1303":1,"1320":0.800000011920929,"1324":0,"65522":{"type":"Buffer","data":[170,117,19,132,201,129,7,65,0,15,12,35,1,4,0,23,10,35,8,0,12,100,11,32,4]}}},"genLevelCtrl":{"attributes":{"245":4611453,"onTransitionTime":15,"offTransitionTime":15,"currentLevel":154}},"genOnOff":{"attributes":{"245":4611522,"onOff":1}}},"binds":[],"configuredReportings":[],"meta":{}},"21":{"profId":260,"epId":21,"devId":0,"inClusterList":[12],"outClusterList":[],"clusters":{"genAnalogInput":{"attributes":{"presentValue":0}}},"binds":[{"cluster":12,"type":"endpoint","deviceIeeeAddress":"0x00124b00215fff90","endpointID":1}],"configuredReportings":[{"cluster":12,"attrId":85,"minRepIntval":10,"maxRepIntval":3600,"repChange":5}],"meta":{}}},"appVersion":27,"stackVersion":27,"hwVersion":1,"dateCode":"20250113","zclVersion":3,"interviewCompleted":true,"meta":{"configured":332242049},"lastSeen":1739184043604}

z2m version 2.1.1

[coldridj]

I obtained an Aqara hub to start exercising the available controls and have a mostly working prototype.

I don't believe the power metering functionality is implemented, or if it is it may be exposed through some of the buffers in the manuSpecificLumi cluster rather than on seMetering and haElectricalMeasurement. I havent yet attempted to decode these and have focused on the controls available in the Aqara Home App.

The UI controls need more work:

• It is possible to cross over the min and max dimmer range values, these could also be exposed in a composite control similar to transition time.
• Transition time is currently configured in 1/10ths of a second, converting the unit would provide a better experience as the granulartiy appers to be 0.5s.
• I would like to enhance the CCT control to report the more familiar kelvin instead of the mired value.

I intend to obtain an RGB/CCT bulb and will add additional controls then.

See gist for current revision: aqara_t2_cct.js

[hoppel118]

I really appreciate what you guys are doing here. Is this for both types of T2 bulbs (GU10, E27)?

[coldridj]

I really appreciate what you guys are doing here. Is this for both types of T2 bulbs (GU10, E27)?

I would assume the functions are the same as for E27 which is what I have been testing, they may report a different model id which would need adding to the converter.

[hoppel118]

I have the following bulbs:

• LED Bulb T2 (GU10, RGB CCT) (6149)
• LED Bulb T2 (E27, RGB CCT) (6147)

I'm really new to Zigbee2MQTT and don't really understand what I need to do to make them compatible. Right now they are paired with Home Assistant via Matter over Thread.

But let me check the model IDs next week. I'll report them back here then.

Is there any other information you are interested in that I can easily find out?

[coldridj]

I'm really new to Zigbee2MQTT and don't really understand what I need to do to make them compatible. Right now they are paired with Home Assistant via Matter over Thread.

I dont use HA, matter or thread. In order to pair them with z2m and get the id's you'll need to put them into pairing mode, and start the process of adding an accessory in the Aqara home app on your phone. The first screen you see after discovering the device will allow you to switch protocol to Zigbee - which will go through the firware upload process and then the device will enter Zigbee pairing mode at which time you can enable joining on z2m and it should be discovered.

From there you can go to the device card in z2m and from the dev console tab click generate_external_definition - this will show you the model id. You can also access the databases.db file in your z2m data directory and copy the corresponding entry (likely the last).

If you want to go back to matter protocol, repeat the above process in aqara home after entering pairing mode.

Is there any other information you are interested in that I can easily find out?

Database entry for the GU10 RGB in particular as I dont have or need any of this model.

[SalGnt]

I got the same definition as the OP with the EU (E27, RGB CCT) variant. I can help with tests if needed.

In the attached archive, you can find the E27 images.

T2_E27.zip

[MarcelMrcn]

Great to see people working on this. Thank you to everyone!
The GU10 (RGB CCT) model reports as lumi.light.agl005
The generated external defintion is the same as OP's, apart from the model number.

[coldridj]

I've obtained an E27 RGB CCT and can confirm this is reporting as agl003 - I've updated the gist and added rgb control functionality for the two models we have confirmed.

I will try and obtain a GU10 CCT to get the model id, my assumption is this will be agl006 as the numbers appear to crrespond to their position on the variants table.

[hoppel118]

@coldridj Thanks for the explanation.

Here are the generate_external_definition outputs:

Aqara T2 GU10 (RGB CCT)

const m = require('zigbee-herdsman-converters/lib/modernExtend');

const definition = {
    zigbeeModel: ['lumi.light.agl005'],
    model: 'lumi.light.agl005',
    vendor: 'Aqara',
    description: 'Automatically generated definition',
    extend: [m.deviceEndpoints({"endpoints":{"1":1,"21":21}}), m.light({"colorTemp":{"range":[111,500]},"color":true}), m.electricityMeter()],
    meta: {"multiEndpoint":true},
};

module.exports = definition;

Aqara T2 E27 (RGB CCT)

const m = require('zigbee-herdsman-converters/lib/modernExtend');

const definition = {
    zigbeeModel: ['lumi.light.agl003'],
    model: 'lumi.light.agl003',
    vendor: 'Aqara',
    description: 'Automatically generated definition',
    extend: [m.deviceEndpoints({"endpoints":{"1":1,"21":21}}), m.light({"colorTemp":{"range":[111,500]},"color":true}), m.electricityMeter()],
    meta: {"multiEndpoint":true},
};

module.exports = definition;

So nothing new. All we need now is the model of the GU10 CCT bulb.

[myrwon]

nice to see some traction on this. I'm very new to this. I'm not even sure where to place all this information....
I have the aqara T2 E26 CCT (US)...I'm to toggle on/off, white to yellow, and dim but getting Z2M errors regarding payload, temp and such

const m = require('zigbee-herdsman-converters/lib/modernExtend');

const definition = {
    zigbeeModel: ['lumi.light.agl002'],
    model: 'lumi.light.agl002',
    vendor: 'Aqara',
    description: 'Automatically generated definition T2 Aqara',
    extend: [m.deviceEndpoints({"endpoints":{"1":1,"21":21}}), m.light({"colorTemp":{"range":[153,370]}}), m.electricityMeter()],
    meta: {"multiEndpoint":true},
};

module.exports = definition;

[coldridj]

I think @myrwon confirms the theory that the agl00x corresponds to the row in the variant table - I have speculatively added the four NA region bulbs and the missing EU GU10 CCT to the external converter

• For those following this thread and unsure what to do with this file see how to add an external converter

I have been experimenting with the RGB bulb and noticed that it reports a larger colour temperature range than the CCT (likely mixing in RGB) and have updated this range for those bulbs as well.

I am not in a rush to get a PR open on the converters repository as there are a number of features I want to explore further before doing so, and all of the low level zigbee protocol details are new to me:

• Explore how to expose and send the level and cct/color control commands (these can be executed via the dev console)
  • see zigbee cluster spec 3.10.2.3, 5.2.2.3 etc
• Explore how to save and recall the RGB custom scenes
  • this will likely involve some packet sniffing
    • re. network key
  • note: I suspect these arent stored/exposed in manuSpecificLumi in a way that is currently exposed in the z2m database
• Expose RGB control in 8bit rgb web colour notation - I think this is a lot more user friendly than CIE 1931
  • see: related stack overflow discussion - there must already be code in the converter utilities to do this as the colour picker control has to use web colours
• Above mentioned improvements to z2m device card controls:
  • on/off transition time unit transaltion to native 1/10th second
  • CCT exposed in Kelvin
  • validate/restrict dimmer range crossover point

I believe the converter in its current form covers the majority of the functionality of these bulbs and should hopefully get these useable for the most of situations in the meantime.

Anyone with time/experience/enthusiasm to contribute to the above or improve my hacky JS is welcome to open a dicsussion or start comment thread on the gist.

[Flumeded]

Really appriciate everyone for contrubuting!
added converter to test with T2 (E27, CCT) [EU], power on control is a god send!

[myrwon]

I can confirm that using the converter gist, and placing the JS file in /zigbee2mqtt/external_converters. Z2M is now showing the Aqara T2 supported - truely grateful!!! ty