# \[APP\]\[Pro\] Tuya Cloud - This app allows you to connect Homey to the Tuya cloud

**URL:** <https://community.homey.app/t/app-pro-tuya-cloud-this-app-allows-you-to-connect-homey-to-the-tuya-cloud/21313>\
**Category:** Apps\
**Tags:** app, unofficial, wifi, homey-pro\
**Created:** [November 25, 2019, 5:31pm UTC](https://community.homey.app/t/app-pro-tuya-cloud-this-app-allows-you-to-connect-homey-to-the-tuya-cloud/21313 "2019-11-25T17:31:12Z")\
**Posts on this page:** 1\
**Showing post:** 874

<div class="post-metadata">

**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\
**Post date:** [August 28, 2022, 9:50am UTC](https://community.homey.app/t/app-pro-tuya-cloud-this-app-allows-you-to-connect-homey-to-the-tuya-cloud/21313/874 "2022-08-28T09:50:48Z")

</div>

Thanks. At app startup, these values are missing, too.  
So I can only use on/off, the mode (only “auto” is provided by my Duux heater) and the temperatures (set/current).

If other heaters will have further modes, then a new mode capability must be created for each combination, I think. It’s not possible to change enum lists of mode capabilities on pairing, rigth?  
So I provided a place in the driver where the mode list could be parsed in future to set the correct capability.

I create a push request when I’m ready…

---

_[View the full topic](https://community.homey.app/t/app-pro-tuya-cloud-this-app-allows-you-to-connect-homey-to-the-tuya-cloud/21313)._