AQARA Temperature and Humidity Sensor T1

deCONZ General Support
1

Name: Aqara Temperature and Humidity Sensor T1
Model: TH-S02D
Link: Aqara Temperature and Humidity Sensor T1 WSDCGQ12LM Zigbee compatibility

I’m unable to connect this device to the ConBee III, and I’m not sure if it is currently supported. Probably not??

Please add support for this device. It also uses the Zigbee protocol.

Is anyone else experiencing the same issue?

2

It seem it is supported > deconz-rest-plugin/devices/xiaomi/xiaomi_wsdcgq12lm_t1_temp_hum_sensor.json at master · dresden-elektronik/deconz-rest-plugin · GitHub
Can you compare the model id and the manufacture name ?

  "manufacturername": "LUMI",
  "modelid": "lumi.sensor_ht.agl02"

And what is your deconz version, old version on branch 2.27 have problem with “short” manufacture name

"manufacturername": "$MF_LUMI",

3

I’m using ioBroker and deConz adapter (v 2.26.3)

Manufacturer: Lumi United Technology Co., Ltd.
Model: TH-S02D

I think the model id is different → not WSDCGQ12LM but TH-S02D

4

The DDF referenced by Smanar is indeed the right one for the device. When it was created back in the days, I haven’t had the device here for testing. However, I noted the wrong Xiaomi model ID as well and would have sworn that I changed it, including renaming the file.

Must have been in a parallel universe :smile:

5

I m saying model id and Manufacture name from the device itself, not the packaging.
I have search on another project and it seem value are good (or I don’t see the bad one …)

fingerprint deviceJoinName: "Aqara Temperature, Humidity & Pressure Sensor (WSDCGQ12LM)", model: "lumi.sensor_ht.agl02", modelType: "Aqara WSDCGQ12LM", profileId:"0104", endpointId:"01", inClusters:"0000,0003,0402,0405,0403,0001", outClusters:"0019", manufacturer:"LUMI"

Deconz use only “lumi.sensor_ht.agl02” and “LUMI” to select the DDF, will be usefull to check in deconz direclty.

6

I have 3 of these sensors now, and have noticed that the pressure sensor is having an issue. I am pretty sure I have seen it switch from values in the 10s to values in the 1000s on one of the sensors. Don’t have screenshot handy but was wondering if it is most likely a hardware issue or if it could possible be something in deCONZ? Though I can’t see how.

image
image714×347 21.1 KB

7

Yes you can edit the DDF.
I don’t understand why there is a state/pressure_bis on the sensor, can you check all values using for exemple Phoscon/help/API Information/sensors

Need to see wich one value is bad, state/pression or state/pression_bis

And can edit the DDF, but ATM the value is already / 100, so need to be / 100 000, it make too much for me

        {
          "name": "state/pressure_bis",
          "awake": true,
          "parse": {
            "at": "0x00F7",
            "ep": 1,
            "eval": "R.item('state/pressure').val = Math.round(Attr.val / 100) + R.item('config/offset').val",
            "fn": "xiaomi:special",
            "idx": "0x66",
            "mf": "0x115F"
          }
        }

Can try to remove this part and use only

        {
          "name": "state/pressure"
        },