# \[APP\]\[Pro\] Tuya Local

**URL:** <https://community.homey.app/t/app-pro-tuya-local/154077>\
**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:** 8

<div class="post-metadata">

**Author:** ![Luca\_Farronato](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/luca_farronato/32/169354_2.png) [@Luca\_Farronato](https://community.homey.app/u/Luca_Farronato)\
**Post date:** [July 13, 2026, 8:18pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/143 "2026-07-13T20:18:46Z")

</div>

Here is the DP Table. I’m not using the IR parts (the device can use IR to control other devices).

Smart IR  
DP 101 temp\_current value 256   
DP 102 humidity\_value value 61   
DP 201 ir\_send string {“control”:“study\_exit”}   
DP 202 ir\_study\_code raw   
DP — va\_temperature Integer 256 -200–800 step 1 ℃  
DP — va\_humidity Integer 61 0–100 step 1 %

---

<div class="post-metadata">

**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 13, 2026, 8:32pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/144 "2026-07-13T20:32:25Z")

</div>

The temperature (DP 101) and humidity (DP 102) sensors work fine with the Generic Driver. Use this dp\_config:

```json
[
  {"dp":101,"cap":"measure_temperature","scale":0.1,"readonly":true,"label":"Temperature","unit":"°C"},
  {"dp":102,"cap":"measure_humidity","readonly":true,"label":"Humidity","unit":"%"}
]

```

Note: the raw temperature value is ×10 (256 = 25.6 °C), so `scale: 0.1` is needed.

The IR functionality (DP 201 `ir_send` / DP 202 `ir_study_code`) is not supported by the Generic Driver. DP 202 uses a binary `raw` type that no Homey capability can handle, and DP 201 sends arbitrary JSON strings which can’t be represented in a standard capability. A dedicated IR driver would be needed for those features.

---

<div class="post-metadata">

**Author:** ![Meruem](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Meruem](https://community.homey.app/u/Meruem)\
**Post date:** [July 14, 2026, 5:45pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/145 "2026-07-14T17:45:17Z")

</div>

Hi @Andi. First of all, thank you for this great app! A lot of devices are automatically discovered and works great!

I have a Tuya Thermostat that is a temperature/humidity sensor with clock but also has Multiple Devices IR. So I created the AC IR, it shows in the Developer Plataform as an “Real Device” with it’s own code different from the thermostat device, but the DP gathered by the Tuya Local didn’t work…  
Here is what I got from the query properties from this device (The Air Conditioner IR created in Tuya App).

> **AC IR Device Query Properties**
>
> {  
> “result”: {  
> “properties”: [  
> {  
> “code”: “control”,  
> “custom\_name”: “”,  
> “dp\_id”: 1,  
> “time”: 1667338507436,  
> “type”: “enum”,  
> “value”: “send\_ir”  
> },  
> {  
> “code”: “study\_code”,  
> “custom\_name”: “”,  
> “dp\_id”: 2,  
> “time”: 1667338507436,  
> “type”: “raw”  
> },  
> {  
> “code”: “ir\_code”,  
> “custom\_name”: “”,  
> “dp\_id”: 3,  
> “time”: 1667338507436,  
> “type”: “string”,  
> “value”: “”  
> },  
> {  
> “code”: “key\_code”,  
> “custom\_name”: “”,  
> “dp\_id”: 4,  
> “time”: 1667338507436,  
> “type”: “string”,  
> “value”: “”  
> },  
> {  
> “code”: “key\_code2”,  
> “custom\_name”: “”,  
> “dp\_id”: 5,  
> “time”: 1667338507436,  
> “type”: “string”,  
> “value”: “”  
> },  
> {  
> “code”: “key\_code3”,  
> “custom\_name”: “”,  
> “dp\_id”: 6,  
> “time”: 1667338507436,  
> “type”: “string”,  
> “value”: “”  
> },  
> {  
> “code”: “key\_study”,  
> “custom\_name”: “”,  
> “dp\_id”: 7,  
> “time”: 1667338507436,  
> “type”: “raw”  
> },  
> {  
> “code”: “key\_study2”,  
> “custom\_name”: “”,  
> “dp\_id”: 8,  
> “time”: 1667338507436,  
> “type”: “raw”  
> },  
> {  
> “code”: “key\_study3”,  
> “custom\_name”: “”,  
> “dp\_id”: 9,  
> “time”: 1667338507436,  
> “type”: “raw”  
> },  
> {  
> “code”: “delay\_time”,  
> “custom\_name”: “”,  
> “dp\_id”: 10,  
> “time”: 1667338507436,  
> “type”: “value”,  
> “value”: 0  
> },  
> {  
> “code”: “key\_code4”,  
> “custom\_name”: “”,  
> “dp\_id”: 11,  
> “time”: 1667338507436,  
> “type”: “string”,  
> “value”: “”  
> },  
> {  
> “code”: “key\_study4”,  
> “custom\_name”: “”,  
> “dp\_id”: 12,  
> “time”: 1667338507436,  
> “type”: “raw”  
> },  
> {  
> “code”: “type”,  
> “custom\_name”: “”,  
> “dp\_id”: 13,  
> “time”: 1667338507436,  
> “type”: “value”,  
> “value”: 0  
> },  
> {  
> “code”: “switch\_power”,  
> “custom\_name”: “”,  
> “dp\_id”: 101,  
> “time”: 1783492361000,  
> “type”: “bool”,  
> “value”: false  
> },  
> {  
> “code”: “mode”,  
> “custom\_name”: “”,  
> “dp\_id”: 102,  
> “time”: 1783492361000,  
> “type”: “enum”,  
> “value”: “0”  
> },  
> {  
> “code”: “temperature”,  
> “custom\_name”: “”,  
> “dp\_id”: 103,  
> “time”: 1783492361000,  
> “type”: “value”,  
> “value”: 25  
> },  
> {  
> “code”: “fan”,  
> “custom\_name”: “”,  
> “dp\_id”: 104,  
> “time”: 1783492361000,  
> “type”: “enum”,  
> “value”: “1”  
> },  
> {  
> “code”: “swing”,  
> “custom\_name”: “”,  
> “dp\_id”: 105,  
> “time”: 1667338507436,  
> “type”: “bool”,  
> “value”: false  
> },  
> {  
> “code”: “ir\_send”,  
> “custom\_name”: “”,  
> “dp\_id”: 201,  
> “time”: 1667338507436,  
> “type”: “string”,  
> “value”: “”  
> },  
> {  
> “code”: “ir\_study\_code”,  
> “custom\_name”: “”,  
> “dp\_id”: 202,  
> “time”: 1667338507436,  
> “type”: “raw”  
> }  
> ]  
> },  
> “success”: true,  
> “t”: 1784050314211,  
> “tid”: “e7e0eda97fa911f1976f5ae95710cd15”  
> }

Is it possible to control this device? I used the IP from the Thermostat and it connected. If you need any more details just ask me. Thanks!

---

<div class="post-metadata">

**Author:** ![Luca\_Farronato](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/luca_farronato/32/169354_2.png) [@Luca\_Farronato](https://community.homey.app/u/Luca_Farronato)\
**Post date:** [July 14, 2026, 6:38pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/146 "2026-07-14T18:38:52Z")

</div>

My DP Config looks more or less like this. I try to modify it with your suggestions but still not working. I need to reconnect the device every xx minutes using a flow to get T and RH updated.

Maybe my device don’t work well locally and need to go through the cloud.

---

<div class="post-metadata">

**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 14, 2026, 8:18pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/147 "2026-07-14T20:18:55Z")

</div>

Hi Luca - How does you reconnect flow look like to get the data?

---

<div class="post-metadata">

**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 14, 2026, 8:25pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/148 "2026-07-14T20:25:20Z")

</div>

Hi Meruem

Could you please set the device in Tuya Cloud to use DP Instructions and afterwards share the DP specification? In **Settings → ☁ Cloud Lookup** → click the device name → **Copy DP Table** and paste it here.

---

<div class="post-metadata">

**Author:** ![Meruem](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Meruem](https://community.homey.app/u/Meruem)\
**Post date:** [July 14, 2026, 8:52pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/149 "2026-07-14T20:52:42Z")

</div>

Hi @Andi, when you say Tuya Cloud is the Homey Official Tuya Cloud App? It doesn’t appear in Tuya Cloud App. It works in SmartThings integration with Tuya and also in Alexa integration with Tuya.  
Is there any information I can get from Tuya Developer Plataform?

---

<div class="post-metadata">

**Author:** ![Luca\_Farronato](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/luca_farronato/32/169354_2.png) [@Luca\_Farronato](https://community.homey.app/u/Luca_Farronato)\
**Post date:** [July 14, 2026, 8:52pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/150 "2026-07-14T20:52:52Z")

</div>

![Screenshot 2026-07-14 alle 22.52.12](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/a/0a514102549e3faec52c498f7679c834d7261ef6.png)

---

<div class="post-metadata">

**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 14, 2026, 8:54pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/151 "2026-07-14T20:54:19Z")

</div>

My bad - I mean the [Tuya Developer Platform](https://platform.tuya.com/)

---

<div class="post-metadata">

**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 14, 2026, 9:22pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/152 "2026-07-14T21:22:26Z")

</div>

Could you please check if the built-in function works in the new TEST version: [Tuya Local | Homey](https://homey.app/a/com.tuyalocal/test/)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/6/46934b1cf1d582ae590a05a98728f545269eb14d.png)

---

<div class="post-metadata">

**Author:** ![Gerald\_Delhaisse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gerald_delhaisse/32/80408_2.png) [@Gerald\_Delhaisse](https://community.homey.app/u/Gerald_Delhaisse)\
**Post date:** [July 15, 2026, 7:38am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/153 "2026-07-15T07:38:07Z")

</div>

Hello, I’m trying to connect an exhaust fan controller. I’ve managed to add it to Homey as a fan, but it doesn’t respond to commands or Flows. I wanted to try adding it as a generic device (it isn’t sold as a Tuya device, so I suspect the device type might be wrong), but I don’t know how to check how it’s recognized within Tuya; it has various sensors (humidity, temperature) for adjusting its speed, but I don’t use them. I just want to adjust the speed from 1 to 10. Do you have any ideas?

---

<div class="post-metadata">

**Author:** ![Gerald\_Delhaisse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gerald_delhaisse/32/80408_2.png) [@Gerald\_Delhaisse](https://community.homey.app/u/Gerald_Delhaisse)\
**Post date:** [July 15, 2026, 8:47am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/154 "2026-07-15T08:47:54Z")

</div>

![Capture d’écran 2026-07-15 104438](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/5/e5a7dc6a285a6a3f01c1bf44741de650a1f94e70.jpeg)

```auto

```

When looking on the Tuya platform, I see it is indeed listed as a fan, but I gather the controls are basic (on/off), whereas in the Tuya app I can actually adjust the speeds. I’m a bit lost—maybe I just don’t get it 😃

---

<div class="post-metadata">

**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 15, 2026, 9:52am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/155 "2026-07-15T09:52:40Z")

</div>

You might need to change the instruction set from ‘Standard Instruction Set’ to ‘DP Instruction Set’ in the Tuya IoT Portal. Refer to [my earlier post](https://community.homey.app/t/app-pro-tuya-local/154077/85) above.

It seems that the standard set only included the on/off control of your device.

---

<div class="post-metadata">

**Author:** ![Gerald\_Delhaisse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gerald_delhaisse/32/80408_2.png) [@Gerald\_Delhaisse](https://community.homey.app/u/Gerald_Delhaisse)\
**Post date:** [July 15, 2026, 10:13am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/156 "2026-07-15T10:13:54Z")

</div>

Thanks for the tip. I’d seen that and tried it this morning, so you’re confirming it might help. Even though the on/off didn’t work—not even in standard mode—I’ll test it when I get home.

---

<div class="post-metadata">

**Author:** ![Luca\_Farronato](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/luca_farronato/32/169354_2.png) [@Luca\_Farronato](https://community.homey.app/u/Luca_Farronato)\
**Post date:** [July 15, 2026, 5:16pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/157 "2026-07-15T17:16:00Z")

</div>

With the test version seems to work. I’m using 3 minutes as auto-reconnect parameter.

Temperature a Humidity change very slowly. So for me 3 minutes of delay is not a problem.

---

<div class="post-metadata">

**Author:** ![Meruem](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@Meruem](https://community.homey.app/u/Meruem)\
**Post date:** [July 15, 2026, 6:42pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/158 "2026-07-15T18:42:27Z")

</div>

In Tuya Developer Plataform I can’t see this Settings → Cloud Lookup.  
What I can see that it seems like what you want was what I sent in the other message:

> **AC IR Device Query Properties**
>
> {  
> “result”: {  
> “properties”: [  
> {  
> “code”: “control”,  
> “custom\_name”: “”,  
> “dp\_id”: 1,  
> “time”: 1667338507436,  
> “type”: “enum”,  
> “value”: “send\_ir”  
> },  
> {  
> “code”: “study\_code”,  
> “custom\_name”: “”,  
> “dp\_id”: 2,  
> “time”: 1667338507436,  
> “type”: “raw”  
> },  
> {  
> “code”: “ir\_code”,  
> “custom\_name”: “”,  
> “dp\_id”: 3,  
> “time”: 1667338507436,  
> “type”: “string”,  
> “value”: “”  
> },  
> {  
> “code”: “key\_code”,  
> “custom\_name”: “”,  
> “dp\_id”: 4,  
> “time”: 1667338507436,  
> “type”: “string”,  
> “value”: “”  
> },  
> {  
> “code”: “key\_code2”,  
> “custom\_name”: “”,  
> “dp\_id”: 5,  
> “time”: 1667338507436,  
> “type”: “string”,  
> “value”: “”  
> },  
> {  
> “code”: “key\_code3”,  
> “custom\_name”: “”,  
> “dp\_id”: 6,  
> “time”: 1667338507436,  
> “type”: “string”,  
> “value”: “”  
> },  
> {  
> “code”: “key\_study”,  
> “custom\_name”: “”,  
> “dp\_id”: 7,  
> “time”: 1667338507436,  
> “type”: “raw”  
> },  
> {  
> “code”: “key\_study2”,  
> “custom\_name”: “”,  
> “dp\_id”: 8,  
> “time”: 1667338507436,  
> “type”: “raw”  
> },  
> {  
> “code”: “key\_study3”,  
> “custom\_name”: “”,  
> “dp\_id”: 9,  
> “time”: 1667338507436,  
> “type”: “raw”  
> },  
> {  
> “code”: “delay\_time”,  
> “custom\_name”: “”,  
> “dp\_id”: 10,  
> “time”: 1667338507436,  
> “type”: “value”,  
> “value”: 0  
> },  
> {  
> “code”: “key\_code4”,  
> “custom\_name”: “”,  
> “dp\_id”: 11,  
> “time”: 1667338507436,  
> “type”: “string”,  
> “value”: “”  
> },  
> {  
> “code”: “key\_study4”,  
> “custom\_name”: “”,  
> “dp\_id”: 12,  
> “time”: 1667338507436,  
> “type”: “raw”  
> },  
> {  
> “code”: “type”,  
> “custom\_name”: “”,  
> “dp\_id”: 13,  
> “time”: 1667338507436,  
> “type”: “value”,  
> “value”: 0  
> },  
> {  
> “code”: “switch\_power”,  
> “custom\_name”: “”,  
> “dp\_id”: 101,  
> “time”: 1783492361000,  
> “type”: “bool”,  
> “value”: false  
> },  
> {  
> “code”: “mode”,  
> “custom\_name”: “”,  
> “dp\_id”: 102,  
> “time”: 1783492361000,  
> “type”: “enum”,  
> “value”: “0”  
> },  
> {  
> “code”: “temperature”,  
> “custom\_name”: “”,  
> “dp\_id”: 103,  
> “time”: 1783492361000,  
> “type”: “value”,  
> “value”: 25  
> },  
> {  
> “code”: “fan”,  
> “custom\_name”: “”,  
> “dp\_id”: 104,  
> “time”: 1783492361000,  
> “type”: “enum”,  
> “value”: “1”  
> },  
> {  
> “code”: “swing”,  
> “custom\_name”: “”,  
> “dp\_id”: 105,  
> “time”: 1667338507436,  
> “type”: “bool”,  
> “value”: false  
> },  
> {  
> “code”: “ir\_send”,  
> “custom\_name”: “”,  
> “dp\_id”: 201,  
> “time”: 1667338507436,  
> “type”: “string”,  
> “value”: “”  
> },  
> {  
> “code”: “ir\_study\_code”,  
> “custom\_name”: “”,  
> “dp\_id”: 202,  
> “time”: 1667338507436,  
> “type”: “raw”  
> }  
> ]  
> },  
> “success”: true,  
> “t”: 1784050314211,  
> “tid”: “e7e0eda97fa911f1976f5ae95710cd15”  
> }

Also this is what I see in Cloud → Project → Debug Device

> **Standard Instruction Set**
>
> | **Code** | **Type** | **Values** |
> | --- | --- | --- |
> | F | ENUM | |
> 
> ```auto
> {
> "min": 0,
> "max": 3,
> "scale": 0,
> "step": 1,
> "type": "Integer"
> }
> 
> ```
> 
> | M | ENUM | |
> | --- | --- | --- |
> | | | |
> 
> ```auto
> {
> "min": 0,
> "max": 4,
> "scale": 0,
> "step": 1,
> "type": "Integer"
> }
> 
> ```
> 
> | PowerOff | STRING | |
> | --- | --- | --- |
> | | | |
> 
> ```auto
> "PowerOff"
> 
> ```
> 
> | PowerOn | STRING | |
> | --- | --- | --- |
> | | | |
> 
> ```auto
> "PowerOn"
> 
> ```
> 
> | T | ENUM | |
> | --- | --- | --- |
> | | | |
> 
> ```auto
> {
> "min": 16,
> "max": 30,
> "scale": 0,
> "step": 1,
> "type": "Integer"
> }
> 
> ```

> **Standard Status Set**
>
> | **Code** | **Type** | **Values** |
> | --- | --- | --- |
> | wind | ENUM | |
> 
> ```auto
> {
> "min": 0,
> "max": 3,
> "scale": 0,
> "step": 1,
> "type": "Integer"
> }
> 
> ```
> 
> | mode | ENUM | |
> | --- | --- | --- |
> | | | |
> 
> ```auto
> {
> "min": 0,
> "max": 4,
> "scale": 0,
> "step": 1,
> "type": "Integer"
> }
> 
> ```
> 
> | power | BOOLEAN | |
> | --- | --- | --- |
> | | | |
> 
> ```auto
> {}
> 
> ```
> 
> | temp | ENUM | |
> | --- | --- | --- |
> | | | |
> 
> ```auto
> {
> "min": 16,
> "max": 30,
> "scale": 0,
> "step": 1,
> "type": "Integer"
> }
> 
> ```

Also found this in **Configure Control Instruction Mode** → **Table of Instructions** of the Device:

> **Table of Instructions -\> Standard Instruction**
>
> | **DP Instruction** | **Standard Instruction** |
> | --- | --- |
> | control | - |
> | study\_code | - |
> | ir\_code | - |
> | key\_code | - |
> | key\_code2 | - |
> | key\_code3 | - |
> | key\_study | - |
> | key\_study2 | - |
> | key\_study3 | - |
> | delay\_time | - |
> | key\_code4 | - |
> | key\_study4 | - |
> | type | - |
> | switch\_power | - |
> | mode | - |
> | temperature | - |
> | fan | - |
> | swing | - |
> | ir\_send | - |
> | ir\_study\_code | - |

---

<div class="post-metadata">

**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 15, 2026, 7:16pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/159 "2026-07-15T19:16:30Z")

</div>

## What to test first

Try the **Generic driver** with this `dp_config`:

```json
[
  {"dp": 101, "cap": "onoff", "label": "Power", "settable": true},
  {"dp": 103, "cap": "generic_number_1", "label": "Temperature", "settable": true, "min": 16, "max": 30, "step": 1},
  {"dp": 102, "cap": "generic_switch_1", "label": "Mode", "settable": true},
  {"dp": 104, "cap": "generic_switch_2", "label": "Fan Speed", "settable": true},
  {"dp": 105, "cap": "generic_switch_3", "label": "Swing", "settable": true}
]

```

**If SET commands to DPs 101–105 work via LAN** → the device firmware handles IR translation locally. You’d get full AC control with no state feedback (IR is one-way).

**If they don’t work** → the translation lives in the cloud. LAN-only is not possible for high-level control.

* * *

## State feedback warning

Either way, **GET will return error 900** (which the app now handles silently). The blaster doesn’t know what state your AC is actually in — it just fires IR codes. You’ll see the last commanded state, not the actual AC state.

* * *

## If LAN control works: a dedicated driver would be better

The Generic driver can get you there, but an `ir_ac` driver would be cleaner — mapping to proper Homey capabilities (`onoff`, `target_temperature`, `thermostat_mode`, `fan_mode`) with the right ranges and no-feedback handling. Worth building if it turns out DPs 101–105 respond to LAN SET commands.

**Start with the Generic driver and test a DP 101 SET first.** If the AC responds, we know it works locally and can build a proper driver.

---

<div class="post-metadata">

**Author:** ![Robin\_Al](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robin_al/32/169534_2.png) [@Robin\_Al](https://community.homey.app/u/Robin_Al)\
**Post date:** [July 15, 2026, 9:36pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/160 "2026-07-15T21:36:59Z")

</div>

Hi Andi !

**BCM700D-TY01 curtain motors connect but do not respond**

Homey Pro 2026 — Tuya Local v1.0.93  
Model: BCM700D-TY01  
Category: cl  
Product ID: p1fiefpamvaqek4u  
Protocol: 3.3  
Control DP: 102  
Position DP: 2  
Other detected DPs: 101 = 6, 103 = false

IP, Device ID and Local Key have been individually verified for all four motors. The Local Keys were refreshed through Cloud Lookup.

All four motors are controlled instantly through Tuya Smart, but none responds to commands from Homey.

After restarting Tuya Local, the devices initially report “Connected”, then repeatedly disconnect with:

`Timeout waiting for status response from device id ...`

Earlier HMAC mismatch errors disappeared after refreshing the Local Key and selecting protocol 3.3.

Could this BCM700D-TY01 firmware require a different status command, push-only operation, or a specific driver profile?

---

<div class="post-metadata">

**Author:** ![Amersfoort](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@Amersfoort](https://community.homey.app/u/Amersfoort)\
**Post date:** [July 16, 2026, 1:49pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/161 "2026-07-16T13:49:12Z")

</div>

Have you already tried other protocols?

---

<div class="post-metadata">

**Author:** ![Robin\_Al](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robin_al/32/169534_2.png) [@Robin\_Al](https://community.homey.app/u/Robin_Al)\
**Post date:** [July 16, 2026, 1:52pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/162 "2026-07-16T13:52:12Z")

</div>

Yes.

The % control work correctly, but the button control doesn’t work.

[Previous page](https://community.homey.app/t/app-pro-tuya-local/154077.md?page=7)

[Next page](https://community.homey.app/t/app-pro-tuya-local/154077.md?page=9)