# \[APP\]\[Pro\] Tuya Zigbee App

**URL:** <https://community.homey.app/t/app-pro-tuya-zigbee-app/26439>\
**Category:** Apps\
**Created:** [February 26, 2020, 9:12am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439 "2020-02-26T09:12:23Z")\
**Posts on this page:** 20\
**Page:** 59

<div class="post-metadata">

**Author:** ![Rudi\_Hendrix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rudi_hendrix/32/31931_2.png) [@Rudi\_Hendrix](https://community.homey.app/u/Rudi_Hendrix)\
**Post date:** [May 19, 2026, 5:04pm UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5471 "2026-05-19T17:04:57Z")

</div>

Let’s stick to English.

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

---

<div class="post-metadata">

**Author:** ![DaPicard](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dapicard/32/163023_2.png) [@DaPicard](https://community.homey.app/u/DaPicard)\
**Post date:** [May 20, 2026, 6:54pm UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5472 "2026-05-20T18:54:17Z")

</div>

**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**

```auto
> "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](https://www.zigbee2mqtt.io/devices/TS0601_bed_presence_sensor.html)**
>
> Integrate your Tuya TS0601\_bed\_presence\_sensor via Zigbee2MQTT with whatever smart home infrastructure you are using without the vendor's bridge or gateway.

> <https://github.com/Koenkk/zigbee2mqtt/issues/31079>
>
> \### Link
> 
> https://www.aliexpress.com/item/1005010633396757.html
> 
> \### Database en…try
> 
> {"id":147,"type":"EndDevice","ieeeAddr":"0xa4c1380cce82ad5e","nwkAddr":57656,"manufId":4417,"manufName":"\_TZE200\_seq9cm6u","powerSource":"Battery","model\>
> 
> \### Zigbee2MQTT version
> 
> 2.7.2 commit: unknown
> 
> \### External converter
> 
> \`\`\`JavaScript
> import \* as exposes from 'zigbee-herdsman-converters/lib/exposes';
> import \* as tuya from 'zigbee-herdsman-converters/lib/tuya';
> 
> const e = exposes.presets;
> const ea = exposes.access;
> 
> // Writable inputs (Tuya schema: DP9, DP101, DP102, DP103 are rw)
> const tzLocal = {
> pir\_sensitivity: {
> key: \['pir\_sensitivity'\],
> convertSet: async (entity, key, value, meta) =\> {
> const map = {low: 0, middle: 1, high: 2};
> if (typeof value !== 'string' || !(value in map)) {
> throw new Error(\`pir\_sensitivity must be one of: low|middle|high\`);
> }
> await tuya.sendDataPointEnum(entity, 9, map\[value\]);
> return {state: {pir\_sensitivity: value}};
> },
> // rely on reporting instead of polling
> convertGet: async () =\> ({}),
> },
> 
> interval\_time: {
> key: \['interval\_time'\],
> convertSet: async (entity, key, value, meta) =\> {
> const v = Number(value);
> if (!Number.isFinite(v)) throw new Error(\`interval\_time must be a number (minutes)\`);
> await tuya.sendDataPointValue(entity, 101, v);
> return {state: {interval\_time: v}};
> },
> convertGet: async () =\> ({}),
> },
> 
> pir\_delay: {
> key: \['pir\_delay'\],
> convertSet: async (entity, key, value, meta) =\> {
> const v = Number(value);
> if (!Number.isFinite(v)) throw new Error(\`pir\_delay must be a number (seconds)\`);
> await tuya.sendDataPointValue(entity, 102, v);
> return {state: {pir\_delay: v}};
> },
> convertGet: async () =\> ({}),
> },
> 
> presence\_time: {
> key: \['presence\_time'\],
> convertSet: async (entity, key, value, meta) =\> {
> const v = Number(value);
> if (!Number.isFinite(v)) throw new Error(\`presence\_time must be a number (seconds)\`);
> await tuya.sendDataPointValue(entity, 103, v);
> return {state: {presence\_time: v}};
> },
> convertGet: async () =\> ({}),
> },
> };
> 
> export default {
> fingerprint: \[
> {modelID: 'TS0601', manufacturerName: '\_TZE200\_seq9cm6u'},
> \],
> model: 'TS0601\_bed\_presence\_sensor',
> vendor: 'Tuya',
> description: 'Bed presence / pressure sensor (Tuya PIR template)',
> 
> fromZigbee: \[tuya.fz.datapoints\],
> toZigbee: \[
> tzLocal.pir\_sensitivity,
> tzLocal.interval\_time,
> tzLocal.pir\_delay,
> tzLocal.presence\_time,
> \],
> 
> exposes: \[
> // DP1 (Tuya code: pir\_state). This device uses it as bed occupancy.
> e.occupancy(),
> 
> // DP4 battery\_percentage
> e.battery(),
> 
> // DP12 Tuya uses lux (illuminance) but it is actually the pressure.
> exposes.numeric('illuminance', ea.STATE)
> .withUnit('lux')
> .withDescription('Pressure'),
> 
> // DP9 pir\_sensitivity (rw). Expose as enum strings; Setting is supported.
> exposes.enum('pir\_sensitivity', ea.ALL, \['low', 'middle', 'high'\])
> .withDescription('Sensitivity (rw)'),
> 
> // DP101 interval\_time (rw, minutes)
> exposes.numeric('interval\_time', ea.ALL).withUnit('min')
> .withDescription('Sampling interval (rw)'),
> 
> // DP102 pir\_delay (rw, seconds)
> exposes.numeric('pir\_delay', ea.ALL).withUnit('s')
> .withDescription('Delay to report no presence (rw)'),
> 
> // DP103 presence\_time (rw, seconds)
> exposes.numeric('presence\_time', ea.ALL).withUnit('s')
> .withDescription('Delay to report presence (rw)'),
> 
> // DP104 work\_state (ro). Expose numeric with meaning in description to avoid enum conversion issues.
> exposes.numeric('work\_state', ea.STATE)
> .withDescription('0=pir,1=none,2=pir\_5min,3=pir\_30min,4=none\_5min,5=none\_30min (ro)'),
> \],
> 
> meta: {
> tuyaDatapoints: \[
> // DP1: 0/1 observed inverted; trueFalse0 means 0=\>true, 1=\>false
> \[1, 'occupancy', tuya.valueConverter.trueFalse0\],
> 
> // DP4: battery %
> \[4, 'battery', tuya.valueConverter.raw\],
> 
> // DP9: sensitivity as numeric 0/1/2 from device reports
> // The meaning is similar to above as exposed high, med, low
> \[9, 'pir\_sensitivity', tuya.valueConverter.raw\],
> 
> // DP12: “illuminance\_value” (reported as lux) but used as pressure
> \[12, 'illuminance', tuya.valueConverter.raw\],
> 
> // DP101/102/103 numeric values
> \[101, 'interval\_time', tuya.valueConverter.raw\],
> \[102, 'pir\_delay', tuya.valueConverter.raw\],
> \[103, 'presence\_time', tuya.valueConverter.raw\],
> 
> // DP104: work\_state numeric 0..5
> \[104, 'work\_state', tuya.valueConverter.raw\],
> \],
> },
> };
> 
> \`\`\`
> 
> \### What does/doesn't work with the external definition?
> 
> This custom external definition appears to work fully but note the differences between reported type vs actual type (lux vs pressure)
> 
> \### Notes
> The device auto calibrates its "base" value on power up. So you can put it under the mattress then put the batteries in and internally gets that as a threshold
> \<img width="1024" height="1024" alt="Image" src="https://github.com/user-attachments/assets/69eff14e-fa21-453c-b554-0c792b5c4e95" /\>
> 
> Image that can be used for the product icon

There is also a Hubitat driver available here:

[https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya%20Contact%20Sensor/Tuya%20Contact%20Sensor.groovy](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!**

---

<div class="post-metadata">

**Author:** ![Rudi\_Hendrix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rudi_hendrix/32/31931_2.png) [@Rudi\_Hendrix](https://community.homey.app/u/Rudi_Hendrix)\
**Post date:** [May 25, 2026, 8:05pm UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5473 "2026-05-25T20:05:33Z")

</div>

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)?

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [May 26, 2026, 1:18am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5474 "2026-05-26T01:18:42Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Rudi\_Hendrix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rudi_hendrix/32/31931_2.png) [@Rudi\_Hendrix](https://community.homey.app/u/Rudi_Hendrix)\
**Post date:** [May 26, 2026, 5:00am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5475 "2026-05-26T05:00:17Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [May 26, 2026, 5:43am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5476 "2026-05-26T05:43:28Z")

</div>

> [@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.

---

<div class="post-metadata">

**Author:** ![Rudi\_Hendrix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rudi_hendrix/32/31931_2.png) [@Rudi\_Hendrix](https://community.homey.app/u/Rudi_Hendrix)\
**Post date:** [May 26, 2026, 6:30am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5477 "2026-05-26T06:30:32Z")

</div>

So, while it is blinking? Will try!

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [May 26, 2026, 7:11am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5478 "2026-05-26T07:11:50Z")

</div>

> [@Rudi\_Hendrix](#):
>
> while it is blinking?

Yes, indeed 😀.

---

<div class="post-metadata">

**Author:** ![Remco\_Ter\_haar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/remco_ter_haar/32/121237_2.png) [@Remco\_Ter\_haar](https://community.homey.app/u/Remco_Ter_haar)\
**Post date:** [May 26, 2026, 11:31am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5479 "2026-05-26T11:31:58Z")

</div>

hey johan

can you also add this soil sensor

```auto
"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
}
\]
}
}
}
}
}

```

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [May 26, 2026, 12:38pm UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5480 "2026-05-26T12:38:26Z")

</div>

FYI

> [@\[APP\]\[Pro\] Universal TUYA Zigbee Device App - test](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/954):
>
> 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.

---

<div class="post-metadata">

**Author:** ![late4marshmellow](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/late4marshmellow/32/163476_2.png) [@late4marshmellow](https://community.homey.app/u/late4marshmellow)\
**Post date:** [May 28, 2026, 7:36am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5481 "2026-05-28T07:36:15Z")

</div>

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](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](https://github.com/JohanBendz/com.tuya.zigbee/issues/new/choose) at the apps Github repository(\</\>).
> 
> Github: [GitHub - JohanBendz/com.tuya.zigbee · GitHub](https://github.com/JohanBendz/com.tuya.zigbee)
> 
> * * *
> 
> 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/](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](https://github.com/JohanBendz/com.tuya.zigbee/issues/new/choose)

---

<div class="post-metadata">

**Author:** ![John\_Kijk\_in\_de\_Vegt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_kijk_in_de_vegt/32/78869_2.png) [@John\_Kijk\_in\_de\_Vegt](https://community.homey.app/u/John_Kijk_in_de_Vegt)\
**Post date:** [June 21, 2026, 10:05am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5482 "2026-06-21T10:05:18Z")

</div>

I want to add a “onomwonden zigbee doorsensor” . This code comes with this equipment:

```auto
"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?

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [June 21, 2026, 10:06am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5483 "2026-06-21T10:06:14Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Michael\_Hadjicosta](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_hadjicosta/32/121194_2.png) [@Michael\_Hadjicosta](https://community.homey.app/u/Michael_Hadjicosta)\
**Post date:** [June 29, 2026, 3:47am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5484 "2026-06-29T03:47:17Z")

</div>

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

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/7/177142965c8840160f27444de917cbdb665b04dd.jpeg)

---

<div class="post-metadata">

**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\
**Post date:** [June 30, 2026, 4:51am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5485 "2026-06-30T04:51:05Z")

</div>

Did you read the first post of this topic?

---

<div class="post-metadata">

**Author:** ![Rudi\_Hendrix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rudi_hendrix/32/31931_2.png) [@Rudi\_Hendrix](https://community.homey.app/u/Rudi_Hendrix)\
**Post date:** [June 30, 2026, 5:15am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5486 "2026-06-30T05:15:24Z")

</div>

I think no one ever does…

---

<div class="post-metadata">

**Author:** ![PetervdK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/petervdk/32/20669_2.png) [@PetervdK](https://community.homey.app/u/PetervdK)\
**Post date:** [June 30, 2026, 5:50pm UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5487 "2026-06-30T17:50:44Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Sergio\_B](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sergio_b/32/170593_2.png) [@Sergio\_B](https://community.homey.app/u/Sergio_B)\
**Post date:** [July 29, 2026, 4:52am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5488 "2026-07-29T04:52:18Z")

</div>

Hi @johan_bendz Please add support for this smart button switch:

Manufacturer name: Hobeian

Model ID: ZG-101ZL

Device type: enddevice

Thank you

---

<div class="post-metadata">

**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\
**Post date:** [July 29, 2026, 5:42am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5489 "2026-07-29T05:42:06Z")

</div>

Please check the first post in this topic on how to request support for devices.

---

<div class="post-metadata">

**Author:** ![Rudi\_Hendrix](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rudi_hendrix/32/31931_2.png) [@Rudi\_Hendrix](https://community.homey.app/u/Rudi_Hendrix)\
**Post date:** [July 29, 2026, 6:42am UTC](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439/5490 "2026-07-29T06:42:39Z")

</div>

Perhaps Athom can build this in as a default response to a reply to this topic 😬

[Previous page](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439.md?page=58)

[Next page](https://community.homey.app/t/app-pro-tuya-zigbee-app/26439.md?page=60)