# \[APP\]\[Pro\] Tuya Local **URL:** \ **Category:** Apps\ **Created:** [April 21, 2026, 10:24pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077 "2026-04-21T22:24:35Z")\ **Posts on this page:** 20\ **Page:** 6
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [July 1, 2026, 6:28am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/102 "2026-07-01T06:28:02Z")
When connecting SmartLife to a Tuya Project, all SmartLife device names are automatically transferred. These names are stored as custom\_name for the Tuya device. No visible improvement/change for me in v1.0.83. EDIT: I can setup the status indicator (position) of the curtain devices in the Homey Android app, but this same indicator has been disabled in the Homey web app. ---
**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:** [July 1, 2026, 9:39am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/103 "2026-07-01T09:39:22Z")
> [@Amersfoort](#): > > but this same indicator has been disabled in the Homey web app Maybe this helps - force reload the web app page - and/or check the quick action settings ![Screenshot_20260701_113058_Vivaldi](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/9/59fff01dcdb7d4199ecf03699921b4adcf335c27.jpeg) ![Screenshot_20260701_113756_Vivaldi](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/9/99fd6ae4931f15e14a61c397f7b6f89df57c30ba.jpeg) ---
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [July 1, 2026, 9:44am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/104 "2026-07-01T09:44:20Z")
Did a F5, Ctrl-F5 and Chrome incognito mode without any luck ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/f/3f97de638a581e57a106c18e71179cdd17954d27.png) ---
**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\ **Post date:** [July 1, 2026, 9:47am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/105 "2026-07-01T09:47:29Z")
> [@Amersfoort](#): > > but this same indicator has been disabled in the Homey web app. Are you logging in to your Homey via a local user account? If so, the local web app version is not up to date. I think it is version 1.15.x, while the cloud web app version is currently on 1.18.1. Check the cloud version via my.homey.app. ---
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [July 1, 2026, 9:50am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/106 "2026-07-01T09:50:25Z")
Using my.homey.app: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/4/b40fccb169726b6274719e2b0ad87e709a33dd63.png) ---
**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\ **Post date:** [July 1, 2026, 5:54pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/107 "2026-07-01T17:54:02Z")
@Amersfoort That’s how it looks like for me in 1.0.83: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/9/899f2a4db450e868bc366b50f022f30b3cff2153.png) Custom\_Name in blue Name Type Device ID is available and Local Key as well ---
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [July 1, 2026, 6:18pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/108 "2026-07-01T18:18:16Z")
> [@Amersfoort](#): > > SmartLife Are you using SmartLife linked to Tuya IOT? Do you have more than one Tuya device? I created a project in Tuya IoT. I established a connection with Tuya via Smartlife and then used your app v1.0.83. Did I forget a step somewhere? ---
**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\ **Post date:** [July 1, 2026, 6:34pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/109 "2026-07-01T18:34:24Z")
Just checked what happens in my case, but I observe the same behavior: the Local Key field is empty: ![Tuya Local Fetch Devices](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/6/06adfb11a13ff602a333fa18096e08f72b4055f5.png) ---
**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\ **Post date:** [July 1, 2026, 6:58pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/110 "2026-07-01T18:58:56Z")
@SunBeech @Amersfoort Could you please test it again in 1.0.84? ---
**Author:** ![SunBeech](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sunbeech/32/111391_2.png) [@SunBeech](https://community.homey.app/u/SunBeech)\ **Post date:** [July 1, 2026, 7:21pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/111 "2026-07-01T19:21:24Z")
Yes, it works now. It also shows the custom name: ![Tuya Local Cloud Lookup](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/0/30f604c339bffb882daadabd468106531c794243.png) ---
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [July 1, 2026, 7:31pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/113 "2026-07-01T19:31:26Z")
Yes, it’s an improvement. The local keys are visible, but for me the choice of blind motor is still hard (no custom\_name but name) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/f/bf93cc804ecabf6d245e0861b37fa28c42d5d9e0.png) ---
**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\ **Post date:** [July 1, 2026, 7:45pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/114 "2026-07-01T19:45:01Z")
Please try it again with **1.0.85** ---
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [July 2, 2026, 5:30am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/115 "2026-07-02T05:30:58Z")
Yes, it’s working! ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/e/ce0b57eb93940a809082fb54fabea6c4f0280fd0.png) I have another suggestion, but I don’t know if it is technically feasible: - Enter Access ID and Access Secret once and press a Test button to test the connection in the Toya local app settings. Save the access credentials so that they only need to be entered once. - When creating a Homey Tuya device, first select the desired IP address of the device to be paired. Then select the desired Tuya device from a dropdown based on name or custom\_name, using the access credentials as set in the app settings behind the scenes. ---
**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\ **Post date:** [July 2, 2026, 9:08pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/116 "2026-07-02T21:08:21Z")
Great 🎉 Could you please try the newest version? I tried to implement your idea in the pairing process: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/2/c21b7750618d1a6c87a269ac8b1bff87abd73939.png) ---
**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\ **Post date:** [July 3, 2026, 6:29am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/117 "2026-07-03T06:29:20Z")
That is indeed what I mean, nice! A few fine-tuning points: - Tuya local app “Cloud lookup” settings are actually no longer necessary, because the same settings are now also available in the device settings, including saving Access settings - if a Homey device already exists, there is still no clear notification, but only a disabled “Add device” button - Auto detect does not include v3.2 (which happens to be used by my curtain motors) and manual setting does not include v3.22 - change the color scheme of the “Fetch devices” button (dark blue with black text is difficult to read) Keep up the good work! ---
**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:** [July 3, 2026, 12:58pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/118 "2026-07-03T12:58:22Z")
@Andi I gave it a go and I’m especially impressed by the device and ID+Key detection! Thanks, highly appreciated. Using Tuya w/o cloud dependency (plus privacy) is always a plus. About the missing quick action button for curtain device types @Amersfoort reported: It misses @ my Tuya local curtains as well. So I’ve been diggin into it a bit. By comparison, I found out a curtain device needs to have both `windowcoverings_opened` and `windowcoverings_closed` boolean capabilities in order for the Quick action toggle to become available; The weird part: apparently _only the “closed” capability seem to act as toggle button_, as you can see on the Aqara curtain device settings screenshot. Aqara curtain capabilities: ![Screenshot_20260703_143633_Vivaldi](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/5/45b95d36dcc27740bfddd17db092abd544d7d41c.jpeg) Quick action is available @ Aqara curtain: ![Screenshot_20260703_143742_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/c/fc2544005c1e84ea30206adaeae04a875b2e6970.jpeg) Despite the odd title “Closed”, it acts as open/close toggle. Tuya Local curtain capabilities ![Screenshot_20260703_143407_Vivaldi](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/b/9b14568e6446c4c8d4e8b6f6e814747d0a8cd79c.jpeg) ![Screenshot_20260703_143424_Vivaldi](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/1/7104095566b99f47426c6f7342d602eab09006b1.jpeg) So, Andi, my question will be: Is it possible to add both these `windowcoverings_opened` and `windowcoverings_closed` capabilities to the curtain device driver? And if true, are you willing to add this to the app in a future release? Thank you. ---
**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\ **Post date:** [July 3, 2026, 1:29pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/119 "2026-07-03T13:29:16Z")
Thanks 🙂 > [@Amersfoort](#): > > - Tuya local app “Cloud lookup” settings are actually no longer necessary, because the same settings are now also available in the device settings, including saving Access settings That’s not fully true → if you click on a device under the app settings, Cloud Lookup, you will get the full picture of the device regarding the DPs and possible values (important for me to debug issues). > [@Amersfoort](#): > > - if a Homey device already exists, there is still no clear notification, but only a disabled “Add device” button added message " _This Device ID already exists in Homey_" in next version > [@Amersfoort](#): > > - Auto detect does not include v3.2 (which happens to be used by my curtain motors) and manual setting does not include v3.22 added `3.22` option in next version > [@Amersfoort](#): > > - change the color scheme of the “Fetch devices” button (dark blue with black text is difficult to read) changed the button color in next version ---
**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\ **Post date:** [July 3, 2026, 1:47pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/120 "2026-07-03T13:47:54Z")
@Peter_Kawa Thanks for the detailed investigation — that was exactly the right lead! You’re correct that `windowcoverings_closed` is the key capability Homey needs to show the Quick Action toggle. I’ve added it to the Curtain Motor driver in **v1.0.91** (just published TEST [Tuya Local | Homey](https://homey.app/a/com.tuyalocal/test/)). The toggle sends open/close commands and its state reflects the actual position — `closed = 0%`, `open = anything above`. Existing curtain devices are migrated automatically; just restart the Tuya Local app after updating and the Quick Action should appear. Note: `windowcoverings_opened` is not a standard Homey capability — it’s a custom one defined by the Aqara app, so we don’t need it here. `windowcoverings_closed` alone is sufficient per the Homey developer docs. [Window coverings | Homey Apps SDK](https://apps.developer.homey.app/the-basics/devices/best-practices/window-coverings) Let me know if the Quick Action shows up after the update! ---
**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:** [July 5, 2026, 6:43pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/121 "2026-07-05T18:43:42Z")
YW and thank you as well! That was quick 🙂 I can confirm the Quick Action is added to existing curtain devices now, with the v1.0.91 update & app restart. The curtain position shows too ![Screenshot_20260705_190553_Homey](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/9/0/9027d4edea40001a0d637a05399de0b80dd5476b.jpeg) I had to enable the QA myself though; maybe it’s an idea to have it enabled by default? > [@Andi](#): > > Note: `windowcoverings_opened` is not a standard Homey capability Ah, thanks! It’s a actually a HomeAssistant Community app device, not sure why this custom capability is present. ---
**Author:** ![FrankP](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/frankp/32/120754_2.png) [@FrankP](https://community.homey.app/u/FrankP)\ **Post date:** [July 7, 2026, 5:53am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/122 "2026-07-07T05:53:31Z")
Hi @Andi , I’m trying to add a Marmitek Buzz LO doorbell, but the DP’s aren’t recognized when adding the device. I do get the DP table in Cloud Lookup. Could you help me out with this one? DP table: ```auto Videocamera DP 101 basic_indicator Boolean true {} DP 103 basic_flip Boolean false {} DP 104 basic_osd Boolean true {} DP 106 motion_sensitivity Enum 1 0, 1, 2 DP 108 basic_nightvision Enum 0 0, 1, 2 DP 109 sd_storge string 0|0|0 maxlen 255 DP 110 sd_status value 5 1–5 step 1 DP 111 sd_format Boolean false {} DP 115 movement_detect_pic raw $ {} DP 117 sd_format_state value -20000 -20000–200000 step 1 DP 134 motion_switch Boolean false {} DP 136 doorbell_active string 1783360353 maxlen 255 DP 150 record_switch Boolean true {} DP 151 record_mode Enum 2 1, 2 DP 154 doorbell_pic raw {} DP 155 doorbell_ring_exist Enum 0 0, 1 DP 156 chime_ring_tune Enum 2 1, 2, 3, 4 DP 157 chime_ring_volume Integer 100 0–100 step 1 DP 160 basic_device_volume Integer 10 0–10 step 1 % DP 165 chime_settings Enum 1 0, 1, 3 DP 168 motion_area_switch Boolean false {} DP 169 motion_area String maxlen 255 DP 185 alarm_message raw eyJ2IjoiMy4wIiwiYnVja2V0IjoidHktZXUtc3RvcmFnZTMwLXBpYyIsImNtZCI6ImlwY19kb29yYmVsbCIsInR5cGUiOiJpbWFnZSIsIndpdGgiOiJyZXNvdXJjZXMiLCJmaWxlcyI6W1siL2JmMzAwMS0zOTc3MDI3OC1wcDAxMDBmNTIzZmQ3YmE2OGEzMi9kZXRlY3QvMTc4MzM2MDM1NC5qcGVnIiwiZDdkNTYzYWU3NDgxM2RjNCJdXX0= {} DP 253 onvif_change_pwd string {"res":"ok"} DP 254 onvif_ip_addr string 10.0.1.xx DP 255 onvif_switch bool true ``` [Previous page](https://community.homey.app/t/app-pro-tuya-local/154077.md?page=5) [Next page](https://community.homey.app/t/app-pro-tuya-local/154077.md?page=7)