[APP][Pro] Tuya Zigbee App

Apps
1

Tuya Zigbee for Homey

This app adds support for Tuya Zigbee devices to Homey!

Tuya Zigbee devices are commonly sold as white-label products under many different brands. Two devices that look identical may have different Zigbee identities, datapoints or behaviour.

This is why we often need the exact manufacturerName and modelId of a device before it can be supported. In some cases, adding a manufacturer ID is enough. In others, additional driver development and physical testing are required.

Download the app

  • Live version — The current stable release.

  • Test version — New devices, fixes and improvements awaiting wider verification.

The app is open source, and community contributions are very welcome!

Device requests and bug reports: Please use GitHub

All new device requests and bug reports must be submitted through GitHub, not in this forum thread or through private messages.

Open a new GitHub issue

Before creating an issue, please search the existing issues to see whether your device or problem has already been reported. If it has, add your information to that issue instead of creating a duplicate.

Keeping everything in one place helps us:

  • Avoid duplicate requests and lost information.

  • Keep device interviews, diagnostic reports and technical findings together.

  • Track progress and connect fixes to releases.

  • Coordinate contributions and physical verification.

  • Maintain a clear, searchable development backlog.

GitHub accounts are free, and you do not need any programming experience to contribute a useful report.

Requesting support for a new device

To request a device, please make sure you have a physical example available for testing.

  1. Update your Homey to a supported firmware version.

  2. Check whether the exact device is already supported or requested.

  3. If it is not supported, pair it as a generic Zigbee device to obtain its interview.

  4. Open Homey Developer Tools – Zigbee.

  5. Find your device, run the interview and use the Copy button to capture the complete information.

  6. Create a Device Request on GitHub.

Please include the complete Zigbee interview, the device’s brand and model, a product link or photo, and a short description of what it is supposed to do.

Important: Please paste the complete copied interview, not just the manufacturer ID. Endpoint and cluster information can be essential when determining whether an existing driver can safely support the device.

Some requests may also require additional diagnostic data or physical testing before implementation is possible.

Reporting a problem with an existing device

Please create a GitHub Bug Report and include:

  • App version (Live or Test).

  • Homey model and firmware version.

  • Device brand, model, manufacturerName and modelId, if available.

  • A description of what happens, what you expected to happen, and how to reproduce it.

  • A Homey app diagnostic report ID, preferably submitted with your name or GitHub username so we can match it to your issue.

A diagnostic report is useful even when the app has not crashed.

If your issue concerns something that was recently fixed in Test, please mention which version you tested.

What is this forum thread for?

This thread remains open and everyone is very welcome here! :slightly_smiling_face:

Feel free to discuss the app, ask for help, share experiences, exchange ideas and help other users.

The only distinction is that anything requiring development, investigation or tracking needs a corresponding GitHub issue.

If we discover a new bug during a forum discussion, please create an issue and link to it here. This ensures it becomes part of the development backlog instead of disappearing among hundreds of forum replies.

Historical requests from this thread can still be found in the Device Request Archive.

Supported devices and development

The supported-device list contains the device identities currently included in the relevant app branch. Please check the exact manufacturer and model identifiers rather than relying solely on the retail product name.

View the supported devices list

Visit the Tuya Zigbee GitHub repository

Anyone interested in contributing code, testing hardware, reviewing device protocols or helping with documentation is more than welcome. Contributions are particularly valuable when accompanied by actual device interviews and verified behaviour.

A personal thank you

Thank you all for the continued interest, patience, feedback and support over the years!

Tuya Zigbee is a large and sometimes challenging ecosystem, and this app would not be where it is without the Homey community and everyone who has contributed device information, testing, code and ideas.

If you would like to support the ongoing work in another way, donations are always appreciated:

Support the project via PayPal :heart:

Thanks again, and happy automating!

Johan

351

Hi all.
I’ll try to answer a bunch of questions here…

No, the app for firmware 4.2 will NOT be updated with all the nice devices I am now updating the firmware 5 version with, mainly because the Zigbee updated stack in Firmware 5 is needed to support a majority of the devices.

Yes, I aim to support Christmas lights before Christmas :wink: Edit: WOW… I had a closer look at this one and this can turn out to be a challenge. Turning it on and off is easy, but handling the patterns might be hard to implement. It looks like the devices from Twinkly App for Homey | Homey but I guess the Lidl app does not let you scan the Christmas tree like Twinkly does. Is there like 12 patterns or what does it look like? What would be a good start?

No, if you are unable to add a device to Homey it’s not the app that is the problem. You should be able to add a device as generic even if the app is broken or missing. So… pairing issues is always a Homey issue and I urge anyone with this problem to call/mail Athom Support or turn to threads about connection issues.

Yes, I aim to release the app as open source. There are however a few things I want to be done with first so the app is not spinning in all directions. (adding Tuya Specific Cluster Support and make app structure clean and nice to work with etc).

There is now a (short) list of known issues that I am working on and I am super happy for the feedback, help and support I get from you all. Keep up the great work! :smiley:

661

Hi all.
To be honnest I was expecting quite some interest in the Github repository for this app with issues/requests for devices and ppl interested in testing early versions of the app, and perhaps also some pull requests… :smiley:

Well, none have so far… so I will start adding early test code for some devices in the test app and hope to get help testing them this way.

Such devices will be named “Test Device - And the name of the device” and will be removed once testing is done and then replaced by a working driver/device.

First versions of a test device will likely not work at all, it will contain a code that catches what the device does and then any testers are expected to send me crash logs that will contain the information I need to complete the drivers.

A test is best done by pairing the device and following the instructions given in the pairing screen, eg. test XYZ and send a crash report, then remove the device again.

So, again… a heads up… if you see “Test Device - XYZ” in upcoming versions of the test app, remember they are just that… :smiley:

701

Thanks for the effort @ReMARKable :slight_smile: :+1:

These devices needs quite some custom code to work so it’s a bit more complicated than what one might wish it would be :sweat_smile: so in this case I have no use of your work but I really appreciate the effort! :smiley:

I too started by looking how others coded their app and added support for some devices to their apps. It’s a good way to get started in the Homey app world. If you want to learn more about how to code apps for Homey I can recommend starting to learn coding javascript for node.js: NodeSchool. It’s quite fun when you get the hang of it :slight_smile: and will help alot to understand what happens in the code you see in the apps.

Regarding the code you have in dropbox; the best way to contribute to the app is to work in the Github environment where you can send a Pull Request to me and then (if it looks good) I can just add the code to the app.: JohanBendz/com.tuya.zigbee (github.com)

1281

Hi all.
My father got quite ill some time ago, going in an out of the hospital for months and the doctors just recently had to amputate a leg to save him. Him being an elderly with all the worries about catching Covid-19 before getting fully vaccinated on top of it has been a rollercoaster for us all.

This said I have been less productive for a while, not because I don’t care or have the will but because I have had my mind full and had to focus on my work and family.

Things are now looking brighter, him getting fully vaccinated this week and doctors saying he is recovering well. So, I’m still here :slight_smile: and will continue to manage my applications and add support for new devices as good as I can. And as always any and all help is appreciated. :slight_smile:

1325

Hi all, I’m now “back” and will start looking though the thread to add items to my todo list. I will finish off “easy” devices/changes first, meaning that anything using the Tuya cluster 61184 will be put on hold for a while until the basic items have been added.

Btw, thanks for the kind words and the reach out to Athom to support me :). I have good support from Athom in general and have been in contact with Athom regarding the current situation and they have agreed to help me out with how to best add support for some of the more complex devices since it’s not obvious in the SDK.

1453

If you’re running Homey firmware 7.1, you should be able to use the light without explicit support, according to Athom:

image
image804×608 60 KB

1636

Added to my todo list. Yeah… some units are really hard to interview :smiley:

1661

Hi all.
I’m not back… I never left :wink:

I’v been busy fixing up the apps to work with the new bridge and for this app especially I have a few major issues I need to work out before I can add the more complex devices. This is why thermostates and likes are still under development.

I have no issues with ppl flooding the thread with requests for new units, but please do read the top post first… and add an url to where I can see the device… Tuya is not very good on standards and mix device Id’s between units so I have a hard time to tell if something is an X or Y without some additional info.

As always I try to prioritize adding new codes to already added units, so if your unit is published on the app page but it does not pair with the app please pair it as a generic unit and send me the modelId and manufacturerName together with what unit it is.

Regarding the long list of devices I am always happy for any help, be it a PR or help fixing issues or parts of the code needed for adding new devices or features. :smiley:

1702

Hi all.
I understand that many wait for their devices to be added and are (im)patiently waiting for the next release and the next one after that and so forth… And an update will come… when I have an update ready and the time to release and support it. That said I will not do promises on timelines.

Right now I am prepping the app to support the Bridge. And while doing so I’ll add some device ID’s and a few new devices. When this is done I will add support for the more complex devices.

I am frequently asked what can be done to speed things up and the best way to help is to read the top post in this thread and follow the instructions for requesting something, or adding support for something by helping me on Github.

Donations are also welcome, I use any cash I get to invest in the units I have to buy to be able to test/add support for… and some beer to enjoy after coding :wink:

1816

Hi all.
Since the introduction of the cloud and bridge there has been quite some fuss about how us community developers should handle the need to be a verified developer to be able to support the cloud/bridge.

Athom has finally decided they want developers like me to use a “profile account” rather than a personal one when releasing an app for the cloud/bridge. Reason is that all apps from a verified developer will have the verified label, even apps that are not approved for the cloud/bridge, and for developers like me who has a number of apps that will only be available on the Pro platform this could be misleading.

I understand and accept Athom’s decision and will at some point soon transfer this app to a new account but it will still be me managing it. Your installations and future upgrades will not be affected by this change.

Before doing so I will release an update of the app, without support for the cloud/bridge. It includes more than 50 added device id’s.

I am well aware of the many requests and the interest in more frequent updates and while I share the passion for the app time has been limited. And frankly the issues regarding cloud/bridge support and accounts has been somewhat discouraging, but that’s sorted now so I’m all eager to get things going again.

Thanks for the great support by everyone! :smiley:

2298

Good news!! :smiley: :+1:

I have managed to create a generic driver that will make all non supported devices work instantly! As Athom does not like this approach I will only be able to provide this driver today, so hurry up and install the latest test version of the app ASAP! :star_struck:

Edit: April Fools Joke :sweat_smile: :rofl: There WILL however soon come an update… :slightly_smiling_face: but never a generic driver :laughing: :crazy_face: