Aqara Dual Relay Module T2

[moddavid]

Is there already an existing issue for this?

• I have searched the existing issues and there is none for my device

Product name

Aqara Dual Relay Module T2 (DCM-K01)

Manufacturer

Xiaomi Aqara LUMI

Model identifier

lumi.switch.acn047

Device type to add

Switch

Node info

Endpoints and clusters

Basic

Further relevant clusters

Electric Measurement

Simple Metering

Multistate Input (Basic)

On/Off

Lumi Specific

Analog Input (Basic)

Additional information

Phoscon shows it currently as two On/Off lights. I have installed the T2 behind my existing roller shader switch to make it smart. While moving the shader up by activating the corresponding "light" worked, the other "light" for the down movement didn't do anything.
I'm running the docker image deconzcommunity/deconz:2.26.3 on an Intel NUC with Conbee II.

[gee-jay-bee]

FWIW, I'm using 2.25 (via the community HA addon) and controlling a garage door using the T2 in a similar way (toggle each light on/off for a second to start the door moving either up or down depending on which light is chosen). Maybe I will hold off moving to 2.26!

Also, I have another T2 module to control a bathroom light and extractor fan and I am experiencing problems with the second relay output reporting that it is off when it is actually still on (the second relay is running the extractor fan). It correctly reports being on for an hour but then gets in a repeated pattern of reporting turning on / off every 5-15 minutes (but it is definitely still on).

Hoping that officially supporting this module might fix this?

[SwoopX]

Hi there.

Unfortunately, the screenshots indicate that the clusters have not been read properly. This page explains how to read clusters. Please take new ones and update the issue accordingly. Thanks a lot!

[moddavid]

Hi @SwoopX, thank you for the advice. I will prepare new screenshots based on the explanation page but it will take me some time to do so. I will update you when done. Maybe @gee-jay-bee can (optionally) help out to speed up the process ;).

[gee-jay-bee]

Screenshots taken in order shown (hope this is correct …):

[moddavid]

@SwoopX sorry for the delay, here are the new screenshots:

Node Info

Endpoints and clusters

Basic

Electric Measurement

Simple Metering

Multistate Input (Basic)

On/Off

Lumi Specific

Lumi Specific (second device - this is the only one which was different)

Analog Input (Basic)

This time both up and down movement worked just fine, I'm not sure why it didn't work the last time.

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[moddavid]

Anything we can do here?
For me right now two options are missing: Measuring the power consumption (like the Aqara smart plug SP-EUC01 -
lumi.plug.maeu01) and the child lock (like the Aqara Thermostat E1 - lumi.airrtc.agl001).

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[gee-jay-bee]

Fwiw, I was experiencing some challenges with Deconz + Conbee II and finally took a chance on Zigbee2mqtt with a newer USB coordinator. This T2 is natively supported there and good news is the drop-out issue I was seeing isn't happening. There is power reporting (though it seems to be the combined power of both relays) but I don't see child lock. You can disconnect the relays from the inputs.

Deconz served me well for many years and I hope the new DDF strategy can accelerate device on-boarding. Good luck!

[moddavid]

I would rather don't stale this ticket for now. Maybe I find some time to compare the DDF files from the mentioned other devices to see if I get it somehow to work as intended.

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[github-actions]

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

[SwoopX]

I'll share a DDF candidate within the next days