# \[APP\]\[Pro\] Tuya Cloud - This app allows you to connect Homey to the Tuya cloud **URL:** \ **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:** 1918
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [January 2, 2024, 9:59pm UTC](https://community.homey.app/t/app-pro-tuya-cloud-this-app-allows-you-to-connect-homey-to-the-tuya-cloud/21313/1918 "2024-01-02T21:59:28Z")
Like Jepke wrote, this can’t be fixed @ Homey level, only Tuya can fix by sending “0” values when that socket is turned off. You can request @ Tuya support and wait. Or, use this workaround: You can use Advanced Virtual Device to replace the original socket device (which you can “hide” by moving it to a zone called “zombie” or whatever). You can control the AVD, and use the values with use of the ‘reflect’ functionality. It makes values of other devices available to the AVD without the use of flows. To set the power and current reading to zero when the socket is turned off, you can use a flow to update the power & current fields with the value “0” In case you’re thinking _WTF?_ I’m happy to make an example AVD. Also you can [take a look here](https://community.homey.app/t/app-pro-advanced-virtual-device-device-capabilities-app-with-unique-text-status-indicator/68198) for many examples; And here’s all posts about “[reflect](https://community.homey.app/search?context=topic&context_id=68198&q=Reflect&skip_context=false)” --- _[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)._