[Device Support Request] TS0601 _TZE204_upagmta9 Tuya outdoor temperature and humidity sensor #2694
Comments
|
It seems not the be working either on zigbeeMQTT, there might be some aspect of the protocol missing at pairing, trying to get element from snifing protocol here : Koenkk/zigbee2mqtt#19137 |
|
@benoitm974 Seems lit a batch that beside the problems with zigbee information transmission, they have huge problems with battery time, or maybe because it tries to send information to gateway to often, the battery just goes dead in 12h. |
|
No in fact the device uses tuya specific protocol, the device works well when use with their gateway and Tuya app and don't have battery issue. The problem exists in both zigbee2mqtt and ZHA where the current code doesn't follow the tuya protocol after pairing the device stay "locked" in a waiting for answer state where it doesn't update the screen info nor send any data and consume all the battery in 12 to 24h...
|
|
I have a similar issue with a device that has the same specification/ID _TZE204_upagmta9 TS0601 For me it does not show ANY entities at all |
|
Hello! For this sensors as a temporary sollution i added a wifi zigbee gateway and used tuya integration for them. They do eat batteries if not communicating good with ha integration. I wait for news when they cand be integrated locally. :( |
Soo they are worse than "for example" I bought one as a test, but might return/see if I can get a refund for it, if there is no probable fix in the next few days. Since its a choice store getting a refund is quite easy. |
|
I wanted with display, i suppose will be a while until this model will be added to the fully supported devices, |
|
It looks like devs from zigbee2mqtt made it working (Koenkk/zigbee2mqtt#19137 (comment)) |
|
Indeed after sniffing zigbee traffic and debuging @Koenkk found the race condition preventi the 0xef00 / 0x03 command sent just after the sensors join the network which was keeping the device in a loop mode... If any one with experience on zha code can point in the right directtion for sending command when sensor joint I'm open to try/look into it. |
|
I manage to get something on dashboard for ZTH05
correct file path would be, 
|
|
The question is not which definition to use, since either V03 or V04 would work, the issue is how to have ZHA to send a custom tuya command on joining to get the sensor to start sending data on regular interval and to sleep in between. |
|
Sounds like I should just pull the battery from mine until this is resolved. Can anyone recommend a temperature sensor that does work properly? |
|
I use these working ok but no screen, and you need to provide the 2 AAA batteries. |
|
I also have a couple of these that are quite useless in ZHA... is anyone working on a fix please? |
|
Adding my support to merge the same fix from zigbee2mqtt which looks like it will be deployed Jan 1st: |
|
Anyone please? Would be nice to have them in ZHA because they are cheap, have a display and natively have zigbee. The people who buy these are mostly the ones who have bricked a LYWSD03MMC and are looking for something with native zigbee. |
|
I have the same one and can't get it working. |
|
Same for me, can't get it working. |
|
Same for me. I have such devices and they don't work with ZHA. |
|
Hello! The correct model for this device seems to be ZTH05 I'm having same issues. Identified as a different device and no entities.
|
I suppose the question is whether there is a way to force the real identity onto devices that list a fake identity. |
|
@marcoaureliovaz, i'm seeinig the exact same on my ZHA installation |
|
I tried some time with ZHA but it didn't work and the "pairing" seemed not to conclude... (After pairing, the logs were always bringing new messages and at the device, low battery icon active) ZigBee2MQTT |
|
With the next HA version 2024.2.0 beta (releasing 2024/01/31), you can try to send the "Tuya query data" command through the clusters menu UI if the manufacturer cluster is added using a quirk. Copying my answer from Discord: That way, no manual command sending would be involved. |
Thanks @TheJulianJES so much! We could on create a new 05 variation and then A Add the import "EnchantedDevice" B Add the variation this way` ` |
Sorry.... But I have the same issue and after looking at this thread I got the quirk indicated and made the suggested changes. It picked up that quirk and I get the identities for humidity and temperature which I didn't have before. But they have no values. Thank you. |
Only changing the quirk will not be enough until this is relaeased or you ensure to get the beta version install and test the new quirk... |
Thank you very much for the promptly reply. I'll wait until this is changed... I don't usually install beta versions of HA because I don't have a "test" system. But I'll keep an eye on this. |
Well I was thinking about cleaning it up for a PR but 2024.11.0 changes how the ts0601_sensors are handled(YAY), and I have no idea how to hack it into that implementation. |
And this got them working again after my HA 11.0 update. 😀 Thank you! 👍🏻 |
|
Hi @Peketr, Your script for Tuya works for temperature sensor but not humidity sensor on my side. Anyway, thanks for the work! -- Edit: after restarting HA again, I have the 2 sensors. Thanks for the work @Peketr |
|
@Peketr the quirk works perfectly on my ZTH05. edit: i have to add this remark, |
|
I have ordered this device from Ali Express, identifying as TS0601 / _TZE200_qrztc3ev and tried to implement the quirk. However, it didn't bring any benefit and I was also not seeing the quirk has been considered, so I checked it and TZE200_qrztc3ev was missing in the file. I tried to add it, restarted HA, tried to add the device again in ZHA and now I'm getting valid temperature information but wrong humidity (5.4% instead of 50%). 
Could it be that I added it to the wrong section in the quirk file? Which is the right one? 
|
Were you able to find a solution for this sensor? I received the same one the other day. And I don't receive any information from it. |
|
@atus42 - Your patch works for my TS0601 / _TZE204_upagmta9 with friendly name "ZTH05". Thank you so much! |
|
Also working here with ts0601_sensor.TuyaTempHumiditySensorVar05, at the beginning there were no sensors, just needed to restart HA once after pairing to get them to show.
|
|
Hello zha: ok i have changed my configuration.yaml this is the new quirks file to copy in this folder, after i have made them?! but this folder is different to so i copied the file ts0601_sensor.py after this all other zha tools doesn t exist any more |
You just need to create a subclass of I don't know how often this pattern shows up, if it's often enough, we could just add it as a parameter to |
|
sorry, i don t understand what i have to do now, i thought i change my configuration.yaml i have changed my configuration.yaml zha: i have build the folder /config/custom_zha_quirks/ts0601_sensor.py |
|
Hi @FranzTen yes, that's what I did, and it works for me. The name of the folder doesn't matter - it has to match the definition in config.yaml I think your next steps would be checking the log files and diagnosis data. Possibly you don't have |
|
Without being able to test, this is what I think this could look like with a custom v2 quirk. https://gist.github.com/prairiesnpr/0b7bf1a63da6224ad9b3147ead120109 We can probably just update |
No, unfortuantely no solution. As mentioned, I modified the Phython script by adding the text in the red square to the file (see screenshot) but I can only get the temperature (after a restart of HomeAssistant), not the humidity (humidity entity is shown but with wrong values). |
As in the scaling is wrong, e.g., off by a factor of ten, or it's completely wrong and likely on the wrong DP? |
|
E.g. 5.4% instead of 52% shown on the display at the same time |
|
Thanks for all the explanation. I added this quirk https://github.com/Peketr/zha-device-handlers/blob/Peketr-patch-zht05/zhaquirks/tuya/ts0601_sensor.py and it works. Battery level is changing from 25% to 50%, I'll monitor in the next days. |
|
@FabTangi can you test https://gist.github.com/prairiesnpr/0b7bf1a63da6224ad9b3147ead120109 and let me know if it works the same? |
|
Can confirm, that I also have the same model I used: and I could also recreate what @dn-gt saw
If I add it to this line, the good news is the sensors finally show up,
But then I was going through the python code, and I noticed this line was commented out, which seems to remove the humidity values being multiply by 10, so I moved the comment along, to put the 10x multiply back in, and now it works!
I'm new to this git hub thing, and so not sure why @Peketr removed that 10x multiplier in his code, maybe to get it to work for a different sensor? So not sure how to combine / add the change that @dn-gt suggseted, along with re-instanting the 10 multiplier, so everyone can benefit? |
|
@JKGHPO Just use the built in quirk here. see So your custom quirk is simply. from zhaquirks.tuya.builder import TuyaQuirkBuilder
(
TuyaQuirkBuilder("_TZE200_qrztc3ev", "TS0601")
.tuya_temperature(dp_id=1, scale=10)
.tuya_humidity(dp_id=2, scale=10)
.tuya_battery(dp_id=4)
.skip_configuration()
.add_to_registry()
) |
I have tried to do the same: But somehow, it still doesn't work for me: I try to check if the custom quirk is really applied but can't find how: I have already try to reboot HA, as well as removed/added the device, multiple times . |
Using this method I can see the custom quirk being applied, but again, the humidity and temperature sensor do not seem to report: here is the quirk: |
|
Turn on debug logging, make sure it's sent some reports, and post it. Should see something along the lines of dp=1, dp=2, etc. That said, let's move this to its own request, it's not related to _TZE204_upagmta9 |
|
Alright, here is the new ticket #3710, thanks |
|
I have the device named But it's not working however. The connection is working but I don't get any temperature or humidity. It's always 0. Since I own a lot of these kind of devices I tried to find any difference. And the only thing that i noticed is the new device that's not working have a cluster that the other don't have.
Maybe there is a polling setting missing? Does someone have a similar device? Any idea how to get this device running? |
|
@webserviceXXL : I have created a new issue dedicated to _TZE200_qrztc3ev here : #3710 |
|
Changing RH_MULTIPLIER from 10 to 100 and waiting for the next update of the device solved the humidity issue for me.
|
and others
Problem description
No values recognized
Device info
TS0601
by _TZE204_upagmta9
Zigbee info
IEEE: a4:c1:38:74:06:b0:2c:89
Nwk: 0x2aff
Device Type: EndDevice
LQI: 192
RSSI: -52
Last Seen: 2023-11-01T13:11:52
Power Source: Battery or Unknown
Solution description
How can i get or make a custom quirk for this device?
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]
Device signature
Device signature
{ "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)", "endpoints": { "1": { "profile_id": "0x0104", "device_type": "0x0051", "input_clusters": [ "0x0000", "0x0004", "0x0005", "0xef00" ], "output_clusters": [ "0x000a", "0x0019" ] } }, "manufacturer": "_TZE204_upagmta9", "model": "TS0601", "class": "zigpy.device.Device" }Diagnostic information
Diagnostic information
{ "home_assistant": { "installation_type": "Home Assistant OS", "version": "2023.10.5", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.11.5", "docker": true, "arch": "aarch64", "timezone": "Europe/Bucharest", "os_name": "Linux", "os_version": "6.1.21-v8", "supervisor": "2023.10.1", "host_os": "Home Assistant OS 11.1", "docker_version": "24.0.6", "chassis": "embedded", "run_as_root": true }, "custom_components": { "browser_mod": { "version": "2.3.0", "requirements": [] }, "hacs": { "version": "1.32.1", "requirements": [ "aiogithubapi>=22.10.1" ] }, "lovelace_gen": { "version": "0.1.1", "requirements": [ "jinja2" ] }, "fusion_solar_kiosk": { "version": "3.0.6", "requirements": [] }, "scheduler": { "version": "v0.0.0", "requirements": [] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "after_dependencies": [ "onboarding", "usb" ], "codeowners": [ "@dmulcahey", "@adminiuga", "@puddly" ], "config_flow": true, "dependencies": [ "file_upload" ], "documentation": "https://www.home-assistant.io/integrations/zha", "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp", "universal_silabs_flasher" ], "requirements": [ "bellows==0.36.5", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.105", "zigpy-deconz==0.21.1", "zigpy==0.57.2", "zigpy-xbee==0.18.3", "zigpy-zigate==0.11.0", "zigpy-znp==0.11.6", "universal-silabs-flasher==0.0.14", "pyserial-asyncio-fast==0.11" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "*2652*", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "1A86", "pid": "55D4", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus v2" ] }, { "vid": "10C4", "pid": "EA60", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*zigstar*", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "*conbee*", "known_devices": [ "Conbee II" ] }, { "vid": "10C4", "pid": "8A2A", "description": "*zigbee*", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "*zigate*", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "*zigate*", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "*bv 2010/10*", "known_devices": [ "Bitron Video AV2010/10" ] } ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube*" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "*zigate*" }, { "type": "_zigstar_gw._tcp.local.", "name": "*zigstar*" }, { "type": "_uzg-01._tcp.local.", "name": "uzg-01*" }, { "type": "_slzb-06._tcp.local.", "name": "slzb-06*" } ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 11007, "manufacturer": "_TZE204_upagmta9", "model": "TS0601", "name": "_TZE204_upagmta9 TS0601", "quirk_applied": false, "quirk_class": "zigpy.device.Device", "manufacturer_code": 4417, "power_source": "Battery or Unknown", "lqi": 192, "rssi": -52, "last_seen": "2023-11-01T13:15:58", "available": true, "device_type": "EndDevice", "signature": { "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)", "endpoints": { "1": { "profile_id": "0x0104", "device_type": "0x0051", "input_clusters": [ "0x0000", "0x0004", "0x0005", "0xef00" ], "output_clusters": [ "0x000a", "0x0019" ] } }, "manufacturer": "_TZE204_upagmta9", "model": "TS0601" }, "active_coordinator": false, "entities": [ { "entity_id": "sensor.tze204_upagmta9_ts0601_rssi", "name": "_TZE204_upagmta9 TS0601" }, { "entity_id": "sensor.tze204_upagmta9_ts0601_lqi", "name": "_TZE204_upagmta9 TS0601" } ], "neighbors": [], "routes": [], "endpoint_names": [ { "name": "SMART_PLUG" } ], "user_given_name": null, "device_reg_id": "f617a18abfa66229233f67c4d981d85f", "area_id": null, "cluster_details": { "1": { "device_type": { "name": "SMART_PLUG", "id": 81 }, "profile_id": 260, "in_clusters": { "0x0004": { "endpoint_attribute": "groups", "attributes": {}, "unsupported_attributes": {} }, "0x0005": { "endpoint_attribute": "scenes", "attributes": {}, "unsupported_attributes": {} }, "0xef00": { "endpoint_attribute": null, "attributes": {}, "unsupported_attributes": {} }, "0x0000": { "endpoint_attribute": "basic", "attributes": { "0x0001": { "attribute_name": "app_version", "value": 73 }, "0x0004": { "attribute_name": "manufacturer", "value": "_TZE204_upagmta9" }, "0x0005": { "attribute_name": "model", "value": "TS0601" } }, "unsupported_attributes": {} } }, "out_clusters": { "0x0019": { "endpoint_attribute": "ota", "attributes": {}, "unsupported_attributes": {} }, "0x000a": { "endpoint_attribute": "time", "attributes": {}, "unsupported_attributes": {} } } } } } }Logs
Logs
Custom quirk
Custom quirk
Additional information
https://www.aliexpress.com/item/1005005627336725.html
Zigbee Version
I tried some quirks but with no help.
Can someone help me?
The text was updated successfully, but these errors were encountered: