Deconz-rest-plugin: Aqara Single Switch Module T1 (with Neutral)

[spunti]

Device

• Product name: Single Switch Module T1 (with Neutral)
• Manufacturer: LUMI
• Model identifier: lumi.switch.n0agl1
• Device type : Switch

https://www.aqara.cn/en/single_switch_T1_with-neutral.html

Screenshots

aqara-t1-single-switch-connecting-and-triggering.pcapng.zip

zigbee_pc_keys.txt

[Smanar]

Ha nice ^^
I have started a discussion yesterday with another user about this device, there is a problem ATM for this device, the cluster 0x0006 is invisible (but present).

Do you have a zigbee sniffer ?

[Smanar]

Ok so have a take a look on the sniff with original gateway

• bad luck it don't ask for basic descriptor to compare (it s the device that ask for node descriptor)
• it is using a new attribute 0x00f7 an octet string, but nothing readable.

[SwoopX]

That's attribute 0x00f7

64 10 00        Boolean                     false
03 28 17        Signed 8-bit integer        23
98 39 00000000  Single precision            0
95 39 00000000  Single precision            0
96 39 90391145  Single precision            2323.59766
97 39 00000000  Single precision            0
05 21 0100      Unsigned 16-bit integer     1
9a 20 00        Unsigned 8-bit integer      0
0b 20 00        Unsigned 8-bit integer      0
08 21 1402      Unsigned 16-bit integer     532
09 21 0001      Unsigned 16-bit integer     256

https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Xiaomi-manufacturer-specific-clusters,-attributes-and-attribute-reporting#xiaomi-single-switch-module-t1-with-neutral-lumiswitchn0agl1

[Smanar]

Ha yes lol, the magic attribute ^^.

[Smanar]

Ok so bad luck, the device realy forget the cluster 0x0006

And it was totaly mute after the inclusion, I realy don't see a way to detect the cluster 0x0006.
It was more active on normal gateway than on deconz.

I think need to use hack based on device type "on/off light" and manufacture number 0x115f ?

[spunti]

Any news? Or can I be helpful with something else?

[Mimiix]

@spunti I've read about this in Discord. The devs had a internal discussion on this. Manup responded with the following:

[Smanar]

Yep, for the moment we are waiting to know if manup want to make something clean in the core, or if I make an ugly hack in the api core ^^

[spunti]

Any progress from manup with fixing this device? Would be nice to be finally able to control the device via HA :)

[Smanar]

No yet sorry, but still in the "todo list"

[manup]

Is there a sniffer log when the device sends on/off reports for endpoints other than the first (0x01)?

Ah if I read the description correctly the device should have only one on/off cluster for endpoint 0x01?

[manup]

08 21 1402 Unsigned 16-bit integer 532

By looking at the special attribute 0x08 uint16, I think this represents a model identifier. This might be the reason why the Xiaomi gateway doesn't query the Basic cluster.

[Smanar]

But the problem is to make the cluster 0x0006 "magically" appear in deconz, for the device can be usable in the API without hack.
Its something possible on deconz side with respecting the "zigbee rules" ?