tuya.js :

fingerprint: tuya.fingerprint('TS0601', ['_TZE200_yjjdcqsq', '_TZE200_9yapgbuv', '_TZE204_upagmta9', '_TZE200_cirvgep4']),
model: 'TS0601_temperature_humidity_sensor_2',
vendor: 'TuYa',
description: 'Temperature and humidity sensor',
fromZigbee: [tuya.fz.datapoints],
toZigbee: [tuya.tz.datapoints],
onEvent: tuya.onEvent({queryOnDeviceAnnounce: true}),
configure: tuya.configureMagicPacket,
exposes: [e.temperature(), e.humidity(), tuya.exposes.batteryState(), tuya.exposes.temperatureUnit()],
meta: {
tuyaDatapoints: [
[1, 'temperature', tuya.valueConverter.divideBy10],
[2, 'humidity', tuya.valueConverter.raw],
[3, 'battery_state', tuya.valueConverter.batteryState],
[9, 'temperature_unit', tuya.valueConverter.temperatureUnitEnum],
],
},
whiteLabel: [
tuya.whitelabel('TuYa', 'ZTH01', 'Temperature and humidity sensor', ['_TZE200_yjjdcqsq']),
tuya.whitelabel('TuYa', 'ZTH02', 'Temperature and humidity sensor', ['_TZE200_9yapgbuv']),
tuya.whitelabel('TuYa', 'ZTH05', 'Temperature and humidity sensor', ['_TZE204_upagmta9']),
tuya.whitelabel('TuYa', 'ZTH08-E', 'Temperature and humidity sensor', ['_TZE200_cirvgep4']),
],
},

but doesn't work . :s

please help me :)

You can ignore the no converter available messages, _TZE204_upagmta9 is supported out-of-the-box in z2m 1.33.1

hello ,

Received Zigbee message from '0xa4c1385bbb64a21f', type 'attributeReport', cluster 'genBasic', data '{"65503":"91�,\u001991�,\u0007\u0000\u0000\u0000\u0000\u0011"}' from endpoint 1 with groupID 0

I run into the same problem with the same sensor.
I can connect, but only get linkquality data.

{
    "battery_state": null,
    "humidity": null,
    "linkquality": 160,
    "temperature": null,
    "temperature_unit": null
}

I am pretty new to zigbee, so please let me know what kind of information you need to help.
Thanks

MR Koenkk say , _TZE204_upagmta9 is supported out-of-the-box in z2m 1.33.1 but after a couple of days on the configutation it's doesn work , so i stay online for the update and another guy who have the same problem .

@aerandir08 have u a probleme with batterry ? my battery is empty on 24h

@aerandir08 have u a probleme with batterry ? my battery is empty on 24h

I just got the sensors. The battery is not full. It says about 50%.
I put on a external power supply, but it´s the same result.

Also ordered this device and paired to z2m and working fine on 1.33.1:

Initially the device showed Null but I selected celcius as Temperature unit, then values started appearing. Maybe selecting a Temperature unit is required?

it is the same sensor ?

3:03:08Received Zigbee message from '0xa4c1385bbb64a21f', type 'attributeReport', cluster 'genBasic', data '{"65503":"�\u0007�,\u0019�\u0007�,\u0007\u0000\u0000\u0000\u0000\u0011"}' from endpoint 1 with groupID 0
Debug 2023-10-10 13:03:43Received Zigbee message from '0xa4c1385bbb64a21f', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0
Debug 2023-10-10 13:03:45Received Zigbee message from '0xa4c1385bbb64a21f', type 'attributeReport', cluster 'genBasic', data '{"65506":56,"65508":1,"appVersion":73}' from endpoint 1 with groupID 0
Debug 2023-10-10 13:03:46Received Zigbee message from '0xa4c1385bbb64a21f', type 'commandMcuVersionResponse', cluster 'manuSpecificTuya', data '{"seq":768,"version":64}' from endpoint 1 with groupID 0

Mine looks like this:

Values are reported as such:

debug 2023-10-10 13:47:38: Received Zigbee message from 'garage/thermometer', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,187],"type":"Buffer"},"datatype":2,"dp":1}],"seq":10752}' from endpoint 1 with groupID 0
debug 2023-10-10 13:47:39: Received Zigbee message from 'garage/thermometer', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,73],"type":"Buffer"},"datatype":2,"dp":2}],"seq":11008}' from endpoint 1 with groupID 0

I’m going crazy, I have 5 sensors, none of them work, I have to make a mistake somewhere, but or? I don’t know!

it's my log at this time :

2023-10-10 13:59:38Received Zigbee message from '0xa4c1385bbb64a21f', type 'attributeReport', cluster 'genBasic', data '{"65503":"�\u0014�,\u0019�\u0014�,\u0007\u0000\u0000\u0000\u0000\u0011"}' from endpoint 1 with groupID 0
Debug 2023-10-10 14:00:02Received Zigbee message from '0xa4c1385bbb64a21f', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0
Debug 2023-10-10 14:00:03Received Zigbee message from '0xa4c1385bbb64a21f', type 'attributeReport', cluster 'genBasic', data '{"65506":56,"65508":1,"appVersion":73}' from endpoint 1 with groupID 0
Debug 2023-10-10 14:00:04Received Zigbee message from '0xa4c1385bbb64a21f', type 'commandMcuVersionResponse', cluster 'manuSpecificTuya', data '{"seq":768,"version":64}' from endpoint 1 with groupID 0
Debug 2023-10-10 14:00:04No converter available for 'ZTH05' with cluster 'manuSpecificTuya' and type 'commandMcuVersionResponse' and data '{"seq":768,"version":64}'

@rdneer u have a external decoder ?
i see difference between :

cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,73],"type":"Buffer"},"datatype":2,"dp":2}],"seq":11008},

and this mine

cluster 'manuSpecificTuya', données '{"seq":768,"version":64}'

I've re-paired the device to see what's happening when the device joins:

debug 2023-10-10 14:16:40: Device '0xa4c1384cfaf9961f' announced itself
debug 2023-10-10 14:16:49: Received Zigbee message from '0xa4c1384cfaf9961f', type 'commandMcuVersionResponse', cluster 'manuSpecificTuya', data '{"seq":1280,"version":64}' from endpoint 1 with groupID 0
debug 2023-10-10 14:16:49: Skipping message, definition is undefined and still interviewing
debug 2023-10-10 14:16:50: Received Zigbee message from '0xa4c1384cfaf9961f', type 'attributeReport', cluster 'genBasic', data '{"65506":56,"65508":1,"appVersion":73}' from endpoint 1 with groupID 0
debug 2023-10-10 14:16:50: Skipping message, definition is undefined and still interviewing
debug 2023-10-10 14:16:50: Received Zigbee message from '0xa4c1384cfaf9961f', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0
debug 2023-10-10 14:16:50: Skipping message, definition is undefined and still interviewing
debug 2023-10-10 14:16:55: Received Zigbee message from '0xa4c1384cfaf9961f', type 'readResponse', cluster 'genBasic', data '{"modelId":"TS0601"}' from endpoint 1 with groupID 0
debug 2023-10-10 14:16:55: Skipping message, definition is undefined and still interviewing
debug 2023-10-10 14:16:55: Received Zigbee message from '0xa4c1384cfaf9961f', type 'readResponse', cluster 'genBasic', data '{"manufacturerName":"_TZE204_upagmta9"}' from endpoint 1 with groupID 0
debug 2023-10-10 14:16:55: Skipping message, definition is undefined and still interviewing
debug 2023-10-10 14:16:56: Received Zigbee message from '0xa4c1384cfaf9961f', type 'readResponse', cluster 'genBasic', data '{"powerSource":3}' from endpoint 1 with groupID 0
debug 2023-10-10 14:16:56: Skipping message, definition is undefined and still interviewing
debug 2023-10-10 14:16:56: Received Zigbee message from '0xa4c1384cfaf9961f', type 'readResponse', cluster 'genBasic', data '{"zclVersion":3}' from endpoint 1 with groupID 0
debug 2023-10-10 14:16:56: Skipping message, definition is undefined and still interviewing
debug 2023-10-10 14:16:56: Received Zigbee message from '0xa4c1384cfaf9961f', type 'readResponse', cluster 'genBasic', data '{"stackVersion":0}' from endpoint 1 with groupID 0
debug 2023-10-10 14:16:56: Skipping message, definition is undefined and still interviewing
debug 2023-10-10 14:16:56: Received Zigbee message from '0xa4c1384cfaf9961f', type 'readResponse', cluster 'genBasic', data '{"hwVersion":1}' from endpoint 1 with groupID 0
debug 2023-10-10 14:16:56: Skipping message, definition is undefined and still interviewing
debug 2023-10-10 14:16:57: Received Zigbee message from '0xa4c1384cfaf9961f', type 'readResponse', cluster 'genBasic', data '{"dateCode":""}' from endpoint 1 with groupID 0
debug 2023-10-10 14:16:57: Skipping message, definition is undefined and still interviewing
debug 2023-10-10 14:16:57: Received Zigbee message from '0xa4c1384cfaf9961f', type 'readResponse', cluster 'genBasic', data '{}' from endpoint 1 with groupID 0
debug 2023-10-10 14:16:57: Skipping message, definition is undefined and still interviewing
info  2023-10-10 14:16:57: Successfully interviewed '0xa4c1384cfaf9961f', device has successfully been paired
info  2023-10-10 14:16:57: Device '0xa4c1384cfaf9961f' is supported, identified as: TuYa Temperature and humidity sensor (ZTH05)

Is this what you see when you pair the device to the coordinator?
I'm not using an external converter, default 1.33.1.
Coordinator type zStack3x0
Coordinator revision 20230507

info 2023-10-08 11:08:34: Successfully interviewed '0xa4c1385bbb64a21f', device has successfully been paired
info 2023-10-08 11:08:34: Device '0xa4c1385bbb64a21f' is supported, identified as: TuYa Temperature and humidity sensor (ZTH05)
info 2023-10-08 11:08:34: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"Temperature and humidity sensor","exposes":[{"access":1,"description":"Measured temperature value","label":"Temperature","name":"temperature","property":"temperature","type":"numeric","unit":"°C"},{"access":1,"description":"Measured relative humidity","label":"Humidity","name":"humidity","property":"humidity","type":"numeric","unit":"%"},{"access":1,"description":"State of the battery","label":"Battery state","name":"battery_state","property":"battery_state","type":"enum","values":["low","medium","high"]},{"access":3,"description":"Temperature unit","label":"Temperature unit","name":"temperature_unit","property":"temperature_unit","type":"enum","values":["celsius","fahrenheit"]},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"ZTH05","options":[{"access":2,"description":"Number of digits after decimal point for temperature, takes into effect on next report of device.","label":"Temperature precision","name":"temperature_precision","property":"temperature_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the temperature value (absolute offset), takes into effect on next report of device.","label":"Temperature calibration","name":"temperature_calibration","property":"temperature_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for humidity, takes into effect on next report of device.","label":"Humidity precision","name":"humidity_precision","property":"humidity_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the humidity value (absolute offset), takes into effect on next report of device.","label":"Humidity calibration","name":"humidity_calibration","property":"humidity_calibration","type":"numeric"}],"supports_ota":false,"vendor":"TuYa"},"friendly_name":"0xa4c1385bbb64a21f","ieee_address":"0xa4c1385bbb64a21f","status":"successful","supported":true},"type":"device_interview"}'
info 2023-10-08 11:08:34: Configuring '0xa4c1385bbb64a21f'
info 2023-10-08 11:08:34: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_successful","meta":{"description":"Temperature and humidity sensor","friendly_name":"0xa4c1385bbb64a21f","model":"ZTH05","supported":true,"vendor":"TuYa"},"type":"pairing"}'
debug 2023-10-08 11:08:34: Received Zigbee message from '0xa4c1385bbb64a21f', type 'readResponse', cluster 'genBasic', data '{"65534":0,"appVersion":73,"manufacturerName":"_TZE204_upagmta9","modelId":"TS0601","powerSource":3,"zclVersion":3}' from endpoint 1 with groupID 0
info 2023-10-08 11:08:34: Successfully configured '0xa4c1385bbb64a21f'
debug 2023-10-08 11:08:40: Received Zigbee message from '0xa4c1385bbb64a21f', type 'readResponse', cluster 'genBasic', data '{}' from endpoint 1 with groupID 0
info 2023-10-08 11:08:40: Successfully interviewed '0xa4c1385bbb64a21f', device has successfully been paired
info 2023-10-08 11:08:40: Device '0xa4c1385bbb64a21f' is supported, identified as: TuYa Temperature and humidity sensor (ZTH05)
info 2023-10-08 11:08:40: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"Temperature and humidity sensor","exposes":[{"access":1,"description":"Measured temperature value","label":"Temperature","name":"temperature","property":"temperature","type":"numeric","unit":"°C"},{"access":1,"description":"Measured relative humidity","label":"Humidity","name":"humidity","property":"humidity","type":"numeric","unit":"%"},{"access":1,"description":"State of the battery","label":"Battery state","name":"battery_state","property":"battery_state","type":"enum","values":["low","medium","high"]},{"access":3,"description":"Temperature unit","label":"Temperature unit","name":"temperature_unit","property":"temperature_unit","type":"enum","values":["celsius","fahrenheit"]},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"ZTH05","options":[{"access":2,"description":"Number of digits after decimal point for temperature, takes into effect on next report of device.","label":"Temperature precision","name":"temperature_precision","property":"temperature_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the temperature value (absolute offset), takes into effect on next report of device.","label":"Temperature calibration","name":"temperature_calibration","property":"temperature_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for humidity, takes into effect on next report of device.","label":"Humidity precision","name":"humidity_precision","property":"humidity_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the humidity value (absolute offset), takes into effect on next report of device.","label":"Humidity calibration","name":"humidity_calibration","property":"humidity_calibration","type":"numeric"}],"supports_ota":false,"vendor":"TuYa"},"friendly_name":"0xa4c1385bbb64a21f","ieee_address":"0xa4c1385bbb64a21f","status":"successful","supported":true},"type":"device_interview"}'
info 2023-10-08 11:08:40: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_successful","meta":{"description":"Temperature and humidity sensor","friendly_name":"0xa4c1385bbb64a21f","model":"ZTH05","supported":true,"vendor":"TuYa"},"type":"pairing"}'
debug 2023-10-08 11:08:40: Received Zigbee message from '0xa4c1385bbb64a21f', type 'attributeReport', cluster 'genBasic', data '{"65506":56,"65508":1,"appVersion":73}' from endpoint 1 with groupID 0

You think this is coming do coordinator?

Zigbee2MQTT:info 2023-10-10 14:36:07: Starting Zigbee2MQTT version 1.33.1-dev (commit #2aae1bd)
Zigbee2MQTT:info 2023-10-10 14:36:07: Starting zigbee-herdsman (0.19.1)
Zigbee2MQTT:debug 2023-10-10 14:36:07: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/config/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","databasePath":"/config/zigbee2mqtt/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"adapter":"ezsp","path":"/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230803180624-if00"}}'
Zigbee2MQTT:info 2023-10-10 14:36:11: zigbee-herdsman started (resumed)
Zigbee2MQTT:info 2023-10-10 14:36:11: Coordinator firmware version: '{"meta":{"maintrel":"3 ","majorrel":"6","minorrel":"10","product":8,"revision":"6.10.3.0 build 297"},"type":"EZSP v8"}'

@jafreenas I'm facing the same issue with the same coordinator :

info  2023-10-10 14:58:55: Starting Zigbee2MQTT version 1.33.1 (commit #7e630391)
info  2023-10-10 14:58:55: Starting zigbee-herdsman (0.19.0)
debug 2023-10-10 14:58:55: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/opt/zigbee2mqtt/data/coordinator_backup.json","databaseBackupPath":"/opt/zigbee2mqtt/data/database.db.backup","databasePath":"/opt/zigbee2mqtt/data/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"path":"/dev/ttyACM0"}}'
info  2023-10-10 14:58:59: zigbee-herdsman started (resumed)
info  2023-10-10 14:58:59: Coordinator firmware version: '{"meta":{"maintrel":"3 ","majorrel":"6","minorrel":"10","product":8,"revision":"6.10.3.0 build 297"},"type":"EZSP v8"}'

Be aware that it is in experimental mode, so the issue may be fixed later ?

@aerandir08 have u a probleme with batterry ? my battery is empty on 24h

Yes, i have the same problem. I soldered some wires on to measure the current consumption. It takes about 9.7 mA in paring mode and about 4.8 mA if it´s paired. So a 220 mAh CR2032 takes about 2 days to be empty.
Seems like something is wrong with these guys. I will go with the WSD500A. They work perfectly fine out of the box.

I received three ZTH05.
The pairing is ok.
I have no value in Z2M, but if I push one time on the button behind the ZTH05, the values are displayed in Z2M. 👍

I'm surprised Francis, I also have the ZTH05, and they don't report any information, could see your logs ?

I am facing same problem as @jafreenas, only lqi value is present, i tried changing battery, pushing button after reconnect.
I am not up to date with debug info from z2m but I am willing to help anyway.

@jafreenas it seems like values on screen only updates after reconnecting battery. What about your device?

Thank you for your feedback @kamilkrz
it would be interesting to see your logs.
I think the battery runs out over time because it does not communicate too often with the dongle.
I am surprised because @francisbesset has no problem.
It is at the origin of the decoder of the ZHT05 .
Can you send your logs? send your photos? and say under which firwmare you work.
I followed what @francisbesset said , we chat on twitter when it’s available , but I can’t reproduce .
I have the same thing as you, only the signal ( lqi)
May be one day we will find the problem.
@francisbesset asks me to test on a hub tuya , but I don’t have any . you have?

Debug 2023-10-25 18:59:46Received Zigbee message from 'termometr_poddasze', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0
Debug 2023-10-25 18:59:46Received Zigbee message from 'termometr_poddasze', type 'attributeReport', cluster 'genBasic', data '{"65506":56,"65508":1,"appVersion":73}' from endpoint 1 with groupID 0
Debug 2023-10-25 18:59:47Received Zigbee message from 'termometr_poddasze', type 'commandMcuVersionResponse', cluster 'manuSpecificTuya', data '{"seq":768,"version":64}' from endpoint 1 with groupID 0
Debug 2023-10-25 18:59:47No converter available for 'ZTH05' with cluster 'manuSpecificTuya' and type 'commandMcuVersionResponse' and data '{"seq":768,"version":64}'
Debug 2023-10-25 19:01:04Received Zigbee message from 'termometr_poddasze', type 'attributeReport', cluster 'genBasic', data '{"65503":"\u0000\u0000\u0000\u0000\u0011"}' from endpoint 1 with groupID 0
Debug 2023-10-25 19:01:27Received Zigbee message from 'termometr_poddasze', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0
Debug 2023-10-25 19:01:28Received Zigbee message from 'termometr_poddasze', type 'attributeReport', cluster 'genBasic', data '{"65506":56,"65508":1,"appVersion":73}' from endpoint 1 with groupID 0
Debug 2023-10-25 19:01:29Received Zigbee message from 'termometr_poddasze', type 'commandMcuVersionResponse', cluster 'manuSpecificTuya', data '{"seq":768,"version":64}' from endpoint 1 with groupID 0
Debug 2023-10-25 19:01:29No converter available for 'ZTH05' with cluster 'manuSpecificTuya' and type 'commandMcuVersionResponse' and data '{"seq":768,"version":64}'

This is on forced comunication (short button press)

I was able to confirm that i have same board as @rdeneer

As per my setup docker build from latest tag so this may vary:

[1.33.1](https://github.com/Koenkk/zigbee2mqtt/releases/tag/1.33.1) commit: [7e63039](https://github.com/Koenkk/zigbee2mqtt/commit/7e63039)
Coordinator type - EZSP v8
Coordinator revision - 6.10.3.0 build 297

This is by far first Zigbee device that I have difficulties with connection

Hope that helps.
If more logs needed please provide info how to proper gather those.

:edit
Sorry but I don't have tuya gateway.

I have the same problem with my newly arrived device, no data is shown apart from lqi.
Correctly paired, I can see all the entities but no values.
Same message "No converter available for 'ZTH05' with cluster 'manuSpecificTuya' and type 'commandMcuVersionResponse' and data '{"seq":768,"version":64}'"
My device is 0xa4c138785706fb9b (0x4880), I am running the HA addon, edge version.
Thank you.

we all have the same problem, stay tuned for good news ;)

I'll follow this issue, having the same issue. Correct values on the screen, but no data send over zigbee. Thats my dongle: 10c4:ea60 Silicon Labs CP210x UART Bridge I am running zigbee2mqtt in docker, but that shouldn't change anything.

After pairing i find these ufo lines in the log:

Zigbee2MQTT:debug 2023-10-30 12:31:03: Received Zigbee message from '0xa4c138089eb39da7', type 'commandMcuVersionResponse', cluster 'manuSpecificTuya', data '{"seq":1280,"version":64}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2023-10-30 12:31:03: No converter available for 'ZTH05' with cluster 'manuSpecificTuya' and type 'commandMcuVersionResponse' and data '{"seq":1280,"version":64}'
Zigbee2MQTT:debug 2023-10-30 12:31:03: Received Zigbee message from '0xa4c138089eb39da7', type 'attributeReport', cluster 'genBasic', data '{"65506":56,"65508":1,"appVersion":73}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2023-10-30 12:31:03: Received Zigbee message from '0xa4c138089eb39da7', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0


Zigbee2MQTT:debug 2023-10-30 12:32:26: Received Zigbee message from '0xa4c138089eb39da7', type 'attributeReport', cluster 'genBasic', data '{"65503":"ҵ�,iյ�,iص�,i۵�,i���,i���,i���,i���,i���,i���,i���,i���,i"}' from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2023-10-30 12:32:27: Received Zigbee message from '0xa4c138089eb39da7', type 'attributeReport', cluster 'genBasic', data '{"65503":"���,i���,i���,i���,i���,\u0011\u0006\u0000\u0000\u0000\u0012��,i��,i"}' from endpoint 1 with groupID 0

So I've made the below tests, hoping it will help to get to those tuya sensors working with ZHA/Zigbee2MQTT:

Initially I received the device, paired it through zha/Home assistant, then as I realized it was not supported added the latest quirks from https://github.com/zigpy/zha-device-handlers patching the "_TZE204_upagmta9" signature but none worked.

Then let the device paired and overnight they were out of battery ....

Then decided to wire one of them to a 3.3V power source and look at power consumption, noticing that once paired the device continue to consume over 5mA which I think was already mentioned by @aerandir08

Then I popped a separate zigbee dongle (ConBEE II) and launch a 1.33.1 Zigbee2MQTT on a separated network only pairing the "_TZE204_upagmta9". The device get paired and recognized but:

• Just like with ZHA power consumption is 5.73mA so way to high
• I have no value in the UI (and they don't update at all on the device screen), but the switch from °F to °C works just after pairing or just after 1 short press on the pairing button of the device. Same, value on the screen gets updated on 1 short press.

At last I found a tuya zigbe gateway, installed the smart Life app, paired the same device to it. Once paired the power consumption drop to 0.017mA ... In the pp, The "update screen" of the device indicate ZigBee Module v1.0.9 and MCU Module v1.0.0. The values are updated. Also confirm the app reports usage of the battery by state and not % on this device (Low, Mid, High). Changing from °F to °C on the smart life app warn it will only be changed on next device wake-up cycle... Which I was not patient enough after 20 minutes of test to witness ...

So it seems the device wait for a "protocol answer"? from the gateway before going to sleep ... otherwise the device stay in a "lock" mode consuming 5.73mA and not updating the internal screen... draining the battery...

The "draining state" can also happen while connecting on the smart life app, if short press on the button, or unplug/plug the power source.

In term of update, the device seems to updates the internal screen every 10 seconds (we can see power consumption move from 0.017mA to around 0.03/0.04mA). By the way measures seems unstable (0.3 *C variation between measure), the app seems to store only 1 measure at the hour but may display in between values from the iot server. I don't know about the zigbee getaway itself.

Next step will be to receive a zigbee sniffing stick and see if I can get zigbee messages and fine tune the message cadence. ...

Good Job . thanks you for your feedback

Copy & paste your configuration.yaml

Sorry, I was standing next to myself. I'm a newbie.

I add it before to --> /homeassistant/configuration.yaml

After add it to --> /homeassistant/zigbee2mqtt/configuration.yaml the reboot was without a failure possible.

`
homeassistant: true
mqtt:
server: mqtt://core-mosquitto:1883
user: addons
password: aipailxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxth
serial:
port: >-
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20221201204234-if00
adapter: ezsp
frontend:
port: 8099
advanced:
homeassistant_legacy_entity_attributes: false
legacy_api: false
legacy_availability_payload: false
device_options:
legacy: false
devices:
'0xe0798dfffeb91190':
friendly_name: Steckdose Pumpe BW-SHP15
description: Garage
'0x00124b002acbc563':
friendly_name: Sensor Pumpe Wasserfass
'0xa4c138d8d5b16045':
friendly_name: Sensor Temperatur Garage
'0xa4c1382bb4ed334e':
friendly_name: Rolladen EG West rechts
description: Rolladen EG West rechts
'0x00124b002a659444':
friendly_name: Sensor Garagentüre
'0xa4c1386f16706eef':
friendly_name: Rolladen EG West links
description: Rolladen EG West links
'0xa4c13898539e8897':
friendly_name: Sensor Wasser Küche
description: |-
Liegt unter dem Waschbecken auf dem Boden.
Kontakt geschlossen --> alles ok
Kontakt offen --> Alarm
'0xa4c138a19457b8c0':
friendly_name: Steckdose2
description: Heizungsraum als Repeater
'0xa4c138ae4fb0ebdd':
friendly_name: Sensor Temperatur Heizungsraum
'0xbc026efffeca363a':
friendly_name: Zigbee Repeater Ikea
'0x00124b002a4f7899':
friendly_name: Sensor Fenster Gästezimmer
'0xa4c1387d83aba0f3':
friendly_name: Sensor Wasser Keller Heizungsraum
description: |-
Liegt neben Wärmepumpe auf dem Boden.
Kontakt geschlossen --> alles ok
Kontakt offen --> Alarm
'0xa4c138695a593d73':
friendly_name: Sensor Temperatur Gästezimmer
'0xa4c138fb9ebebca6':
friendly_name: Rolladen EG Sud
'0x00158d0009df3ac6':
friendly_name: 1 Test Türsensor
'0xa4c13846a083fc2f':
friendly_name: Sensor Temp LCD
blocklist: []

external_converters:

• ext_converter.js
  `
  After add a new battery to sensor and reboot HA the temperature will not shown at HA.
  Further the ZTH05 sensor is not shown at dash board,
  So the problem is not solved

the external converter works perfectly.
it will be integrated into the source on December 1st.
and therefore no longer need to add a line to configuration.yaml.
the configuration.yaml file is that of Z2m, and not that of HA

I just think there is a mistake.
indentation

I will wait further 2 weeks, thank you
Have a nice Sunday

Good afternoon. I have two such devices, bought from different sellers on AliExpress. Wired using a converter by @Koenkk
Koenkk/ext.js
But there are some problems:
On both, the battery always shows "full"
And with one, something incredible happens. Last seen dropped sharply when the battery was not full, as a result, it drained it in a few hours. Replacing the battery with a new one and reconnecting the device helped.

First: Thanks for the work! Excuse my ignorance, but the sensors are now displayed in my zigbee2mqtt ui. Sometimes the details still say "none", but when I reload the page the values are correct. Also under "status".

However, the messages on the topic still sometimes write "temperature": null, which is why homeassistant then sets the entities to "unknown" at some point.

Has the external converter not yet worked for me or is the problem in home assistant?

Home assistant and zigbee2mqtt are two separate docker containers for me.

Good afternoon. Yesterday, I specially connected a new sensor with a weak battery, got the same picture as last seen, and after replacing the battery, resetting the device with a button and connecting, the operation of the sensor resumed in normal mode.
Currently, all temperature sensors of various types are working normally.
I currently have the following sensors:
They work fine
1.
Zigbee Model TS0601
Zigbee Manufacturer _TZE200_9yapgbuv
2.
Zigbee Model TS0601
Zigbee Manufacturer _TZE204_upagmta9
3.
Zigbee Model TS0601
Zigbee Manufacturer _TZE200_yjjdcqsq

Even with a new battery and a fully reset/repair, my new ZTH05 still shows null.

I'm able to change from Fahrenheit to Celsius from Zigbee2mqtt.

with the external converter ?

My experience is with stock zigbee2mqtt. I haven't used an external converter.

the following ext converter might fix the issue: https://gist.github.com/Koenkk/43579e5e8d06e84f2af77dfa3b2196a7

save this as file next to configuration.yaml as ext_converter.js
add it to configuration.yaml:
external_converters:

• ext_converter.js
  start z2m, check if issue is fixed

the following ext converter might fix the issue: https://gist.github.com/Koenkk/43579e5e8d06e84f2af77dfa3b2196a7

save this as file next to configuration.yaml as ext_converter.js add it to configuration.yaml: external_converters:

• ext_converter.js
  start z2m, check if issue is fixed

Great, but I understand that This device will start working normally without ext_converter in the next release of Zigbee2MQTT?

yes 2023/12/01

I want to add just my experience because I didnt see anyone else in this post to experience the same thing.
I bought a TH01 sensor, at the beginning I had same issue as other users: only LQI data was sent, temp/humidity were NULL.
But I had very hard time trying to have the LQI because after pairing, the led on the sensor stay forever solid red.
After searching I found this post and I did all the suggested things:

• Reset the sensor with it's button until red flashing led.
• Removed the battery
• Deleted the sensor from Z2M and rebooted HA
• Added the external converter configuration to configuration.yaml in the z2m folder
• Rebooted HA again
• Tried to pair the sensor again in z2m.
  The sensor was paired in few seconds but N/A in the values. Clicked on "Celsius" of "Fahreneit" changed the values from N/A tu "null". In the meantime, the LED on the sensor staied SOLID RED for all the time. Tried putting the battery off and on but nothing changed.
  While I was searching for another solution, after about 5 minutes I noticed that the led was finally off and finally all the values were there. Moved the sensor in the fridge to see if the values changes and it did after about 5 minutes, and keeps changing every 5 minutes.

So If someone arrives here becaue it's sensor is unresponsive and has the led solid red for long time, just wait 5 minutes to see if this changes.

Anyway it still puzzle me: why this happens? I see no other users experienced this....

Final note: I didnt suggest to buy this sensor: it has no "openings" for the air to enter and picked by the sensor, so it's temperature updates are really really slow: moved from a 28 °C to the fidge at 4°C, after 15 minutes it still read 14°C, deacreasoing very slowly.... It's ok for an application where temp doesnt change too much or too fast.

There is a problem with this sensor when a connection is lost. he is endlessly looking for a pairing with Z2M, when he does not find it, he consumes the battery in a few hours, this is really the big problem with this cheap sensor..

It sure is a piece of crap. The Xiaomi one is the same price and so far much better, and can be flashed between ZigBee and Bluetooth.

My tip for anyone buying these: At least get a 10 pack of CR2032 batteries! A mod with a AAAs would be nice.

I have had a different problem with my sensor, a cheap ZTH05.
After having solved the problem with null values (solved by using the external converter), my sensor paired with HA and started sending data correctly with a normal battery drain. However, after around 8 hours, it invariably stopped sending data even though keeping changing the temperature on the display, no way to have it back in the network unless I did a fresh pairing.
I have changed sensor location, battery, procedures and whatnot but always with the same result: after about 8 hrs the sensor went away.
And finally went to the bin... :D

could you give me the link to the xiaomi sensors?

Here's the similar Xiaomi models that support BT to Zigbee conversion among other things.

https://github.com/pvvx/ATC_MiThermometer

I have the LYWSD03MMC, which is similar in form factor and function. It was $7 CAD from AliExpress 'choice' vs $7 for the Tuya ZTH05.

@jafreenas
Works mit newest Zigbee@MQTT update
Thank you :-)

Updating to the latest Z2M, we have to remove the external converter line in configuration.yaml?

I have updated and the configuration.yaml seems to have been regenerated (I did not find the external converter reference anymore in the file)

@benoitm974 btw I would expect that z2m already send the 0xef00/0x03, the device should do a deviceAnnounce when it connects and z2m replies to it here

If this is not the case, maybe there is some race condition and the following ext converter might fix the issue: https://gist.github.com/Koenkk/43579e5e8d06e84f2af77dfa3b2196a7

* save this as file next to `configuration.yaml` as `ext_converter.js`

* add it to `configuration.yaml`:

external_converters:
  - ext_converter.js

* start z2m, check if issue is fixed

Salut Benoit et merci de ton aide.

Malheureusement quand j'ajoute ton code j’obtiens:

J'utilise Hassos, aurais-tu une idée ?

the external converter works perfectly.
it will be integrated into the source on December 1st.
and therefore no longer need to add a line to configuration.yaml.
the configuration.yaml file is that of Z2m, and not that of HA

How do I pair my ZTH05 with Z2M?
I enable paring in Z2M and I push the button on the backside of the device but it doesn't showup in Z2M

Thank you!

The ZTH05 temperature and humidity sensor pairs fine with Z2M and provides the relevant data points, but it's still draining the battery completely in the space of about 24 hours. Is there any fix for this?

Hello, @benoitm974 @Koenkk did an excellent job, unfortunately when the sensor loses the signal, it only consumes the battery, there is no solution to date. Personally I abandoned this type of sensor for Sonoff. more expensive but it works!