I needed to buy som new humidity sensors and bought two Aqara temperature and humidity sensors as I have these since before and they work well. I noticed that there where two versions sold of which one was slightly more expensive. Without doing any analysis I assumed the slightly more expensive one was the latest verision and bought two of those. This seems to have been a mistake and slightly confusing one at that.
The sensors I have since before are called 'Aqara temperature and humidity sensor' with model no WSDCGQ11LM. There is a driver for these that works swell.
The two new sensors I bought are called 'Aqara temperature and humidity sensor T1'. The Aqara model no for this sensor is TH-S02D according to the Aqara website. When connected to Hubitat they how ever show up with the model no RTCGQ01LM. This sensor, the T1 version, does not work with the WSDCGQ11LM driver. Searching here on the Hubitat forum, RTCGQ01LM shows up as both a motion sensor and a humidity sensor. This seems odd as they probably won't have the same sets of parameters? At any rate, nor the driver for the humidity version or the motion version works with the T1.
Anyone else come across this issue? Is there a driver that works for the T1 version?
Yes! That is the one. It appears like this when connected.
As far as I can see there is one generic driver for temperature and another one for humidity, but I gave it a try but none of them seemd to work. I did a reset on the device and the hub found them again, but no change unfortunately.
It looks like they appear as 'unknown' in the network map. (Because they don't have driver?)
No, it is not required to have a specific driver for a Zigbee device to be visible with its name/label on the map. It seems to me that the pairing process does not complete successfully.
With the HE inbuilt Device driver, do you see anything in the live logs when you press the sensor button shortly? If not, try removing and re-inserting the battery again, Anything in the logs?
No, celebrated to soon, didn't work But thank you anyway. I think I will just replcae these. The connected fine and was recogniced imediately, but then goes scilent. Thank you anyway for your help!
I can confirm the problem - because of some reason, the sensor does not send periodic check-in messages and does not update the T/H frequently enough, so the healthStatus goes offline :
