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

**URL:** <https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352>\
**Category:** Apps\
**Tags:** app, zigbee\
**Created:** [July 25, 2025, 1:07am UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352 "2025-07-25T01:07:08Z")\
**Posts on this page:** 20\
**Page:** 107

<div class="post-metadata">

**Author:** ![Cam](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cam/32/135693_2.png) [@Cam](https://community.homey.app/u/Cam)\
**Post date:** [August 31, 2026, 4:47am UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2209 "2026-08-31T04:47:54Z")

</div>

Hi there @dlnraja

Just checking in after a few months of devices not working and trying to add them again. My [smart button](https://github.com/JohanBendz/com.tuya.zigbee/issues/1268) and [motion sensor](https://github.com/JohanBendz/com.tuya.zigbee/issues/1267) aren’t detecting/passing through any data through my flows.

I know the motion sensors are working because I can see the red light flash when movement occurs near it but they just don’t respond to flows, regardless of how many ways I try (same for button too).

I’ve also tried adding them as several different devices to see if that helps, sadly it does not. You had them working once upon a time but I suspect one the updates along the way boned them again.

Thanks for your time.  
Cam

---

<div class="post-metadata">

**Author:** ![dlnraja](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dlnraja/32/129224_2.png) [@dlnraja](https://community.homey.app/u/dlnraja)\
**Post date:** [August 31, 2026, 6:02am UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2210 "2026-08-31T06:02:52Z")

</div>

| User | Action |
| --- | --- |
| meter91 | Update ≥9.0.738 → remove → re-pair Scene Switch 4-Gang |
| VicHY | Update Test → re-pair Presence Sensor Radar (`clrdrnya`) |
| Cam | Update → re-pair motion on Presence Sensor Radar; send button diag if flows still dead |

---

<div class="post-metadata">

**Author:** ![VicHY](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vichy/32/143896_2.png) [@VicHY](https://community.homey.app/u/VicHY)\
**Post date:** [August 31, 2026, 7:35am UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2211 "2026-08-31T07:35:40Z")

</div>

> [@dlnraja](#):
>
> User Action meter91 Update ≥9.0.738 → remove → re-pair Scene Switch 4-Gang VicHY Update Test → re-pair Presence Sensor Radar (`clrdrnya`) Cam Update → re-pair motion on Presence Sensor Radar; send button diag if flows still dead

Thanks, I´ll try it this afternoon.  
I’ll edit this to say if it works or if it still detects it the same way.

---

<div class="post-metadata">

**Author:** ![dlnraja](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dlnraja/32/129224_2.png) [@dlnraja](https://community.homey.app/u/dlnraja)\
**Post date:** [August 31, 2026, 9:39am UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2212 "2026-08-31T09:39:32Z")

</div>

Please for peoples who has issues with their devices , to remove repair et retest it with the latest app update.

Please give me diags logs and interviews at each request.

Best regards.

---

<div class="post-metadata">

**Author:** ![meter91](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/meter91/32/172271_2.png) [@meter91](https://community.homey.app/u/meter91)\
**Post date:** [August 31, 2026, 10:04am UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2213 "2026-08-31T10:04:11Z")

</div>

switch still comes on as unknown device driver missing. Interview is timing out

Diagnostic report ID: 2b0b4e4f-971e-4e1f-8d32-09d255e232d0

Device State:

**{**

“availability”:

undefined

,

“zigbee\_error”:

undefined

,

“zigbee\_ready”:

booltrue

,

“zigbee\_state”: **{**

“currentCommand”:

string"IDLE"

**}** ,

_1 item_

“controllerState”: **{**

“channel”:

int11

,

“panId”:

string"3F3D"

,

“extPanId”:

string""

,

“ieeeAddr”:

string""

,

“extendedPanId”:

string"c7:09:c9:7a:32:a8:8e:e8"

,

“IEEEAddress”:

string"00:12:4b:00:1b:44:e9:73"

,

“networkKey”:

xxx

,

“currentCommand”:

string"IDLE"

,

“softwareVersion”:

string"2.6.3-20231124"

,

“routes”: **{}** ,

_0 items_

“networkAddress”:

string"0"

**}** ,

_11 items_

“nodes”: **{**

“a4:c1:38:8d:83:d2:25:34”: **{**

“type”:

string"EndDevice"

,

“name”:

string"Onbekend Zigbee Apparaat"

,

“parent”:

int0

,

“nwkAddr”:

int55960

,

“modelId”:

string"TS0044"

,

“receiveWhenIdle”:

boolfalse

,

“manufacturerName”:

string"\_TZ3000\_zgyzgdua"

**}**

_7 items_

**}**

_1 item_

**}**

_6 items_

---

<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:** [August 31, 2026, 10:07am UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2214 "2026-08-31T10:07:26Z")

</div>

> [@meter91](#):
>
> “networkKey”:
> 
> string

I would recommend to remove the network key from your post, AFAIK this can be used to access your Zigbee network.

---

<div class="post-metadata">

**Author:** ![meter91](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/meter91/32/172271_2.png) [@meter91](https://community.homey.app/u/meter91)\
**Post date:** [August 31, 2026, 10:24am UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2215 "2026-08-31T10:24:07Z")

</div>

thanks!

---

<div class="post-metadata">

**Author:** ![VicHY](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vichy/32/143896_2.png) [@VicHY](https://community.homey.app/u/VicHY)\
**Post date:** [August 31, 2026, 2:15pm UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2216 "2026-08-31T14:15:53Z")

</div>

What type of device is it? I’ve searched for “PIR mmWave,” but it still recognizes it as generic.

Thanks a lot.

---

<div class="post-metadata">

**Author:** ![VicHY](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vichy/32/143896_2.png) [@VicHY](https://community.homey.app/u/VicHY)\
**Post date:** [August 31, 2026, 2:52pm UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2217 "2026-08-31T14:52:34Z")

</div>

Thanks i clear de app and reinstall and the sensor was detected.

I think that have all the options

Thanks!

---

<div class="post-metadata">

**Author:** ![Joep\_Vullings](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joep_vullings/32/9293_2.png) [@Joep\_Vullings](https://community.homey.app/u/Joep_Vullings)\
**Post date:** [August 31, 2026, 8:00pm UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2218 "2026-08-31T20:00:28Z")

</div>

I tried to repair my two way Irrigation Valve, but it wasn’t recognized. It paired as unknown Zigbee device. Could you look into it?

---

<div class="post-metadata">

**Author:** ![VicHY](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vichy/32/143896_2.png) [@VicHY](https://community.homey.app/u/VicHY)\
**Post date:** [September 1, 2026, 2:04pm UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2219 "2026-09-01T14:04:00Z")

</div>

```auto
Following today's update, the sensor recognizes more data, but its type has changed to "curtain," and a button for adjusting the opening range appears instead of a simple on/off switch. Also, the sensors seem to be performing worse; they keep detecting presence even when there isn't any.
What could be happening?
Thanks.

```

---

<div class="post-metadata">

**Author:** ![Peter\_van\_Werkhoven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_van_werkhoven/32/101322_2.png) [@Peter\_van\_Werkhoven](https://community.homey.app/u/Peter_van_Werkhoven)\
**Post date:** [September 1, 2026, 4:43pm UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2220 "2026-09-01T16:43:47Z")

</div>

Hi Dylan Good evening, I deleted the Smartbutton again and restarted Homey, re-added the Smartbutton again but still no response from it.

 ![1000045748](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/d/6d3ff38b1399628bec9fc8a77bcfb8e64da7b66c.jpeg)  
 ![1000045749](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/4/54272ca947341ab8c30f86ee4419aeec57777699.jpeg)

Diagnostic code cfbf687f-fcce-4cbe-b5ea-d7d245e6eee6

The Waterdetector sensor is fine now, no more errors that it needs another driver. 👍🏻

Good luck and thanks again and have a nice evening.  
Regards Peter.

---

<div class="post-metadata">

**Author:** ![PresentSky](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/presentsky/32/167962_2.png) [@PresentSky](https://community.homey.app/u/PresentSky)\
**Post date:** [September 1, 2026, 8:11pm UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2221 "2026-09-01T20:11:28Z")

</div>

Hi @dlnraja ,

Could you please check this as well? Updated diagnostic ID and interview data have been provided.

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![VicHY](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vichy/32/143896_2.png) [@VicHY](https://community.homey.app/u/VicHY)\
**Post date:** [September 2, 2026, 10:54am UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2222 "2026-09-02T10:54:34Z")

</div>

Hi @dlnraja  
I’ve noticed that if I delete the presence sensor and reconnect it, it works fine, but after a while (it seems to coincide roughly with updates), it switches to “blind mode” and goes haywire, continuously detecting presence and movement.  
Do you know what might be causing this?  
I’m also getting this notification on the timeline for both sensors (I have two installed in different rooms).

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/f/4f5cf0c71ada2024da9e5922c03c0e928dc6853e.jpeg)

Thanks!

---

<div class="post-metadata">

**Author:** ![dlnraja](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dlnraja/32/129224_2.png) [@dlnraja](https://community.homey.app/u/dlnraja)\
**Post date:** [September 2, 2026, 11:26am UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2223 "2026-09-02T11:26:12Z")

</div>

> [@VicHY](#):
>
> Hi @dlnraja  
> I’ve noticed that if I delete the presence sensor and reconnect it, it works fine, but after a while (it seems to coincide roughly with updates), it switches to “blind mode” and goes haywire, continuously detecting presence and movement.  
> Do you know what might be causing this?  
> I’m also getting this notification on the timeline for both sensors (I have two installed in different rooms).

please share :

1. **The exact Manufacturer ID & Model ID** from Developer Tools (Zigbee tab).
2. **What the timeline notification says verbatim** (e.g., what capability or warning it shows).
3. **An app diagnostic log:** Go to **More \> Apps \> Universal Tuya Zigbee \> Settings (Gear icon) \> Send Diagnostic Report** and post the report code so the exact DP cluster dump can be inspected.

---

<div class="post-metadata">

**Author:** ![VicHY](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vichy/32/143896_2.png) [@VicHY](https://community.homey.app/u/VicHY)\
**Post date:** [September 2, 2026, 12:47pm UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2224 "2026-09-02T12:47:18Z")

</div>

1. Manufacter ID: \_TZE204\_clrdrnya  
Model ID: TS0601

2. This is the timeline in spanish. Update-\>low baterry-\>Flood zigbee netwrk-\> Low batery

3. Report Code: 0e28d470-c67e-4876-9d19-75f816abc7bb

Sorry for my english..

Thanks!

---

<div class="post-metadata">

**Author:** ![dlnraja](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dlnraja/32/129224_2.png) [@dlnraja](https://community.homey.app/u/dlnraja)\
**Post date:** [September 2, 2026, 1:52pm UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2225 "2026-09-02T13:52:27Z")

</div>

Hi VicHY — thanks for the detailed report, that helped a lot.

I found the cause on the clrdrnya mmWave radars. After an app update, some radar setting DPs (sensitivity, range, delay) were being restored as curtain/blind capabilities from stored data. That’s the “blind mode” UI, and one of those DPs was also feeding motion, which explains the stuck presence.

Delete + re-pair works until the next update because it clears that stored state temporarily.

Fix is in Test 9.0.790+: phantom caps are stripped automatically and DynCap no longer re-applies them on update. Please update, restart the app, and check both sensors. Re-pair only if they still show as blinds.

The “flooding the Zigbee network” timeline message is the app rate-limiting ~200 msg/min from the Tuya firmware — related to the stuck presence spam, and it should calm down once the sensor is healed. Let me know if it persists after 9.0.790.

---

<div class="post-metadata">

**Author:** ![VicHY](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vichy/32/143896_2.png) [@VicHY](https://community.homey.app/u/VicHY)\
**Post date:** [September 2, 2026, 2:27pm UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2226 "2026-09-02T14:27:42Z")

</div>

Thanks a lot for the quick response and the explanations. I’ll give it a try and let you know. Regards.

---

<div class="post-metadata">

**Author:** ![VicHY](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vichy/32/143896_2.png) [@VicHY](https://community.homey.app/u/VicHY)\
**Post date:** [September 2, 2026, 9:47pm UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2227 "2026-09-02T21:47:08Z")

</div>

Hi @dlnraja

I had version 9.0.791 installed, and it was working correctly as a mmWave PIR sensor; however, after the version updated, the sensor switched to “curtain” mode and stopped working again. If I delete and reinstall it, it works correctly. The Zigbee network saturation warning no longer appears, but the battery warning persists (even though they don’t use batteries; they are connected to 220V). Here is the report number (c5165a37-2208-47a8-baaf-7a4190c4f97a).

Thank you very much.

 ![121748](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/b/6be1013b889c64e5ffa2787d005fc048dba2ff14.jpeg)

---

<div class="post-metadata">

**Author:** ![Eduard\_Martirosyan](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/eduard_martirosyan/32/173383_2.png) [@Eduard\_Martirosyan](https://community.homey.app/u/Eduard_Martirosyan)\
**Post date:** [September 5, 2026, 5:06am UTC](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352/2228 "2026-09-05T05:06:01Z")

</div>

Hi @dlnraja,

Thanks a lot for your work on this app.

I have a tubular roller blind motor with a built-in Tuya Zigbee receiver that is not recognised. It pairs fine but always ends up as “Unknown Zigbee Device” — tried Curtain Motor Shutter, Cover Controller, Curtain Motor Wall and 2 Gang Curtain Module on v9.0.809, same result every time.

**Fingerprint**

- manufacturerName: `_TZE284_fodv6bkr`
- modelId: `TS0601`
- appVersion: 67, hwVersion: 1, zclVersion: 3
- powerSource: battery, deviceType: enddevice, receiveWhenIdle: false (sleepy device)
- endpoint 1, profileId 260, deviceId 81
- inputClusters: `[0, 4, 5, 61184, 0, 60672]`
- outputClusters: `[25, 10]`

No windowCovering cluster (258), so everything goes through the Tuya EF00 datapoints as expected.

**Note:** this cluster list is identical to `_TZE284_libht6ua`, which is also a roller blind motor and already has support — the datapoints are probably the same. Might be an easy one to add.

**Device details**

- DC tubular motor, built-in lithium battery, electronic limits (manual: “DC Tubular Motor User Manual — Built-in Lithium Battery Electronic Limit V05”)
- Up/down limits are already set on the motor itself
- It also has a separate 433.92 MHz RF channel with an Alpha RE301 handheld remote, which works fine and is unrelated to Zigbee

**What I’d need exposed:** open / stop / close and position in percent. Motor direction would be a nice extra.

I couldn’t find this manufacturer ID anywhere — not in this app, not in the zigbee2mqtt database. Looks like a recent batch.

Full interview output:

```json
{
  "ids": {
    "modelId": "TS0601",
    "manufacturerName": "_TZE284_fodv6bkr"
  },
  "endpoints": {
    "ieeeAddress": "70:c5:9c:ff:fe:c2:14:52",
    "networkAddress": 36459,
    "modelId": "TS0601",
    "manufacturerName": "_TZE284_fodv6bkr",
    "endpointDescriptors": [
      {
        "status": "SUCCESS",
        "nwkAddrOfInterest": 36459,
        "_reserved": 24,
        "endpointId": 1,
        "applicationProfileId": 260,
        "applicationDeviceId": 81,
        "applicationDeviceVersion": 0,
        "_reserved1": 1,
        "inputClusters": [0, 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": {
          "basic": {
            "attributes": [
              { "id": 0, "name": "zclVersion", "value": 3 },
              { "id": 1, "name": "appVersion", "value": 67 },
              { "id": 2, "name": "stackVersion", "value": 0 },
              { "id": 3, "name": "hwVersion", "value": 1 },
              { "id": 4, "name": "manufacturerName", "value": "_TZE284_fodv6bkr" },
              { "id": 5, "name": "modelId", "value": "TS0601" },
              { "id": 6, "name": "dateCode", "value": "" },
              { "id": 7, "name": "powerSource", "value": "battery" },
              { "id": 65502, "dataTypeId": 32 },
              { "id": 65504, "dataTypeId": 72 },
              { "id": 65505, "dataTypeId": 72 },
              { "id": 65506, "dataTypeId": 32 },
              { "id": 65507, "dataTypeId": 72 },
              { "id": 65533, "name": "clusterRevision", "value": 2 },
              { "id": 65534, "name": "attributeReportingStatus", "value": "PENDING" }
            ],
            "commandsGenerated": "UNSUP_GENERAL_COMMAND",
            "commandsReceived": "UNSUP_GENERAL_COMMAND"
          },
          "groups": {
            "attributes": [
              { "id": 0, "name": "nameSupport", "value": { "type": "Buffer", "data": [0] } },
              { "id": 65533, "name": "clusterRevision", "value": 2 }
            ],
            "commandsGenerated": "UNSUP_GENERAL_COMMAND",
            "commandsReceived": "UNSUP_GENERAL_COMMAND"
          },
          "scenes": {
            "attributes": [
              { "id": 0, "dataTypeId": 32 },
              { "id": 1, "dataTypeId": 32 },
              { "id": 2, "dataTypeId": 33 },
              { "id": 3, "dataTypeId": 16 },
              { "id": 4, "dataTypeId": 24 },
              { "id": 65533, "name": "clusterRevision", "value": 2 }
            ],
            "commandsGenerated": "UNSUP_GENERAL_COMMAND",
            "commandsReceived": "UNSUP_GENERAL_COMMAND"
          }
        },
        "bindings": {
          "ota": { "attributes": [] },
          "time": { "attributes": [] }
        }
      }
    }
  }
}

```

Happy to test any build and report back — the motor is installed and accessible. Let me know if you need anything else.

Thanks!

[Previous page](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352.md?page=106)

[Next page](https://community.homey.app/t/app-pro-universal-tuya-zigbee-device-app-test/140352.md?page=108)