I tried again, but now the device isn’t recognized at all.
Hi Dylan,
Hope you are great!
Unfortunately the referred devices are still not responding with the app.
I believe that the 4 gang switch (now cannot paired) needs only to be added to the 4 buttons wireless drivers and json (not to the 4 scene) as the other switch i have is now perfect with this driver and I had tested in the past that is the same.
the motion sensor is paired as presence sensor and is not operating
the curtain and smoke cannot be paired at all.
the curtain was working with a previous version during December but now not.
thank you Eftychis
Hi, just to make sure, this app doesn’t appear in Homey Apps without the “Test”, right? I tried to access the https://homey.app/a/com.dlnraja.tuya.zigbee/ but it gives me an error, but the https://homey.app/a/com.dlnraja.tuya.zigbee/test/ currently is working just in test mode, right? Thanks and congrats for this amazing app and fast updates!
That’s true, test apps don’t show up in the App Store
Ver.5.11.118. Contact Sensor ZG-102Z still not installing. Comes up as unknown Zigbee. Use to work in version xx.45.
Hi @dlnraja, is this app working on Homey Self-Hosted Server?
Cause I’ve tried 3 Zigbee devices that are marked as already supported in v5.11.138 but when I try to add in my Homey Self-Hosted Server it shows as Unknown Zigbee Device.
Here is my server information:
Homey Self-Hosted Server using Docker
homeyVersion “13.0.0”
nodeVersion “v24.14.0”
Homey Bridge
Homey App: Android Version 9.9.0
Universal Tuya Experimental: v5.11.118
When I click on App Settings it keeps Loading without opening anything as show in the images below:
Developer Tool as iPhone:
Android Phone:
Also, when I see Homey Log when I restart the app I receve this information:
Log while Restarting App:
2026-Mar-24 20:28:03
Homey [log][ManagerAppsLocal][AppLocal:com.dlnraja.tuya.zigbee] Stopping…
2026-Mar-24 20:28:03
Homey [log][ManagerAppsLocal][AppLocal:com.dlnraja.tuya.zigbee] Exited. Code: 0, Signal: null
2026-Mar-24 20:28:03
Homey [log][ManagerAppsLocal][AppLocal:com.dlnraja.tuya.zigbee] Stopped
2026-Mar-24 20:28:03
Homey [log][ManagerAppsLocal][AppLocal:com.dlnraja.tuya.zigbee] Starting…
2026-Mar-24 20:28:03
Homey [log][ManagerAppsLocal][AppLocal:com.dlnraja.tuya.zigbee] Session ID: com.dlnraja.tuya.zigbee-5.11.118-e139d6fc
2026-Mar-24 20:28:03
Homey [log][ManagerDiscoveryLocal][DiscoveryStrategyMDNSSDLocal:3d9d4f35-24d7-4342-83fa-df62cf102cda] Init mDNS-SD Strategy: _ewelink._tcp
2026-Mar-24 20:28:04
Homey [log][ManagerAppsLocal][AppLocal:com.dlnraja.tuya.zigbee] Child process spawned successfully
2026-Mar-24 20:28:04
Homey [log][ManagerAppsLocal][AppLocal:com.dlnraja.tuya.zigbee] Started
2026-Mar-24 20:28:04
Homey [log][ManagerApiLocal] IO homey:manager:apps:restartApp → Success 204
And in pairing there is no errors.
Devices I tried to add:
Manufacturer Name: ZBeacon
Model ID: TS011F
Manufacturer Name: _TZE284_bquwrqh1
Model ID: TS0601
If you need any more information that could help just ask me and I’ll gladly answer. Thank you very much.
Just one more information, when I tried to add Manufacturer Name: _TZE284_bquwrqh1 Model ID: TS0601I got a different error:
Here is what I got from Docker Log error (got some information masked for security issues)
026-Mar-24 21:41:35
Homey [log][ManagerApiLocal] IO homey:manager:drivers:createPairSession
2026-Mar-24 21:41:35
Homey [log][ManagerApiLocal] IO homey:manager:drivers:createPairSession → Success 200
2026-Mar-24 21:41:36
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent
2026-Mar-24 21:41:36
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent → Success 204
2026-Mar-24 21:41:40
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
2026-Mar-24 21:41:40
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
2026-Mar-24 21:41:40
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent
2026-Mar-24 21:41:40
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent → Success 204
2026-Mar-24 21:41:40
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent
2026-Mar-24 21:41:40
Homey [log][ManagerVirtualDeviceLocal][VirtualDriverZigbee:driver] Status: ADD_NODE_STATUS_LEARN_READY
2026-Mar-24 21:41:40
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingEvent → Success 204
2026-Mar-24 21:41:40
Homey [log][ManagerZigbee] Waiting for node to join…
2026-Mar-24 21:41:41
zigbee:process:join waiting for node to join
2026-Mar-24 21:41:45
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
2026-Mar-24 21:41:45
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
2026-Mar-24 21:41:46
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx update node address networkAddress=55556
2026-Mar-24 21:41:46
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx node joined networkAddress=55556
2026-Mar-24 21:41:46
zigbee:process:join node joined { ieeeAddress: ‘xx:xx:xx:xx:xx:xx:xx:xx’, networkAddress: 55556 }
2026-Mar-24 21:41:46
Homey [log][ManagerZigbee] Node joined with ieeeAddress xx:xx:xx:xx:xx:xx:xx:xx
2026-Mar-24 21:41:46
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [001] get node capabilities
2026-Mar-24 21:41:46
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx zdo end device announce indication Bitmap [ allocateAddress ]
2026-Mar-24 21:41:46
Homey [log][ManagerZigbee] received end device announce indication with ieeeAddress: xx:xx:xx:xx:xx:xx:xx:xx
2026-Mar-24 21:41:46
zigbee:process:interview Get match descriptor for poll control cluster
2026-Mar-24 21:41:46
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [002] get match descriptor profileId=260 inputClusters=[ 32 ]
2026-Mar-24 21:41:46
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [001] get node capabilities error: This operation was aborted
2026-Mar-24 21:41:46
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [002] got match descriptor { matchList: , nwkAddrOfInterest: 55556, status: ‘ZSuccess’ }
2026-Mar-24 21:41:46
zigbee:process:interview Got match descriptor response { matchList: , nwkAddrOfInterest: 55556, status: ‘ZSuccess’ }
2026-Mar-24 21:41:46
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [003] get active endpoints
2026-Mar-24 21:41:47
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [003] got active endpoints [ 1 ]
2026-Mar-24 21:41:47
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [004] get simple descriptor endpointId=1
2026-Mar-24 21:41:47
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [004] got simple descriptor endpointId=1 { endpointId: 1, applicationProfileId: 260, applicationDeviceId: 81, applicationDeviceVersion: 0, _reserved1: 1, inputClusters: [ 4, 5, 61184, 0, 60672 ], outputClusters: [ 25, 10 ], nwkAddrOfInterest: 55556, _reserved: 0, status: ‘ZSuccess’ }
2026-Mar-24 21:41:47
zigbee:process:interview get basic attributes
2026-Mar-24 21:41:47
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [005] enabling route discovery for nwkAddr=55556
2026-Mar-24 21:41:47
zigbee:process:interview got basic attributes: { modelId: ‘TS0601’, manufacturerName: ‘_TZE284_bquwrqh1’ }
2026-Mar-24 21:41:47
zigbee:process:interview No poll control cluster found
2026-Mar-24 21:41:47
zigbee:process:interview complete { ieeeAddress: ‘xx:xx:xx:xx:xx:xx:xx:xx’, networkAddress: 55556, modelId: ‘TS0601’, manufacturerName: ‘_TZE284_bquwrqh1’, endpointDescriptors: [ { endpointId: 1, applicationProfileId: 260, applicationDeviceId: 81, applicationDeviceVersion: 0, _reserved1: 1, inputClusters: [Array], outputClusters: [Array], nwkAddrOfInterest: 55556, _reserved: 0, status: ‘ZSuccess’ } ], deviceType: ‘enddevice’, receiveWhenIdle: false, swBuildId: undefined, touchlinkGroupIds: undefined, capabilities: { alternatePANCoordinator: false, deviceType: false, powerSourceMains: false, receiveWhenIdle: false, security: false, allocateAddress: true }, pollControl: undefined }
2026-Mar-24 21:41:47
zigbee:process:interview Received abort signal { reason: ‘Destroyed’ }
2026-Mar-24 21:41:47
zigbee:process:interview destroyed
2026-Mar-24 21:41:47
zigbee:process:join Received abort signal { reason: ‘Destroyed’ }
2026-Mar-24 21:41:47
zigbee:process:join destroyed
2026-Mar-24 21:41:47
Homey [log][ManagerZigbee] Node interviewed: modelId: TS0601, manufacturerName: _TZE284_bquwrqh1, ieeeAddress: xx:xx:xx:xx:xx:xx:xx:xx, networkAddress: 55556
2026-Mar-24 21:41:47
Homey [log][ManagerVirtualDeviceLocal][VirtualDriverZigbee:driver] Searching for installed driver (_TZE284_bquwrqh1 - TS0601)
2026-Mar-24 21:41:47
Homey [log][ManagerVirtualDeviceLocal][VirtualDriverZigbee:driver] Using driver: Presence Sensor Radar (id: homey:app:com.dlnraja.tuya.zigbee:presence_sensor_radar, installed: true)
2026-Mar-24 21:41:47
Homey [log][ManagerZigbee] bind ieeeAddress=xx:xx:xx:xx:xx:xx:xx:xx, endpointId=1, clusterId=1
2026-Mar-24 21:41:47
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [006] bind endpointId=1 clusterId=1 target=yy:yy:yy:yy:yy:yy:yy:yy:1
2026-Mar-24 21:41:48
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [006] bind error endpointId=1 clusterId=1: Unexpected Bind Response (status: zdoInvalidEndpoint)
2026-Mar-24 21:41:48
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [006] bind endpointId=1 clusterId=1 target=yy:yy:yy:yy:yy:yy:yy:yy:1
2026-Mar-24 21:41:48
zigbee:controller:node:xx:xx:xx:xx:xx:xx:xx:xx [006] bind error endpointId=1 clusterId=1: Unexpected Bind Response (status: zdoInvalidEndpoint)
2026-Mar-24 21:41:48
Homey [err][ManagerZigbee] Error: failed to create binding (ep: 1, cl: 1) Unexpected Bind Response (status: zdoInvalidEndpoint)
2026-Mar-24 21:41:48
Homey [err][ManagerZigbee] Could not create node bindings ZNPAsyncRequestError: Unexpected Bind Response (status: zdoInvalidEndpoint)
2026-Mar-24 21:41:48
at file:///app/node_modules/@athombv/zstack/dist/lib/ZStackController.mjs:922:27
2026-Mar-24 21:41:48
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
2026-Mar-24 21:41:48
at async fn (file:///app/node_modules/@athombv/zigbee/dist/src/Controller.mjs:481:42)
2026-Mar-24 21:41:48
at async Queue.runTask (file:///app/node_modules/@athombv/zigbee/dist/src/Queue.mjs:220:28) {
2026-Mar-24 21:41:48
status: ‘zdoInvalidEndpoint’
2026-Mar-24 21:41:48
}
2026-Mar-24 21:41:48
Homey [err][ManagerVirtualDeviceLocal][VirtualDriverZigbee:driver] Error: create_bindings_failed
Hello @dlnraja Dylan, I hope you are doing OK. I have tried to add the device BSEED Zigbee 1-Gang Touch Switch but unfortunately, it shows the error “Unable to connect Something went wrong while adding this device, please try again”
when I checked in the Homey Developer tool, I have observed:
Manufacturer: _TZ3002_jn2x20tg
Model ID: TS0726
Device: Unknown Mode
Model TS0726 (_TZ3002_jn2x20tg) is currently assigned to 4-Gang, but it’s also used for 1-Gang devices. Please, Could you update the driver?"
Thanks!
( @dlnraja if this post is inappropriate regarding your app, please let me know, I’ll remove it )
@ all:
Homey Pro 2023/26 & mini recently published firmware v13.1.0-RC.x should support more generic zigbee devices, with sensors standing out.
I’m curious which sensors work as generic zigbee device (without an app):
v5.11.138 is up on test.
v5.11.132: Implemented batch close/respond state update for improved device management., No new features added in this release., No improvements made in this release., No changes in CI/CD processes.
Covers a huge range of Tuya devices at this point.
Hello Dylan, I hope you are doing OK.
I’am trying to add a new Soil Moisture Sensor (_TZE284_oitavov2 | TS0601). I alread have several of these devices connected to my homey. They work great.
But i just bought some new ones and when i try to add them i got the “Unable to connect Something went wrong while adding this device, please try again”. If i cancel the installation i can’t see a device in homey, but i can see it in the developer tool as an unknow node.
On the commuitie form i can see that there are more users with this problem. I looks like there is a problem adding new devices.
Can you please take a look at it. if you need testing i will be available. just send me an email
Thanks.
Yes dont worry if someone have the list of this new native support it will be grateful to share @Peter_Kawa
Concerning the récurent issue , it might be related to the new system to support dp dynamically . I will check asap @Ronald_Bok
I would appreciate if you could correct this. Ver.5.11.118. Contact Sensor ZG-102Z still not installing. Comes up as unknown Zigbee. Use to work in version xx.45.
Hi Lasse
We are on Ver 5.11.138 now so if you update maybe it’s working now.
Grtz Peter.
Sorry, Ver. 138. It installs, but no reaction at all from moving magnet.
@dlnraja Hello Dylan,
I can pair the device BSEED Zigbee 1-Gang Touch Switch using the v5.11.138. The switch is paired as 1-Gang Smart Switch.
The problem is if I try to switch Off or ON then it shows the following error:
Driver Not Initialized: switch_1gang
Thank you very much!
Since last update I lost access to many switch modules like the TZ3000_jl7qyupf, TZ3000_46t1rvdu & TZ3000_bvrlqyj7?
All other items like lights or wall sockets work fine, it’s only these switch modules that don’t work any longer?
I tried reinstalling them but after installation get the error message “Driver Not Initialized: switch_2gang” for example (for the TZ3000_bvrlqyj7)
Can you please check if this can be corrected?
Many thanks!!
Just pushed v5.11.138 to the test channel.
Universal Tuya Zigbee app v5.11.138 adds full DP mapping for A89G12C and ZS-300TF models, fixes pairing for TS0601 models, and prevents universal_fallback from affecting motion sensors.
Covers a huge range of Tuya devices at this point.
v5.11.138 is up on test.
Universal Tuya Zigbee app v5.11.138 adds new device support and fixes critical pairing issues.
Covers a huge range of Tuya devices at this point.
Dropped v5.11.142 on the test channel just now.
v5.11.140: Fixed pairing failure for presence_sensor_radar with DP-only TS0601 devices., Removed strict cluster endpoints requirement to improve pairing for TS0601 models., Prevented universal_fallback from hijacking motion sensors., Added full Tuya DP mapping for A89G12C and ZS-300TF models., Enriched driver and fingerprint data, increasing total to 3862 fingerprints across 189 drivers.
Covers a huge range of Tuya devices at this point.
