Tuya ZTH05 Diver?

🛎️ Get Help Devices
1

I did try searching for other posts before writing this

I recently bought the Tuya Temperature/ Humidity sensors with a screen. I already had one that was working no problem. But apparently these are a different model. I can pair them, but then nothing happens. No data is sent to the HE, and the screen on the device no longer updates the temp/humidity.

I've tried using:
Generic Zigbee temp/humidity driver
Konoke Temp/humidity sensor
Kkossevs drivers

None of them seem to work. When i pair the device, it defaults to Kkossevs "Tuya Temperature Humidity Illuminance LCD with Clock"

Has anyone had any luck with this model? I apologize for poor formatting of the following data, I'm on mobile...

Current States

  • _info : installed

State Variables

  • lastTx : {"cfgFailure":false,"cfgTimer":0,"humiCfg":"-1,-1,-1","humiCfgOK":false,"tempCfg":"-1,-1,-1","tempCfgOK":false}
  • modelGroup : UNKNOWN
  • lastRx : {"humiCfg":"-1,-1,-1","humiTime":1715516747649,"tempCfg":"-1,-1,-1","tempTime":1715516747649}
  • stats : {"date":"2024-05-12","rejoins":0,"rxCtr":6,"txCtr":2}
  • driverVersion : 1.3.9 2023/09/29 10:54 PM
  • notPresentCounter : 0
  • configState : 0

Data

  • endpointId: 01
  • application: 49
  • manufacturer: _TZE204_upagmta9
  • model: TS0601
1 Like
2

I will notify you when this new manufacturer is added into the driver.

3

You can update the driver to the latest version dev.branch version 1.5.2. Click on the Initialize button. Please let me know if it works.

4

Thank you for trying to help with this!

When pairing the device, it does change the unit to F, which is a start. Unfortunately it still does not pull the temp/humidity. And, I think the issue persists where once paired, the device screen does not update anymore. I'll check when I get home from work to see if it started updating.

Current States

  • _info : installed
  • healthStatus : online
  • rtt : timeout

State Variables

  • lastTx : {"tempCfg":"-1,-1,-1","humiCfg":"-1,-1,-1","tempCfgOK":false,"humiCfgOK":false,"cfgFailure":false,"cfgTimer":0}
  • modelGroup : TS0601_Tuya_2
  • lastRx : {"tempTime":1715686572349,"humiTime":1715686572349,"tempCfg":"-1,-1,-1","humiCfg":"-1,-1,-1"}
  • stats : {"date":"2024-05-14","rxCtr":0,"txCtr":0,"rejoins":0}
  • driverVersion : 1.5.2 2024/05/14 8:00 AM
  • notPresentCounter : 0
  • configState : 0
5

The stats section shows that nothing is received from the device…

Enable the debug logging and click on ‘Save Preferences. Then remove the batteries for 10 seconds and reinsert them back.

Anything in the live logs?

Also, click on F5 to refresh the web page before posting a screenshot. The State Variables is typically for internal driver usage and does not refresh automatically.

6

I have a feeling that, even though it is saying the device is online, it isn't staying connected. If I do add device, it finds the device again. I will try what you ask when I get home.

1 Like
7

There are entries in the live logs for the sensor,

Kitchen Thermometer NOT PARSED : [raw:45C001000026DFFF420F111ED62D19111ED62D070000000011, dni:45C0, endpoint:01, cluster:0000, size:26, attrId:FFDF, encoding:42, command:0A, value:Ö-Ö-a, clusterInt:0, attrInt:65503]

8

If this Zigbee message was received recently, it means that the device communicates to the hub.
Let's see the events when you can reinsert the batteries.

9

After removing battery and putting back in these are the live logs that immediately post

dev:12652024-05-14 10:42:16.103 AMdebugKitchen Thermometer parse() descMap = [raw:catchall: 0104 EF00 01 01 0040 00 45C0 01 00 0000 11 01 000340, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:45C0, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:11, direction:01, data:[00, 03, 40]]

dev:12652024-05-14 10:42:15.153 AMdebugKitchen Thermometer Tuya check-in message (attribute 0001 reported: 49)

dev:12652024-05-14 10:42:15.151 AMdebugKitchen Thermometer parse() descMap = [raw:45C00100001801002049E2FF2038E4FF2001, dni:45C0, endpoint:01, cluster:0000, size:18, attrId:0001, encoding:20, command:0A, value:49, clusterInt:0, attrInt:1, additionalAttrs:[[value:38, encoding:20, attrId:FFE2, consumedBytes:4, attrInt:65506], [value:01, encoding:20, attrId:FFE4, consumedBytes:4, attrInt:65508]]]

dev:12652024-05-14 10:42:10.019 AMinfoKitchen Thermometer device announcement

dev:12652024-05-14 10:42:10.017 AMdebugKitchen Thermometer parse() descMap = [raw:catchall: 0000 0013 00 00 0040 00 45C0 00 00 0000 00 00 00C0458842C435DB38C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:45C0, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, C0, 45, 88, 42, C4, 35, DB, 38, C1, A4, 80]]

Current States

  • _info : installed
  • healthStatus : online
  • rtt : timeout

State Variables

  • lastTx : {"cfgFailure":false,"cfgTimer":0,"humiCfg":"-1,-1,-1","humiCfgOK":false,"pingTime":1715697834458,"tempCfg":"-1,-1,-1","tempCfgOK":false}
  • modelGroup : TS0601_Tuya_2
  • lastRx : {"tempTime":1715697809833,"humiTime":1715697809833,"tempCfg":"-1,-1,-1","humiCfg":"-1,-1,-1"}
  • stats : {"date":"2024-05-14","rejoins":2,"rxCtr":8,"txCtr":4}
  • driverVersion : 1.5.2 2024/05/14 8:00 AM
  • notPresentCounter : 0
  • configState : 0
10

All seems OK here..

Do you see any new debug logs when you rapidly change the temperature or the humidity?

11

I did not. The screen has also defaulted back to Celsius and no longer updates temp/humidity.

12

Can you post a link to the seller’s site ?

What you can try as a last resort for the moment is to completely delete the device (use the red REMOVE DEVICE button on the device webpage), and then pair it again to your hub.

When paired, there will be a ‘Device info’ hyperlink click on it and make a screenshot, before entering a device label.

This driver should be automatically selected now.

Pair it very close to the hub.

14

1000000129
10000001291080×2400 207 KB

1000000128
10000001281080×2400 107 KB

1 Like
15

Well, if it doesn't work again - I suggest we give up for now..

There are 117 comments in this Zigbee2MQTT thread in GitHub, this device has much more 'specifics' than the usual Tuya devices have... :frowning:

1 Like
16

I really appreciate everything you tried . Next time I'll order products from my PC instead of cell phone. I thought I was ordering the same one I already had...

17

Reading these comments, it is probably not worth to dig any further :

image
image1009×521 32.9 KB

I also avoid placing POs from my mobile, there are a lot of details that you can miss on the small cell phone screen... However, in this case, the bigger screen would not help - sometimes, the Tuya device sellers receive rather different electronics/different firmware inside the same device that they've been selling in the past without even knowing that something has changed.

1 Like
18

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.