[APP][Pro] Tuya Zigbee App

[Rudi_Hendrix]

Let’s stick to English.

And I think you are better off building your own version of the app

[DaPicard]

Hi Johan,

I would like to request support for the Tuya Zigbee Pressure/Contact Sensor. Homey pairs it as a generic Zigbee device without functions.

Here are the device details:

• Manufacturer ID / Product ID: TS0601 _TZE200_seq9cm6u / _TZE204_seq9cm6u

“ids”: {
“modelId”: “TS0601”,
“manufacturerName”: “_TZE200_seq9cm6u”
},
“endpoints”: {
“ieeeAddress”: “a4:c1:38:d1:ee:0b:be:07”,
“networkAddress”: 61652,
“modelId”: “TS0601”,
“manufacturerName”: “_TZE200_seq9cm6u”,
“endpointDescriptors”: [
{
“status”: “SUCCESS”,
“nwkAddrOfInterest”: 61652,
“_reserved”: 16,
“endpointId”: 1,
“applicationProfileId”: 260,
“applicationDeviceId”: 12,
“applicationDeviceVersion”: 0,
“_reserved1”: 1,
“inputClusters”: [
0,
61184
],
“outputClusters”: [
10,
25
]
}
],
“deviceType”: “enddevice”,
“receiveWhenIdle”: false,
“capabilities”: {
“alternatePANCoordinator”: false,
“deviceType”: false,
“powerSourceMains”: false,
“receiveWhenIdle”: false,
“security”: false,
“allocateAddress”: true
},
“extendedEndpointDescriptors”: {
“1”: {
“clusters”: {
“basic”: {
“attributes”: [
{
“acl”: [
“readable”,
“reportable”
],
“id”: 0,
“dataTypeId”: 32,
“name”: “zclVersion”,
“value”: 3
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 1,
“dataTypeId”: 32,
“name”: “appVersion”,
“value”: 105
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 2,
“dataTypeId”: 32,
“name”: “stackVersion”,
“value”: 1
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 3,
“dataTypeId”: 32,
“name”: “hwVersion”,
“value”: 1
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 4,
“dataTypeId”: 66,
“name”: “manufacturerName”,
“value”: “_TZE200_seq9cm6u”
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 5,
“dataTypeId”: 66,
“name”: “modelId”,
“value”: “TS0601”
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 6,
“dataTypeId”: 66,
“name”: “dateCode”,
“value”: “”
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 7,
“dataTypeId”: 48,
“name”: “powerSource”,
“value”: “battery”
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 65472,
“dataTypeId”: 66
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 65487,
“dataTypeId”: 33
},
{
“acl”: [
“readable”,
“writable”,
“reportable”
],
“id”: 65502,
“dataTypeId”: 32
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 65533,
“dataTypeId”: 33,
“name”: “clusterRevision”,
“value”: 2
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 65534,
“dataTypeId”: 48,
“name”: “attributeReportingStatus”,
“value”: “PENDING”
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 65504,
“dataTypeId”: 72
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 65505,
“dataTypeId”: 72
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 65506,
“dataTypeId”: 32
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 65507,
“dataTypeId”: 66
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
}
},
“bindings”: {
“time”: {
“attributes”: [
{
“acl”: [
“readable”
],
“id”: 65533,
“dataTypeId”: 33,
“name”: “clusterRevision”,
“value”: 1
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“ota”: {}
}
}
}
}

The device is already integrated into Zigbee2MQTT as “TS0601_bed_presence_sensor”. I found a GitHub Issue containing the exact custom External Converter script where all Tuya Data Points (DPs) are fully mapped and explained:

Tuya TS0601_bed_presence_sensor control via MQTT | Zigbee2MQTT

[External Converter]: Zigbee Pressure Pad/Bed Occupancy Sensor

There is also a Hubitat driver available here:

https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya%20Contact%20Sensor/Tuya%20Contact%20Sensor.groovy

It would be awesome if you could add this to the test/beta version of the Tuya Zigbee app.

Thank you so much for your support!

[Rudi_Hendrix]

Today I wanted to add my Tuya 2 Gang Switch Module with metering. It has been connected before, but lost connection.

While trying to connect, I wasn’t able to doe so. So, what I did: set it to pairing mode, started adding the device in Homey in the Tuya Zigbee app. It had the spinning wheel kind of thing indicating it found the device and was tyring to add it. Then I received an error.

Question: does it have to be in direct contact with the Homey Pro? Or can you also add a device through other Zigbee network devices (if powered)?

[smarthomesven]

AFAIK you can pair through router devices as well, I’ve never had issues with pairing Zigbee devices on the other side of the house at least.

[Rudi_Hendrix]

Thanks! In that case something different is happening. It’s not a big issue as I have a Z-Wave switch module in place that does the actual switching. This one is just for power metering

[SunBeech]

@Rudi_Hendrix

It had the spinning wheel kind of thing indicating it found the device and was tyring to add it. Then I received an error.

You could try toggling the switch on/off every few seconds during the pairing procedure. Like keeping a battery powered device active.

My experience is that this sometimes also helps for pairing mains powered devices, that take a long time to pair.

[Rudi_Hendrix]

So, while it is blinking? Will try!

[SunBeech]

@Rudi_Hendrix

while it is blinking?

Yes, indeed .

[Remco_Ter_haar]

hey johan

can you also add this soil sensor

“ids”: {
“modelId”: “TS0601”,
“manufacturerName”: “_TZE284_myd45weu”
},
“endpoints”: {
“ieeeAddress”: “a4:c1:38:c9:a1:3f:38:97”,
“networkAddress”: 36789,
“modelId”: “TS0601”,
“manufacturerName”: “_TZE284_myd45weu”,
“endpointDescriptors”: [
{
“status”: “SUCCESS”,
“nwkAddrOfInterest”: 36789,
“_reserved”: 22,
“endpointId”: 1,
“applicationProfileId”: 260,
“applicationDeviceId”: 81,
“applicationDeviceVersion”: 0,
“_reserved1”: 1,
“inputClusters”: [
4,
5,
61184,
0,
60672
],
“outputClusters”: [
25,
10
]
}
],
“deviceType”: “enddevice”,
“receiveWhenIdle”: false,
“capabilities”: {
“alternatePANCoordinator”: false,
“deviceType”: false,
“powerSourceMains”: false,
“receiveWhenIdle”: false,
“security”: false,
“allocateAddress”: true
},
“extendedEndpointDescriptors”: {
“1”: {
“clusters”: {
“groups”: {
“attributes”: [
{
“acl”: [
“readable”,
“reportable”
],
“id”: 0,
“dataTypeId”: 24,
“name”: “nameSupport”,
“value”: {
“type”: “Buffer”,
“data”: [
0
]
},
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 65533,
“dataTypeId”: 33,
“name”: “clusterRevision”,
“value”: 2,
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
}
]
},
“scenes”: {
“attributes”: [
{
“acl”: [
“readable”,
“reportable”
],
“id”: 0,
“dataTypeId”: 32,
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 1,
“dataTypeId”: 32,
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 2,
“dataTypeId”: 33,
“rapportageconfiguratie”: {
“status”: “NIET GEVONDEN”,
“richting”: “gerapporteerd”
}
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 3,
“dataTypeId”: 16,
“rapportageconfiguratie”: {
“status”: “NIET GEVONDEN”,
“richting”: “gerapporteerd”
}
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 4,
“dataTypeId”: 24,
“rapportageconfiguratie”: {
“status”: “NIET GEVONDEN”,
“richting”: “gerapporteerd”
}
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 65533,
“dataTypeId”: 33,
“name”: “clusterRevision”,
“value”: 2,
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
}
]
},
“basic”: {
“attributes”: [
{
“acl”: [
“readable”,
“reportable”
],
“id”: 0,
“dataTypeId”: 32,
“name”: “zclVersion”,
“value”: 3
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 1,
“dataTypeId”: 32,
“name”: “appVersion”,
“value”: 80
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 2,
“dataTypeId”: 32,
“name”: “stackVersion”,
“value”: 0
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 3,
“dataTypeId”: 32,
“naam”: “hwVersion”,
“waarde”: 1
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 4,
“dataTypeId”: 66,
“naam”: “fabrikantnaam”,
“waarde”: “_TZE284_myd45weu”
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 5,
“dataTypeId”: 66,
“naam”: “modelId”,
“waarde”: “TS0601”
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 6,
“dataTypeId”: 66,
“naam”: “datumcode”,
“waarde”: “”
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 7,
“dataTypeId”: 48,
“naam”: “powerSource”,
“waarde”: “batterij”
},
{
“acl”: [
“leesbaar”,
“schrijfbaar”,
“rapporteerbaar”
],
“id”: 65502,
“dataTypeId”: 32
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 65533,
“dataTypeId”: 33,
“naam”: “clusterRevision”,
“waarde”: 2
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 65534,
“dataTypeId”: 48,
“naam”: “attributeReportingStatus”,
“waarde”: “IN AFWACHTING”
},
{
“acl”: [
“leesbaar”,
“reportable”
],
“id”: 65506,
“dataTypeId”: 32
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 65507,
“dataTypeId”: 72
},
{
“acl”: [
“readable”,
“writable”,
“reportable”
],
“id”: 65487,
“dataTypeId”: 33
}
]
}
},
“bindings”: {
“ota”: {},
“time”: {
“attributes”: [
{
“acl”: [
“readable”
],
“id”: 65533,
“dataTypeId”: 33,
“name”: “clusterRevision”,
“value”: 1
}
]
}
}
}
}
}

Hoi Johan

kun je deze bodemsensor toevoegen

“ids”: {
“modelId”: “TS0601”,
“manufacturerName”: “_TZE284_myd45weu”
},
“endpoints”: {
“ieeeAddress”: “a4:c1:38:c9:a1:3f:38:97”,
“networkAddress”: 36789,
“modelId”: “TS0601”,
“manufacturerName”: “_TZE284_myd45weu”,
“endpointDescriptors”: [
{
“status”: “SUCCESS”,
“nwkAddrOfInterest”: 36789,
“_reserved”: 22,
“endpointId”: 1,
“applicationProfileId”: 260,
“applicationDeviceId”: 81,
“applicationDeviceVersion”: 0,
“_reserved1”: 1,
“inputClusters”: [
4,
5,
61184,
0,
60672
],
“outputClusters”: [
25,
10
]
}
],
“deviceType”: “enddevice”,
“receiveWhenIdle”: false,
“capabilities”: {
“alternatePANCoordinator”: false,
“deviceType”: false,
“powerSourceMains”: false,
“receiveWhenIdle”: false,
“security”: false,
“allocateAddress”: true
},
“extendedEndpointDescriptors”: {
“1”: {
“clusters”: {
“groups”: {
“attributes”: [
{
“acl”: [
“readable”,
“reportable”
],
“id”: 0,
“dataTypeId”: 24,
“name”: “nameSupport”,
“value”: {
“type”: “Buffer”,
“data”: [
0
]
},
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 65533,
“dataTypeId”: 33,
“name”: “clusterRevision”,
“value”: 2,
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
}
]
},
“scenes”: {
“attributes”: [
{
“acl”: [
“readable”,
“reportable”
],
“id”: 0,
“dataTypeId”: 32,
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 1,
“dataTypeId”: 32,
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 2,
“dataTypeId”: 33,
“rapportageconfiguratie”: {
“status”: “NIET GEVONDEN”,
“richting”: “gerapporteerd”
}
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 3,
“dataTypeId”: 16,
“rapportageconfiguratie”: {
“status”: “NIET GEVONDEN”,
“richting”: “gerapporteerd”
}
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 4,
“dataTypeId”: 24,
“rapportageconfiguratie”: {
“status”: “NIET GEVONDEN”,
“richting”: “gerapporteerd”
}
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 65533,
“dataTypeId”: 33,
“name”: “clusterRevision”,
“value”: 2,
“reportingConfiguration”: {
“status”: “NOT_FOUND”,
“direction”: “reported”
}
}
]
},
“basic”: {
“attributes”: [
{
“acl”: [
“readable”,
“reportable”
],
“id”: 0,
“dataTypeId”: 32,
“name”: “zclVersion”,
“value”: 3
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 1,
“dataTypeId”: 32,
“name”: “appVersion”,
“value”: 80
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 2,
“dataTypeId”: 32,
“name”: “stackVersion”,
“value”: 0
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 3,
“dataTypeId”: 32,
“naam”: “hwVersion”,
“waarde”: 1
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 4,
“dataTypeId”: 66,
“naam”: “fabrikantnaam”,
“waarde”: “_TZE284_myd45weu”
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 5,
“dataTypeId”: 66,
“naam”: “modelId”,
“waarde”: “TS0601”
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 6,
“dataTypeId”: 66,
“naam”: “datumcode”,
“waarde”: “”
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 7,
“dataTypeId”: 48,
“naam”: “powerSource”,
“waarde”: “batterij”
},
{
“acl”: [
“leesbaar”,
“schrijfbaar”,
“rapporteerbaar”
],
“id”: 65502,
“dataTypeId”: 32
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 65533,
“dataTypeId”: 33,
“naam”: “clusterRevision”,
“waarde”: 2
},
{
“acl”: [
“leesbaar”,
“rapporteerbaar”
],
“id”: 65534,
“dataTypeId”: 48,
“naam”: “attributeReportingStatus”,
“waarde”: “IN AFWACHTING”
},
{
“acl”: [
“leesbaar”,
“reportable”
],
“id”: 65506,
“dataTypeId”: 32
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 65507,
“dataTypeId”: 72
},
{
“acl”: [
“readable”,
“writable”,
“reportable”
],
“id”: 65487,
“dataTypeId”: 33
}
]
}
},
“bindings”: {
“ota”: {},
“time”: {
“attributes”: [
{
“acl”: [
“readable”
],
“id”: 65533,
“dataTypeId”: 33,
“name”: “clusterRevision”,
“value”: 1
}
]
}
}
}
}
}

[SunBeech]

FYI

[APP][Pro] Universal TUYA Zigbee Device App - test

To all those posting interview results in this topic, please consider using the following to increase readability of your post: Preformatted text option to keep the output in the original format and presented in a scrollable window. This reduces the length of your post. Hide details option, to collapse/hide the entire interview output. Clicking the collapsed item will show the interview output again. [IMG_2409]

[late4marshmellow]

Even though that is indeed a better way to post interviews, they should be directed to Github

@johan_bendz

PROCESS FOR REQUESTING DEVICES TO BE ADDED
If your device is not supported by the app it will have to be added by adding code to the app, this is done by me or by someone helping me out (anyone can - it’s open source ).

To be able to add more devices I will need help with interviews of the devices you want added. Anyone asking for a device to be added will have to have:

• upgraded to firmware v5
• have a physical example of the device
• add it as a generic Zigbee device
• go to https://developer.athom.com/tools/zigbee and interview the device
• copy the info (by clicking the copy button/icon!) and post it as a new issue at the apps Github repository(</>).

Github: GitHub - JohanBendz/com.tuya.zigbee · GitHub

---

I request that all device requests be directed to Github. The reason is straightforward: previously, when requests were made in this thread, I had to manually create an issue on Github, transfer the information, fill in any missing details, and then schedule the device to be added. Additionally, many requests were either duplicates or inquiries about the status of an existing request.

I hope that creating a Github account (which is free and straightforward) isn’t too much to ask. Doing so will significantly streamline my process for handling requests and follow-ups. I believe this approach will also encourage more individuals to contribute code.

Old requests made in this thread can be found here:
https://community.homey.app/t/app-pro-tuya-zigbee-app-device-request-archive/

You are, and will always be, more than welcome to discuss the app, report problems, seek support, share ideas, and more in this thread. All I ask is that device requests be made on Github

[John_Kijk_in_de_Vegt]

I want to add a “onomwonden zigbee doorsensor” . This code comes with this equipment:“ids”: {
“modelId”: “TS0203”,
“manufacturerName”: “_TZ3000_996rpfy6”
},
“endpoints”: {
“endpointDescriptors”: [
{
“endpointId”: 1,
“applicationProfileId”: 260,
“applicationDeviceId”: 1026,
“applicationDeviceVersion”: 0,
“_reserved1”: 1,
“inputClusters”: [
3,
1,
1280,
0
],
“outputClusters”: [
3,
25,
10
]
}
],
“endpoints”: {
“1”: {
“clusters”: {
“identify”: {
“attributes”:
},
“powerConfiguration”: {},
“iasZone”: {},
“basic”: {}
},
“bindings”: {
“identify”: {
“attributes”:
},
“ota”: {},
“time”: {}
}
}
}
}

Can this be updates?

[robertklep]

This is an English thread. Also read the first post!

[Michael_Hadjicosta]

Hello @johan_bendz, I am reaching out for assistance with the Zemismart ZN-LRL1E Water Boiler Switch (30A). Currently, the device is not functioning correctly within Homey, as I am unable to see or use an on/off button. Only as generic Zigbee device.

I have attached a screenshot of the device, and have listed the key details below for your reference:

• Device Name: generic-ef00-v1

• Model: TS0601

• Manufacturer Code: _TZE28C100000_rzdkn5rx

• Device ID: 2fec90f0-fcf2-47c7-af39-ffce49127b84

• Device Profile: zemismart-tuya-switch

Please let me know if any further logs or information are required to help resolve this issue

[PetervdK]

Did you read the first post of this topic?

[Rudi_Hendrix]

I think no one ever does…

[PetervdK]

Strange. I always start reading at the beginning, not at the end…