Built-in Aqara Zigbee Weather Sensor Driver Not Getting Temperature since 2.4.1.151

Since I first saw this when I updated to 2.4.1.151 on a production hub, I have added the same device model to my beta hub and have the same issue so it can be debugged.

Aqara Temperature and Humiidity Sensor, model WSDCGQ11LM
image

image

dev:142025-04-03 09:44:51.903 AMinfoAqara Test Sensor pressure is 98.3kPa
dev:142025-04-03 09:44:51.889 AMdebugdescMap: [raw:01B40104031C000029D703140028FF1000296D26, dni:01B4, endpoint:01, cluster:0403, size:1C, attrId:0000, encoding:29, command:0A, value:03D7, clusterInt:1027, attrInt:0, additionalAttrs:[[value:FF, encoding:28, attrId:0014, consumedBytes:4, attrInt:20], [value:266D, encoding:29, attrId:0010, consumedBytes:5, attrInt:16]]]
dev:142025-04-03 09:44:51.886 AMdebugdescription: read attr - raw: 01B40104031C000029D703140028FF1000296D26, dni: 01B4, endpoint: 01, cluster: 0403, size: 1C, attrId: 0000, encoding: 29, command: 0A, value: D703140028FF1000296D26
dev:142025-04-03 09:44:51.886 AMinfoAqara Test Sensor is 55%RH
dev:142025-04-03 09:44:51.883 AMdebugdescMap: [raw:01B40104050A000021DC15, dni:01B4, endpoint:01, cluster:0405, size:0A, attrId:0000, encoding:21, command:0A, value:15DC, clusterInt:1029, attrInt:0]
dev:142025-04-03 09:44:51.880 AMdebugdescription: read attr - raw: 01B40104050A000021DC15, dni: 01B4, endpoint: 01, cluster: 0405, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: DC15
dev:142025-04-03 09:44:51.876 AMdebugdescMap: [raw:01B40104020A000029B908, dni:01B4, endpoint:01, cluster:0402, size:0A, attrId:0000, encoding:29, command:0A, value:08B9, clusterInt:1026, attrInt:0]
dev:142025-04-03 09:44:51.874 AMdebugdescription: read attr - raw: 01B40104020A000029B908, dni: 01B4, endpoint: 01, cluster: 0402, size: 0A, attrId: 0000, encoding: 29, command: 0A, value: B908
dev:142025-04-03 09:44:48.715 AMinfoAqara Test Sensor pressure is 98.3kPa
dev:142025-04-03 09:44:48.609 AMdebugdescMap: [raw:01B40104031C000029D703140028FF1000296D26, dni:01B4, endpoint:01, cluster:0403, size:1C, attrId:0000, encoding:29, command:0A, value:03D7, clusterInt:1027, attrInt:0, additionalAttrs:[[value:FF, encoding:28, attrId:0014, consumedBytes:4, attrInt:20], [value:266D, encoding:29, attrId:0010, consumedBytes:5, attrInt:16]]]
dev:142025-04-03 09:44:48.607 AMdebugdescription: read attr - raw: 01B40104031C000029D703140028FF1000296D26, dni: 01B4, endpoint: 01, cluster: 0403, size: 1C, attrId: 0000, encoding: 29, command: 0A, value: D703140028FF1000296D26
dev:142025-04-03 09:44:48.595 AMdebugdescMap: [raw:01B40104050A0000210116, dni:01B4, endpoint:01, cluster:0405, size:0A, attrId:0000, encoding:21, command:0A, value:1601, clusterInt:1029, attrInt:0]
dev:142025-04-03 09:44:48.594 AMdebugdescription: read attr - raw: 01B40104050A0000210116, dni: 01B4, endpoint: 01, cluster: 0405, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: 0116
dev:142025-04-03 09:44:48.589 AMdebugdescMap: [raw:01B40104020A000029B508, dni:01B4, endpoint:01, cluster:0402, size:0A, attrId:0000, encoding:29, command:0A, value:08B5, clusterInt:1026, attrInt:0]
dev:142025-04-03 09:44:48.587 AMdebugdescription: read attr - raw: 01B40104020A000029B508, dni: 01B4, endpoint: 01, cluster: 0402, size: 0A, attrId: 0000, encoding: 29, command: 0A, value: B508
dev:142025-04-03 09:44:45.350 AMinfoAqara Test Sensor pressure is 98.3kPa

Beta Hub is a C7 and it did not work with C8 Pro with same version of OS.

I updated Beta hub to 2.4.1.152 and still have the problem.

Let me know if you need anything else.

Tagging @mike.maxwell

What was the last platform version when this device worked for temperature?

1 Like

Currently working on 2.4.0.151 in my production environment

1 Like

I concur! Update on C7 from 2.4.0.151 to 2.4.1.151 has broken temperature on these sensors.

Both mine were the same, I just reinstalled them and they're fine now

Have you used the inbuilt driver again? Or is it possible youve re-paired and picked up a community driver you used before?

I've re-paired two of mine, and the same issue persists - it has not been fixed.

what was the last platform version these reported correctly on?

As said before - 2.4.0.151 for me. I am not on the Beta, so that was the last available version before the jump to 2.4.1.151 when it stopped working.

1 Like

Yup, found the bug, will be fixed in the next platform version

3 Likes

Just looked and they both dropped off around 3-4 hours later

Just updating as I type

Confirmed fixed. Thanks @mike.maxwell :partying_face:

2 Likes