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

New version released

I have found the publish issue ( related of number of drivers , I have merged some drivers to unified one ) and now working of fixing all issues forums users , pr , and forums messages . So the fix will be soon available. This one might right now crash ( the today released version ), so I reimplementing back the d fingerprint.json .

And good new I have found another new job I will start back en 10 June my new job. ( In cyber strategy)

Hi Dylan Good afternoon, installed new version 8.1.60.
Contact sensors okay, repairing existing SOS button no result. Adding Smartbutton and other SOS button still only been seen as Universal ZigBee device.

Diagnostic code: 703fb7df-35b6-478a-995e-5beb8fb6d901

Thanks again and good luck again, best regards Peter.

Version 8.1.63 no changes for me.

And now APP works fine to me. Thank You!

Hi,
I’m trying to integrate a SmarterCurry Solar Lux Sensor (Tuya fingerprint: _TZE284_aaeasoll / TS0601) with the Tuya Unified Zigbee app on my Homey Pro.
After pairing, the device is recognized as a climate_sensor instead of a brightness/lux sensor, and no lux values are displayed.
I was pointed here by dlnraja via GitHub Issue #1379 (JohanBendz/com.tuya.zigbee), where he mentioned that TZE284 is logged for the next release but not yet fully implemented.
I have created a diagnostic report — ID: [056e5755-7444-44a7-889f-7a7e95569c0b]
Hope this helps to add proper support for this device. Happy to provide any additional information if needed.
Thanks!

Hi Dylan, just tested version 8.1.68 no changes and I’ve seen that the Luminance of the Doo/Window sensors the Luminance is not lower than 1128 Lx while it’s fully dark outside see screenshot.

Diagnostic code 'ff555890-afce-4dee-8706-6ff993c40db2

Good night and thanks for your hard work.
Best regards Peter.

Hi

I’m a bit confused …

Does every sensor have to be recognized by an app before integrating it in this app ?

Hi the device’s need to be registered into the app and after that you need to add every single device to your Homey.
Registering can be done by interviewing the device from the tools.developer.homey.app/tools/zigbee page.

Best regards Peter.

Hi Dylan Good morning,

I’ve installed the latest version 8.1.75 of your app, the Luminance readings from the Door/Window sensors are still wrong the all staying at the same value even when it’s dark.
Also the Smartbutton _TZ3000_mrpevh8p TS0041 and the SOS button _TZ3000_0dumfk2z TS0215A still been added as generic ZigBee device.

Diagnostic code: ea2c0a85-4cc3-40e2-8e71-166016b6ed9e


Good luck and thanks again Peter.

No other needed ? just this APP

In devtools I can see it but in unkwon Zigbee item


Appareil Zigbee inconnu
a4:c1:38:8a:9c:51:ab:a0 14993 (3A91) EndDevice ? x eWeLink SNZB-03

image

“ids”: {
“modelId”: “SNZB-03”,
“manufacturerName”: “eWeLink”
},
“endpoints”: {
“endpointDescriptors”: [
{
“endpointId”: 1,
“applicationProfileId”: 260,
“applicationDeviceId”: 1026,
“applicationDeviceVersion”: 0,
“_reserved1”: 0,
“inputClusters”: [
0,
3,
1,
1280,
32
],
“outputClusters”: [
25
]
}
],
“endpoints”: {
“1”: {
“clusters”: {
“basic”: {
“attributes”: [
{
“acl”: [
“readable”
],
“id”: 0,
“name”: “zclVersion”,
“value”: 3
},
{
“acl”: [
“readable”
],
“id”: 1,
“name”: “appVersion”,
“value”: 113
},
{
“acl”: [
“readable”
],
“id”: 2,
“name”: “stackVersion”,
“value”: 2
},
{
“acl”: [
“readable”
],
“id”: 3,
“name”: “hwVersion”,
“value”: 0
},
{
“acl”: [
“readable”
],
“id”: 4,
“name”: “manufacturerName”,
“value”: “eWeLink”
},
{
“acl”: [
“readable”
],
“id”: 5,
“name”: “modelId”,
“value”: “SNZB-03”
},
{
“acl”: [
“readable”
],
“id”: 7,
“name”: “powerSource”,
“value”: “battery”
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 18,
“name”: “deviceEnabled”,
“value”: true
},
{
“acl”: [
“readable”
],
“id”: 16384,
“name”: “swBuildId”,
“value”: “0122052017”
},
{
“acl”: [
“readable”
],
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“identify”: {
“attributes”: [
{
“acl”: [
“readable”,
“writable”
],
“id”: 0,
“name”: “identifyTime”,
“value”: 0
},
{
“acl”: [
“readable”
],
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“powerConfiguration”: {
“attributes”: [
{
“acl”: [
“readable”,
“reportable”
],
“id”: 32,
“name”: “batteryVoltage”,
“value”: 24,
“reportingConfiguration”: {
“direction”: “reported”,
“attributeDataType”: 32,
“minInterval”: 0,
“maxInterval”: 3600,
“minChange”: 3,
“status”: “SUCCESS”
}
},
{
“acl”: [
“readable”,
“reportable”
],
“id”: 33,
“name”: “batteryPercentageRemaining”,
“value”: 58,
“reportingConfiguration”: {
“direction”: “reported”,
“attributeDataType”: 32,
“minInterval”: 0,
“maxInterval”: 3600,
“minChange”: 6,
“status”: “SUCCESS”
}
},
{
“acl”: [
“readable”
],
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“iasZone”: {
“attributes”: [
{
“acl”: [
“readable”
],
“id”: 0,
“name”: “zoneState”,
“value”: “enrolled”
},
{
“acl”: [
“readable”
],
“id”: 1,
“name”: “zoneType”,
“value”: “motionSensor”
},
{
“acl”: [
“readable”
],
“id”: 2,
“name”: “zoneStatus”,
“value”: {
“type”: “Buffer”,
“data”: [
1,
0
]
}
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 16,
“name”: “iasCIEAddress”,
“value”: “00:12:4b:00:1b:44:e3:cc”
},
{
“acl”: [
“readable”
],
“id”: 17,
“name”: “zoneId”,
“value”: 0
},
{
“acl”: [
“readable”
],
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
},
“pollControl”: {
“attributes”: [
{
“acl”: [
“readable”,
“writable”
],
“id”: 0,
“name”: “checkInInterval”,
“value”: 14400
},
{
“acl”: [
“readable”
],
“id”: 1,
“name”: “longPollInterval”,
“value”: 14400
},
{
“acl”: [
“readable”
],
“id”: 2,
“name”: “shortPollInterval”,
“value”: 1
},
{
“acl”: [
“readable”,
“writable”
],
“id”: 3,
“name”: “fastPollTimeout”,
“value”: 40
},
{
“acl”: [
“readable”
],
“id”: 4,
“name”: “checkInIntervalMin”,
“value”: 0
},
{
“acl”: [
“readable”
],
“id”: 5,
“name”: “longPollIntervalMin”,
“value”: 0
},
{
“acl”: [
“readable”
],
“id”: 6,
“name”: “fastPollTimeoutMax”,
“value”: 0
},
{
“acl”: [
“readable”
],
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
}
},
“bindings”: {
“ota”: {
“attributes”: [
{
“acl”: [
“readable”
],
“id”: 0
},
{
“acl”: [
“readable”
],
“id”: 1
},
{
“acl”: [
“readable”
],
“id”: 2
},
{
“acl”: [
“readable”
],
“id”: 3
},
{
“acl”: [
“readable”
],
“id”: 4
},
{
“acl”: [
“readable”
],
“id”: 5
},
{
“acl”: [
“readable”
],
“id”: 6
},
{
“acl”: [
“readable”
],
“id”: 7
},
{
“acl”: [
“readable”
],
“id”: 8
},
{
“acl”: [
“readable”
],
“id”: 9
},
{
“acl”: [
“readable”
],
“id”: 65533,
“name”: “clusterRevision”,
“value”: 1
}
],
“commandsGenerated”: “UNSUP_GENERAL_COMMAND”,
“commandsReceived”: “UNSUP_GENERAL_COMMAND”
}
}
}
}
}

Hi Dylan Good evening, thanks for fixing the Luminance is okay now it decreased now it’s dark to 0 :+1:t2:
The SOS button and the Smartbutton are added now as the right ones, Smartbutton was very difficult to add it took me about 10 time’s, no response and battery readings from both of them.

Diagnostic code: 330bb9b9-83f5-4c9e-952a-a4b5755decbe

Thanks so far and good luck :crossed_fingers:t2:
Good night Peter.

Moes 2 gang dimmer, pairs okay but this comes up..

i see u update app the whole time, super good and hard work, hope you can fix my problem to​:smiling_face_with_three_hearts:

Hi,

I’m trying to use a Zigbee soil moisture sensor with the Universal Tuya Zigbee app on Homey Pro.

Device information

  • Manufacturer: _TZE284_aao3yzhs
  • Model: TS0601
  • Device type: Soil moisture sensor
  • Homey Pro firmware: 7.4.2
  • App: Universal Tuya Zigbee

Issue
The device pairs successfully and appears to communicate correctly with Homey.

  • Zigbee interview completes successfully.
  • The device is online.
  • RX and TX counters increase, indicating that data is being received.
  • However, both temperature and soil moisture are displayed as 67109120 instead of valid values.

For example:

  • Temperature: 67109120 °C
  • Soil moisture: 67109120 %

This makes me think the device is sending data, but the datapoints may not be decoded correctly.

Interview information
The device exposes the Tuya cluster 0xEF00 (61184) and does not expose standard temperature or humidity clusters.

Relevant identifiers:

  • Manufacturer: _TZE284_aao3yzhs
  • Model: TS0601
  • Input clusters: 4, 5, 61184, 0, 60672

Could support for this specific TS0601 variant be missing, or does it require a different datapoint mapping?

I can provide the full interview dump if needed.

Thanks!

Hi Dylan,

First I want to say thank you for implementing the smartercurry luminace / brightness Sensor.

I updated the device, installed it again, it is correctly recognized as light sensor, but currently is Not showing Information about Lux Data.

This is the Diagnose Code b00b28a3-1470-4c2b-8f1e-0d8b6d167e7d

Thank you so much for your dedication

Hi Dylan Good afternoon, I’m on version 8.1.106 now but not working well either.
Luminance is not updating anymore, SOS button not reparable or re-adding doesn’t find device anymore and Smartbutton no data or battery readings.

Diagnostic code: 754a12da-9e6a-4385-aad8-4a75ccef76f4

Thanks and good luck with debugging grtz Peter.

Version 8.1.115 Luminance changing again, SOS and Smartbutton no changes.

Diagnostic code: 56345958-2af6-4955-afee-ccad90b52fbd

Good luck :crossed_fingers:t2:

Luminance not going lower than 455 Lx

Don’t know of you working on it currently, but to ensure up to date Information, the SmarterCurry Luminance Sensor is not receiving brightness data. Version 8.1.124

0ed123ea-9195-4a38-b961-ee42328d7611

Have a nice Saturday

Edit:

Updating with Version 8.1.133

e81acce5-e0f0-440f-8a17-f3cd5470fdb4

Edit:

Update regarding the SmarterCurry Luminance Sensor (_TZE284_aaeasoll / TS0601):

I did some research and found that the correct Tuya datapoint mapping for this device has already been implemented in the zigbee-herdsman-converters project:

-> PR #12347: Support SMARTERCURRY TZE284_aaeasoll illuminance sensor by AloneHUANG · Pull Request #12347 · Koenkk/zigbee-herdsman-converters · GitHub
→ Merged and released in v26.59.1 (May 29, 2025)

According to the PR, the relevant datapoints are:

  • DP 2 → Illuminance (Lux), raw value
  • DP for battery and configurable report interval also included

The Zigbee node data for my device confirms the same cluster setup (input cluster 0xEF00 / 61184), which matches the PR description.

Hoping this helps to implement the correct DP mapping on the Homey side as well. Happy to provide additional diagnostic data if needed.

Diagnostic code (v8.1.133): e81acce5-e0f0-440f-8a17-f3cd5470fdb4

Hi Dylan Good evening, I’m on Version 8,1,147 now and still no Luminance changing even not after a repair, also no changes for SOS and Smartbutton.

Diagnostics: 8bbdbad4-f0b4-4eb4-96e8-429a7c8b97a6

Have a nice evening and good luck regards Peter.

Hi, my presence sensor has stopped working, i tried to delete and add again but still nothing.

Diag report:

950ea50e-07f1-4c97-a46d-86a8baa6b3e7