Aqara E1 Water Leak Sensor SJCGQ13LM

[cwm77]

Device

• Product name: E1 Water Leak Sensor
• Manufacturer: LUMI
• Model identifier: lumi.flood.acn001
• Device type :
  • Sensor

Screenshots

Basic

Identify

Alarms

N/A

Device Temperature

N/A

Groups

N/A

Scenes

N/A

On/Off

N/A

Level Control

N/A

Color Control

N/A

Simple Metering

N/A

Diagnostics

N/A

Other clusters that are not mentioned above

Power Configuration

IAS Zone

Lumi specific

Identify

OTAU

[Mimiix]

Manufacturer name and model Id in the template are wrong. Please adjust it so it matches the basic cluster.

[cwm77]

Manufacturer name and model Id in the template are wrong. Please adjust it so it matches the basic cluster.

Done

[SwoopX]

All screenshots are only showing the default values, so I'm afraid this is not helpful. Please exchange the screenshots with some where all the attributes have been read.

[cwm77]

All screenshots are only showing the default values, so I'm afraid this is not helpful. Please exchange the screenshots with some where all the attributes have been read.

Ok, I updated the screenshots. The clue was to push the button of the sensor while reading. Not every screenshot got changed, but I checked everyone. Please let me know if something is still missing.

[cwm77]

I wanted to ask if it is already possible to foresee if the integration of this sensor into the software will take a lot of effort and time? According to zigbee.blakadder.com, the two previous models are already supported by Deconz.

https://zigbee.blakadder.com/Aqara_SJCGQ11LM.html
https://zigbee.blakadder.com/Aqara_SJCGQ12LM.html

For this sensor, here is the link, by the way:

https://zigbee.blakadder.com/Aqara_SJCGQ13LM.html

Supposedly it is 100% Zigbee 3.0 compatible.

[SwoopX]

... 100% Zigbee 3.0 compatible

That's the best joke I read since a long time (I'm afraid)

No, the links unfortunately do no help.

[Mimiix]

@SwoopX what's missing?

[SwoopX]

@Mimiix Read attributes

[cwm77]

@Mimiix Read attributes

I would also be interested to know exactly which attributes are the problem now? I am not a dev, but if I can help in any way, for example testing, please let me know. Hope the laugh I generated didn't knock you off your chair ;-).

[Mimiix]

@SwoopX Which ones?

[cwm77]

@SwoopX Which ones?

I compared the device request from the predecessor model SJCGQ12LM #4440 with mine. Maybe he means the missing battery settings. I just tried to read them again, but nothing changes. I was hoping that this model would be as easy to integrate as SJCGQ12LM. What exactly is wrong with it now?

According to Xiaomi, the SJCGQ12LM (T1 series) was only designed and sold for/in the Chinese market. The successor SJCGQ13LM (E1 series) should also be sold in the rest of the world. So I can well imagine that I will not be the only person who wants to integrate this sensor!?

I specially got this model, because SJCGQ11LM only gives problems, SJCGQ12LM is not available in Europe and I hope that SJCGQ13LM will work best because of Zigbee 3.0, but as I now know, something seems to be wrong with this assumption of mine. #5725 (comment) But what exactly I still do not know.

[Smanar]

What exactly is wrong with it now?

IDK, waiting for SwoopX answer.
But not possible using code for next devices, can use only DDF, so this device will be not included in deconz like the previous one. The previous one have not the lumi cluster so we can be sure it s don't use it ^^.
And honnestly I have never used the lumi cluster in DDF, so not sure if this device can be added as it ?

[cwm77]

What exactly is wrong with it now?

IDK, waiting for SwoopX answer. But not possible using code for next devices, can use only DDF, so this device will be not included in deconz like the previous one. The previous one have not the lumi cluster so we can be sure it s don't use it ^^. And honnestly I have never used the lumi cluster in DDF, so not sure if this device can be added as it ?

Has this something to do with this #5733 ?

[Mimiix]

Yes.

[SwoopX]

As already mentioned twice, the attributes from all but 2 clusters have NOT been read.

[cwm77]

As already mentioned twice, the attributes from all but 2 clusters have NOT been read.

After Update deCONZ to v2.14.1 read attributes again. Something changed.

[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.

[4val0v]

Is there currently support for this sensor ?

[SwoopX]

No, it isn't. However, the subsequently added screenshots appear to be complete now and drafting should be doable. Anybody able to test an initial DDF once ready?