[APP][Pro] Tuya Zigbee App

Rudi_Hendrix · May 19, 2026, 5:04pm

Let’s stick to English.

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

DaPicard · May 20, 2026, 6:54pm

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:

github.com/Koenkk/zigbee2mqtt

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

offen 10:45AM - 16 Feb 26 UTC

geschlossen 07:35PM - 24 Feb 26 UTC

shopsD

external converter

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

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 · May 25, 2026, 8:05pm

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 · May 26, 2026, 1:18am

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 · May 26, 2026, 5:00am

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 · May 26, 2026, 5:43am

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 · May 26, 2026, 6:30am

So, while it is blinking? Will try!

SunBeech · May 26, 2026, 7:11am

Yes, indeed .

Remco_Ter_haar · May 26, 2026, 11:31am

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 · May 26, 2026, 12:38pm

FYI

late4marshmellow · May 28, 2026, 7:36am

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

Topic		Replies	Views
[APP][Pro] Universal TUYA Zigbee Device App - test Apps app , zigbee	1979	19791	May 30, 2026
[APP] Tuya - Connect any Tuya device with Homey (by Tuya Inc. / Athom) Apps app	1113	45207	February 5, 2026
[APP] Tuya - Smart Life. Smart Living Apps official , homey	231	5165	May 29, 2026
[APP][Pro] Tuya Cloud - This app allows you to connect Homey to the Tuya cloud Apps app , unofficial , wifi , homey-pro	2708	185074	May 17, 2026
[APP][Pro] TuyAPI / Neo Coolcam wall plug WIFI app Apps app , wifi , homey-pro	335	31731	March 2, 2026

[APP][Pro] Tuya Zigbee App

Related topics