What is the actual model on the device is it a TZE200 TS0601? That doesn’t look right as on Blakadder site that is a switch and not a Temp/Humidity sensor.
Also, I’m assuming that you confirmed you were ordering the Zigbee version and didn’t have the WiFi or Bluetooth version selected when you ordered?
@nickrout so well, yes whkgqxse would be the manufacturer code. And I can’t find that it’s listed in either of the databases. I’ll go take a look at the code base for Zigbee2MQTT as I just recently supplied a patched to correctly tag a device that was under the wrong device model. It’s possible that whkgqxse was grouped with the switches and so it’s not recognized correctly.
OK, so I took a look at the Zigbee2MQTT code and it does in fact have the device coded, and supported properly.
Looking at the ZHA device handlers it doesn’t appear that your device is supported.
This means that with ZHA you will most likely need to develop a quirk to get it working. Personally, this is sort of why I decided to use Z2M instead of ZHA as there seems to be support for more devices with Z2M, however that is not mutually exclusive as sometimes there are devices that get support in ZHA before Z2M. Anyways, I’m not suggesting you move to Z2M but if a quirk can get created for your device I think you’ll be in business.
Another possibility is ZHA supports modifying the device type. I’m not sure if that might help you out.
@nickrout Google can rarely find results in most GitHub code. I’m pretty sure that GitHub significantly restricts how much Google can actually index. Even GitHub itself doesn’t have all code indexed as they have file size(lines) limits on how much they index. I knew where this code was because I just submitted a PR that is now in the latest release for some Tuya ZigBee devices changes.