# \[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:** 19

<div class="post-metadata">

**Author:** ![Jan-Feijen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-feijen/32/47915_2.png) [@Jan-Feijen](https://community.homey.app/u/Jan-Feijen)\
**Post date:** [September 2, 2026, 10:43am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/366 "2026-09-02T10:43:52Z")

</div>

Hi Andi,

I’ve tested everything and it works perfectly.

Having the current Silent Mode state visible as a switch on the device page is absolutely fine. Actually, it’s even better, as I can control it directly from there as well.

Thanks a lot for all your help and for making the changes/updates to the app. It’s really appreciated!

And I bought you some beers as a small thank-you. 🍻

Jan

---

<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:** [September 2, 2026, 2:59pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/367 "2026-09-02T14:59:21Z")

</div>

Hi Jan,

That’s great to hear — thanks for testing it so quickly, and for the beers. Much appreciated.

And thank you for the reports themselves. Three fixes in the app came directly out of what you sent.

Andi

---

<div class="post-metadata">

**Author:** ![Stijn\_Van\_Heeswijk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stijn_van_heeswijk/32/73136_2.png) [@Stijn\_Van\_Heeswijk](https://community.homey.app/u/Stijn_Van_Heeswijk)\
**Post date:** [September 2, 2026, 6:19pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/368 "2026-09-02T18:19:17Z")

</div>

Hi Andi,  
I’m trying to get my Fairland pool heat pump working with Tuya Local.  
Jan has been helping me with the configuration, as my heat pump seems to be quite similar to his, but we’ve found an important difference in the Smart/Silence implementation.

My heat pump is a Fairland/Poolstyle PSL-150-0252 (6 kW).  
Most functions are already working correctly.  
The relevant DPs are:

- DP101 = On/Off (boolean)
- DP102 = Smart/Silence (enum/string)
- DP103 = Current water temperature
- DP105 = Power level %
- DP106 = Operating mode (warm, etc.)
- DP107 = Target temperature
- DP108/109 = Min/Max target temperature
- DP110 = Fault

The main difference compared with Jan’s Fairland is DP102.  
I tested this by manually switching between Smart and Silence on the heat pump and checking the DP values:

- Smart → DP102 = smart
- Silence → DP102 = silence

So on my heat pump Smart/Silence is an enum/string DP, rather than a boolean DP. Jan’s heat pump uses DP117 with boolean values for the same function.  
In the current Tuya Local Heat Pump settings, Silent Mode seems to expect a boolean DP, using the “On this data point, true means…” setting.

Would it be possible to also support an enum/string DP for Silent Mode, for example:

- Silent Mode DP: 102
- Smart value: smart
- Silence value: silence

On/Off, current temperature and target temperature are already working correctly.

Thanks for your help!

---

<div class="post-metadata">

**Author:** ![Kringloper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kringloper/32/70714_2.png) [@Kringloper](https://community.homey.app/u/Kringloper)\
**Post date:** [September 4, 2026, 6:41am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/369 "2026-09-04T06:41:42Z")

</div>

Some troubles to get my new fancoils to work with Tuya local. At the first attempt one of the fancoils did connect. I could control it, but the second one wouldn’t. So i removed the working one to check if it had to do something with multiple instances. But now both don’t get connected anymore. The first attempt was adding it as a heater, later i tried airconditioner because it has also modes for couling, heating and dehydrating. But also going back to heater doesn’t change things.

 ![Scherm­afbeelding 2026-09-04 om 08.18.30](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/d/ed975a41de01f5a8317b4b341e36e2bee45cd187.png)

I the configuration i can retrieve the devices, even see changes made in the tuya app reflected in this screen. But ECONNRESET is the message as soon as i install the device in homey.  
Tried all the protocols manualy. Protocol 3.3 seems to connect fine during setup, but also results in ECONNRESET as soon as connected as a new device.

The scanning for protocol says it can reach the IP, port 6668 is known.

Not sure how to continue from here on.

**Tuya Local 1.0.225 — support bundle (1 device)**

> **Support bundle**
>
> ```auto
> Tuya Local v1.0.225 — support bundle
> Generated: 2026-09-04T06:28:13.311Z
> App started: 2026-09-04T05:54:41.820Z (running 33m 31s)
> Homey: 13.4.1
> Cloud lookup: configured (eu)
> ========================================================================
> 
> DEVICE Air Conditioner sk
> driver air_conditioner
> model Ventilconvettore (product 5dgguakbmhwzwiko)
> device id bf0066…
> available no
> protocol configured 3.2, connected 3.3 ip 192.168.2.70
> status Disconnected · last seen 04-09-2026, 08:25:38 · poll 30s
> history 21 connections since app start · up 33s total · avg 2s · longest 2s
> packets 0 received · data ever received: NO
> DP mapping
> dp_anion 0
> dp_child_lock 0
> dp_countdown_left 0
> dp_countdown_timer 0
> dp_current_temp 3
> dp_eco 0
> dp_fan_speed 5
> dp_fault 20
> dp_mode 4
> dp_onoff 1
> dp_sleep 0
> dp_swing 0
> dp_swing_h 0
> dp_target_temp 2
> other settings
> alarm_grace_seconds 30
> command_gap_ms 100
> fan_speed_values "auto,low,medium,high,turbo"
> fire_and_forget true
> lock_protocol false
> mode_values "cool,heat,auto,dry,fan"
> offline_grace_seconds 60
> reconnect_interval 0
> swing_values "off,on"
> temp_divisor 1
> temp_max 30
> temp_min 16
> temp_step 1
> live DPs none received yet
> cloud spec code / dp / type / value / range
> switch 1 Boolean null             
> temp_set 2 Integer null 0-40 ℃
> temp_current 3 value null -20-50 ℃
> mode 4 enum null             
> fan_speed_enum 5 enum null             
> fault 6 bitmap null             
> ------------------------------------------------------------------------
> 
> LOG — warnings, errors and connection events, newest first
> 23 of 23 distinct messages from 300 of 500 entries. Repeats are folded into one line. The device sections above carry the DP mapping and the live values — please include them when quoting this report.
> 2026-09-04T06:20:39.719Z [WARN] [Air Conditioner sk] 30 failures — trying protocol 3.3 (configured: 3.2)
> 2026-09-04T06:01:01.992Z [WARN] [Air Conditioner sk] All protocol versions tried — reverting to 3.2. None of them produced a reply, so the protocol version is not the cause: check that nothing else holds the device's single local connection (the Tuya app, another integration, or a second entry for the same address).
> 2026-09-04T05:59:38.799Z [WARN] [Air Conditioner sk] 20 failures — trying protocol 3.5 (configured: 3.2)
> 2026-09-04T05:58:17.418Z [WARN] [Air Conditioner sk] 15 failures — trying protocol 3.1 (configured: 3.2)
> 2026-09-04T05:56:55.454Z [WARN] [Air Conditioner sk] 10 failures — trying protocol 3.4 (configured: 3.2)
> 2026-09-04T05:55:29.711Z [WARN] [Air Conditioner sk] 5 failures — trying protocol 3.3 (configured: 3.2) ×4 — 05:51:40, 05:52:55, 05:53:56, 05:55:29
> 2026-09-04T05:50:18.999Z [WARN] [Air Conditioner] 5 failures — trying protocol 3.3 (configured: 3.4)
> 2026-09-04T05:49:28.114Z [WARN] [Air Conditioner sk] 5 failures — trying protocol 3.4 (configured: 3.3)
> 2026-09-04T05:49:07.222Z [WARN] [Air Conditioner sk] Connected and answering keep-alives, but 2 status requests in a row went unanswered and no data has ever arrived on this connection. That combination points at the Local Key or the Device ID, not at the protocol: a keep-alive needs neither, a status request needs both, so a device that answers the first and drops the second is receiving something it cannot decrypt. Re-copy both from the Tuya IoT platform — the Local Key changes every time the device is re-added in the Smart Life app. ×3 — 05:47:05, 05:47:45, 05:49:07
> 2026-09-04T05:46:25.136Z [WARN] [Air Conditioner] All protocol versions tried — reverting to 3.4. None of them produced a reply, so the protocol version is not the cause: check that nothing else holds the device's single local connection (the Tuya app, another integration, or a second entry for the same address).
> 2026-09-04T06:20:43.703Z [WARN] [Air Conditioner sk] Status request failed: Timeout waiting for status response from device id: bf00664084f764c7e1euc0 ×27 since 2026-09-04T05:46:15.374Z
> 2026-09-04T06:25:32.028Z [INFO] [Air Conditioner sk] Connected ×54 since 2026-09-04T05:46:09.862Z
> 2026-09-04T05:45:53.313Z [WARN] [Air Conditioner sk] 20 failures — trying protocol 3.2 (configured: 3.3)
> 2026-09-04T05:46:29.121Z [WARN] [Air Conditioner] Status request failed: Timeout waiting for status response from device id: bfb32516d48812993eireu ×5 — 05:45:19, 05:45:38, 05:45:53, 05:46:09, 05:46:29
> 2026-09-04T05:50:32.871Z [WARN] [Air Conditioner] Disconnected: Error from socket: read ECONNRESET (up 2s, no data received) ×6 — 05:45:15, 05:45:34, 05:45:49, 05:46:05, 05:46:25, 05:50:32
> 2026-09-04T05:50:31.343Z [INFO] [Air Conditioner] Connected ×6 — 05:45:13, 05:45:33, 05:45:48, 05:46:04, 05:46:23, 05:50:31
> 2026-09-04T05:44:58.718Z [WARN] [Air Conditioner] 20 failures — trying protocol 3.2 (configured: 3.4)
> 2026-09-04T06:01:01.992Z [ERROR] [Air Conditioner sk] Connection failed: read ECONNRESET — likely a protocol version mismatch. The app retries the other versions on its own after 5 failed attempts. If it stays offline, set Protocol Version manually in the device settings; 3.3 and 3.4 are the common ones. ×26 since 2026-09-04T05:44:51.496Z
> 2026-09-04T05:50:18.999Z [ERROR] [Air Conditioner] Connection failed: read ECONNRESET — likely a protocol version mismatch. The app retries the other versions on its own after 5 failed attempts. If it stays offline, set Protocol Version manually in the device settings; 3.3 and 3.4 are the common ones. ×8 since 2026-09-04T05:44:41.558Z
> 2026-09-04T05:50:32.870Z [ERROR] [Air Conditioner] Error from socket: read ECONNRESET — likely a protocol version mismatch. The app retries the other versions on its own after 5 failed attempts. If it stays offline, set Protocol Version manually in the device settings; 3.3 and 3.4 are the common ones. ×14 since 2026-09-04T05:44:41.556Z
> 2026-09-04T05:44:37.618Z [WARN] [Air Conditioner sk] 15 failures — trying protocol 3.5 (configured: 3.3)
> 2026-09-04T06:25:33.556Z [WARN] [Air Conditioner sk] Disconnected: Error from socket: read ECONNRESET (up 2s, no data received) ×55 since 2026-09-04T05:44:37.618Z
> 2026-09-04T06:25:33.555Z [ERROR] [Air Conditioner sk] Error from socket: read ECONNRESET — likely a protocol version mismatch. The app retries the other versions on its own after 5 failed attempts. If it stays offline, set Protocol Version manually in the device settings; 3.3 and 3.4 are the common ones. ×81 since 2026-09-04T05:44:37.617Z
> 
> ```

---

<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:** [September 4, 2026, 3:32pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/370 "2026-09-04T15:32:24Z")

</div>

@Kringloper

Two things to check:

In the pairing screen, press Scan network. Each device found is listed with the Device ID it broadcasts. Compare the ID next to 192.168.2.70 with the Device ID in your device’s settings. If they differ, that’s it — correct the IP (or the ID and key) so the pair belongs together.  
Give both fancoils a fixed IP in your router. Two Tuya devices swapping addresses over DHCP produces exactly this, intermittently and confusingly.  
Also, if you re-added either fancoil in the Smart Life app at any point, the Local Key changed. Re-fetch both under Cloud Lookup.

Two settings to correct while you’re there, independent of the connection:

Fault DP is set to 20; your device reports fault on DP 6.  
Fan speed values is auto,low,medium,high,turbo, but your device reports superlow. A Tuya device silently discards a value it doesn’t know, so fan speed commands would fail without any error. Set it to match what your device actually offers — superlow first, then whatever else it reports.  
Send another bundle after the scan if it still won’t connect, and include what the scan showed for that address.

Andi

---

<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:** [September 4, 2026, 3:51pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/371 "2026-09-04T15:51:52Z")

</div>

@Stijn_Van_Heeswijk

Hi Stijn,

Yes — and your measurement is what made it straightforward. Switching at the pump and watching DP 102 is exactly the right way to establish it.

It’s in the next test version. There’s **no new choice to make** : the app tells a named silent mode from a switched one by what the device reports, so your DP 102 and Jan’s DP 117 both work without saying which kind you have.

→ [Tuya Local | Homey](https://homey.app/a/com.tuyalocal/test/)

Your settings:

```auto
Silent Mode DP 102
Silent mode values smart,silence

```

The values setting is new — the normal mode first, the quiet one second. Case doesn’t matter. On a boolean pump like Jan’s it’s ignored.

If your pump ever reports a name that isn’t in that list, the app now says so in the log rather than dropping the command silently — that’s the trap that cost Jan a while on his mode list.

Two other things from your DP list worth setting while you’re there:

- **Fault DP** → `110`
- **Mode values** → whatever DP 106 actually reports. Check DP Debug for the exact spelling; a Tuya device discards a mode name it doesn’t recognise without any error, which looks exactly like the mode picker doing nothing.

DP 108/109 (min/max target) aren’t read from the device — the driver uses the `temp_min` / `temp_max` settings instead, so just enter the same numbers there.

Thanks to you and Jan both for working this out between you before it reached me.

Andi

---

<div class="post-metadata">

**Author:** ![Kringloper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kringloper/32/70714_2.png) [@Kringloper](https://community.homey.app/u/Kringloper)\
**Post date:** [September 5, 2026, 5:57am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/372 "2026-09-05T05:57:03Z")

</div>

The mixup of the two devices was the problem. I made fixed ip addresses but at that moment i registered the wrong name in the dhcp table. So every time i made the combination of the fixed ip address and the device it was the wrong combination. It is all working now. Thanks.

---

<div class="post-metadata">

**Author:** ![Oleh\_Nevynnyi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oleh_nevynnyi/32/173740_2.png) [@Oleh\_Nevynnyi](https://community.homey.app/u/Oleh_Nevynnyi)\
**Post date:** [September 5, 2026, 9:36am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/373 "2026-09-05T09:36:51Z")

</div>

Hi Andy,

Any idea what I should do with this charger?

---

<div class="post-metadata">

**Author:** ![Stijn\_Van\_Heeswijk](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stijn_van_heeswijk/32/73136_2.png) [@Stijn\_Van\_Heeswijk](https://community.homey.app/u/Stijn_Van_Heeswijk)\
**Post date:** [September 5, 2026, 11:28am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/374 "2026-09-05T11:28:14Z")

</div>

**Hi Andy,**

Thank you for updating the app. @Jan-Feijen was a tremendous help in providing you with the right information. It works perfectly now!

I don’t have time at the moment to continue building the flows, but I’ll get back to that later.

**Kind regards,**  
Stijn

---

<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:** [September 5, 2026, 11:45am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/375 "2026-09-05T11:45:46Z")

</div>

Hi Oleh

Could you please create a support bundle and send it to me?

 ![](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/c/3c22cb5c3ab81e56faac5fd75e8dcdc7fb95a36c.png)

---

<div class="post-metadata">

**Author:** ![Jan-Feijen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jan-feijen/32/47915_2.png) [@Jan-Feijen](https://community.homey.app/u/Jan-Feijen)\
**Post date:** [September 5, 2026, 12:39pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/376 "2026-09-05T12:39:08Z")

</div>

@Stijn_Van_Heeswijk, great to hear and let me know if help needed with the flows.

BR Jan

---

<div class="post-metadata">

**Author:** ![Oleh\_Nevynnyi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/oleh_nevynnyi/32/173740_2.png) [@Oleh\_Nevynnyi](https://community.homey.app/u/Oleh_Nevynnyi)\
**Post date:** [September 5, 2026, 4:28pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/377 "2026-09-05T16:28:51Z")

</div>

Hi Andi,

I am already did it but there a lot of text.. should I put everything there or send it in different way?

Now I have it in txt file, but can’t attach to this chat.

---

<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:** [September 5, 2026, 9:52pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/378 "2026-09-05T21:52:16Z")

</div>

Hi Oleh - send it directly to me as message.

Andi

---

<div class="post-metadata">

**Author:** ![Anthony\_Cherpeau](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anthony_cherpeau/32/172641_2.png) [@Anthony\_Cherpeau](https://community.homey.app/u/Anthony_Cherpeau)\
**Post date:** [September 6, 2026, 1:09pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/379 "2026-09-06T13:09:24Z")

</div>

Hi Andy,

I have a Voldt EV charger connected to Homey using Tuya Local.

I use **DP14** to control the charging mode. Its possible values are:

- `charge_now`
- `charge_schedule`
- `charge_pct`
- `charge_energy`
- `charge_delay`

I have set the charger to `charge_schedule` so it does not start charging immediately when I plug in my car.

My HomeyScript calculates the required charging start time to reach **80% at 04:30**.

The problem is that the Homey **Start charging** card does not work while DP14 is set to `charge_schedule`. I need to change DP14 to `charge_now` first.

**Would it be possible to add Flow cards for DP14, for example:**

**WHEN:** DP14 = …  
**AND:** DP14 = …  
**THEN:** Set DP14 = …

With the five possible values listed above.

This would allow Homey to fully control the charging mode.

Thank you very much for all the work you have already done on Tuya Local and for your help with this issue. I really appreciate it!

---

<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:** [September 6, 2026, 1:21pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/380 "2026-09-06T13:21:42Z")

</div>

Thanks — this was a good catch, and the fix turned out to be smaller than expected.

The charging mode has been a proper capability all along (`ev_work_mode`, with exactly your five values). What was missing is that Homey only generates Flow cards automatically for its own capabilities — a custom one gets none. So the picker was reachable by hand and by nothing else.

**Three cards are in the next test version:** [Tuya Local | Homey](https://homey.app/a/com.tuyalocal/test/)

| | |
| --- | --- |
| **WHEN** | Charging mode changed — with `mode` and `previous mode` tokens |
| **AND** | Charging mode is / is not … |
| **THEN** | Set charging mode to … |

All five values are there: Charge Now, Charge to %, Charge kWh, Scheduled, Delayed Start.

One difference from your sketch: the trigger has no mode dropdown, it carries tokens instead. That is how the app’s five other mode-changed triggers work, and `WHEN mode changed` + `AND mode is Scheduled` gives you the same flow. The trigger also fires when you switch the mode at the charger itself or in the Voldt app, not just from Homey.

For your case the flow becomes: **THEN Set charging mode → Charge Now** , then **Start charging**. Your script keeps deciding the time.

One thing to check on the first run: not every charger implements every mode it advertises, and one it does not know is discarded without an error. If a mode appears to do nothing, the DP Debug tab shows what DP 14 actually reports back.

---

<div class="post-metadata">

**Author:** ![Anthony\_Cherpeau](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/anthony_cherpeau/32/172641_2.png) [@Anthony\_Cherpeau](https://community.homey.app/u/Anthony_Cherpeau)\
**Post date:** [September 6, 2026, 1:45pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/381 "2026-09-06T13:45:06Z")

</div>

Thank you very much for the quick response and for fixing this so quickly!

I’ve just installed the test version and everything is working perfectly now. I really appreciate how fast you reacted to the issue and how quickly you provided a solution.

Thanks again for your excellent work and responsiveness! 🙏

---

<div class="post-metadata">

**Author:** ![Dietrich\_Kassner](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dietrich_kassner/32/176924_2.png) [@Dietrich\_Kassner](https://community.homey.app/u/Dietrich_Kassner)\
**Post date:** [September 6, 2026, 3:26pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/382 "2026-09-06T15:26:58Z")

</div>

Hello, I just tried your app and I really like the idea of controling the devices localy because this was one idea behind homeys advertising.

I now tryed your app with a multi plug (4 usb ports and 3 normal plugs) but the created device can only switch on and off the whole device and not the different embedet plugs. Is it possible to implement that?

---

<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:** [September 6, 2026, 4:14pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/383 "2026-09-06T16:14:25Z")

</div>

Hi Dietrich

Could you please provide the support bundle (Fix it → Create support bundle) and make sure to setup your account under Cloud Lookup before doing that?

Thank you

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/5/c5b23fb236d8c5046130264f3a940321845a20b4.png)

---

<div class="post-metadata">

**Author:** ![Dietrich\_Kassner](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/dietrich_kassner/32/176924_2.png) [@Dietrich\_Kassner](https://community.homey.app/u/Dietrich_Kassner)\
**Post date:** [September 6, 2026, 6:02pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/385 "2026-09-06T18:02:21Z")

</div>

**Tuya Local 1.0.225 — support bundle (3 devices)**

> **Support bundle**
>
> ```auto
> Tuya Local v1.0.225 — support bundle
> Generated: 2026-09-06T18:01:25.371Z
> App started: 2026-09-03T08:32:54.710Z (running 81h 28m)
> Homey: 13.4.1
> Cloud lookup: configured (eu)
> ========================================================================
> 
> DEVICE Alex Bad
> driver smart_plug
> model Smart plug-EU (product eljrqdagltsgoycp)
> device id bf084c…
> available yes
> protocol configured 3.3, connected 3.3 ip 192.168.13.15
> status Connected · last seen 06.09.26, 20:00:58 · poll 30s
> history 55 connections since app start · up 81h 25m total · avg 1h 28m · longest 6h 36m
> packets 8477 received · 0.03/s while connected · data ever received: yes
> DP mapping
> dp_countdown 9
> dp_current 18
> dp_energy 17
> dp_fault 26
> dp_power 19
> dp_power_factor 0
> dp_relay_status 38
> dp_switch 1
> dp_voltage 20
> other settings
> command_gap_ms 100
> current_scale "0.001"
> fire_and_forget true
> kwh_scale "0.001"
> lock_protocol false
> offline_grace_seconds 60
> power_scale "0.1"
> reconnect_interval 0
> relay_status "memory"
> voltage_scale "0.1"
> live DPs (updated 2026-09-06T18:01:01.831Z)
> DP 1 true boolean
> DP 9 0 number
> DP 17 1 number
> DP 18 0 number
> DP 19 0 number
> DP 20 2344 number
> DP 21 1 number
> DP 22 536 number
> DP 23 28194 number
> DP 24 15438 number
> DP 25 2710 number
> DP 26 0 number
> DP 38 "memory" string
> DP 39 "relay" string
> DP 40 false boolean
> DP 41 "" string
> DP 42 "" string
> DP 44 "" string
> DP 46 false boolean
> cloud spec code / dp / type / value / range
> switch_1 1 Boolean null             
> countdown_1 9 Integer null 0-86400 s
> add_ele 17 value null 0-50000 kW·h
> cur_current 18 value null 0-30000 mA
> cur_power 19 value null 0-80000 W
> cur_voltage 20 value null 0-5000 V
> test_bit 21 value null             
> voltage_coe 22 value null 0-100000000
> electric_coe 23 value null 0-100000000
> power_coe 24 value null 0-1000000000
> electricity_coe 25 value null 0-1000000
> fault 26 bitmap null             
> relay_status 38 Enum null power_off,power_on,last
> light_mode 39 Enum null relay,pos,none
> child_lock 40 Boolean null             
> cycle_time 41 String null             
> random_time 42 String null             
> switch_inching 44 String null             
> overcharge_switch 46 Boolean null             
> ------------------------------------------------------------------------
> 
> DEVICE Smart Plug
> driver smart_plug
> model NX-4473 (product 0oaikegxcfwwfcsr)
> device id bfe198…
> available yes
> protocol configured 3.3, connected 3.3 ip 192.168.13.2
> status Connected · last seen 06.09.26, 20:01:04 · poll 30s
> history 1 connection since app start · up 52s total · avg 52s · longest 52s
> packets 2 received · data ever received: yes
> DP mapping
> dp_countdown 9
> dp_current 0
> dp_energy 0
> dp_fault 0
> dp_power 0
> dp_power_factor 0
> dp_relay_status 38
> dp_switch 1
> dp_voltage 0
> other settings
> command_gap_ms 100
> current_scale "0.001"
> fire_and_forget true
> kwh_scale "0.001"
> lock_protocol false
> offline_grace_seconds 60
> power_scale "0.1"
> reconnect_interval 0
> relay_status "memory"
> voltage_scale "0.1"
> live DPs (updated 2026-09-06T18:00:37.773Z)
> DP 1 true boolean
> DP 2 false boolean
> DP 3 true boolean
> DP 4 false boolean
> DP 9 0 number
> DP 10 0 number
> DP 11 0 number
> DP 12 0 number
> DP 38 "memory" string
> cloud spec code / dp / type / value / range
> switch_1 1 Boolean null             
> switch_2 2 Boolean null             
> switch_3 3 Boolean null             
> switch_4 4 Boolean null             
> countdown_1 9 Integer null 0-86400 s
> countdown_2 10 Integer null 0-86400 s
> countdown_3 11 Integer null 0-86400 s
> countdown_4 12 Integer null 0-86400 s
> relay_status 38 Enum null power_off,power_on,last
> ------------------------------------------------------------------------
> 
> DEVICE Licht Badezimmer
> driver light
> model *NX-4648* (product ohaebnvyrmgx2sh6)
> device id bf9960…
> available yes
> protocol configured 3.3, connected 3.3 ip 192.168.10.8
> status Connected · last seen 06.09.26, 20:01:12 · poll 30s
> history 250 connections since app start · up 81h 15m total · avg 19m 30s · longest 2h 7m
> packets 33826 received · 0.12/s while connected · data ever received: yes
> DP mapping
> dp_brightness 22
> dp_color 24
> dp_color_mode 21
> dp_color_temp 23
> dp_onoff 20
> other settings
> brightness_max 1000
> color_mode_color_val "colour"
> color_mode_white_val "white"
> color_temp_invert false
> color_temp_max 1000
> command_gap_ms 100
> fire_and_forget true
> lock_protocol false
> offline_grace_seconds 60
> power_off_watts 0
> power_on_watts 0
> reconnect_interval 0
> live DPs (updated 2026-09-06T17:48:44.975Z)
> DP 20 false boolean
> DP 21 "white" string
> DP 22 1000 number
> DP 23 500 number
> DP 24 "00dc03a203e8" string
> DP 25 "000e0d0000000000000000c80000" string
> DP 26 0 number
> DP 30 "AAAAAAA=" string
> DP 31 "AAA=" string
> DP 32 "AAA=" string
> DP 209 "AAAA" string
> DP 210 "AAAA" string
> cloud spec code / dp / type / value / range
> switch_led 20 Boolean null             
> work_mode 21 Enum null white,colour,scene,music
> bright_value 22 value null             
> temp_value 23 value null             
> colour_data 24 string null             
> scene_data 25 string null             
> countdown 26 value null             
> music_data 27 Json null             
> control_data 28 Json null             
> rhythm_mode 30 Raw null             
> sleep_mode 31 Raw null             
> wakeup_mode 32 Raw null             
> cycle_timing 209 Raw null             
> random_timing 210 Raw null             
> bright_value_v2 undefined Integer null 10-1000
> temp_value_v2 undefined Integer null 0-1000
> colour_data_v2 undefined Json null             
> scene_data_v2 undefined Json null             
> countdown_1 undefined Integer null 0-86400 s
> ------------------------------------------------------------------------
> 
> LOG — warnings, errors and connection events, newest first
> 120 of 139 distinct messages from 300 of 500 entries. Repeats are folded into one line. The device sections above carry the DP mapping and the live values — please include them when quoting this report.
> 2026-09-06T17:47:38.215Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 2m 42s, 16 packets)
> 2026-09-06T17:37:56.881Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 6m 2s, 39 packets)
> 2026-09-06T17:37:43.523Z [WARN] [Smart Plug] Disconnected: Error from socket: read ECONNRESET (up 20m 0s, 21 packets)
> 2026-09-06T17:31:51.981Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 4m 2s, 27 packets)
> 2026-09-06T17:27:46.312Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 28m 53s, 198 packets)
> 2026-09-06T17:17:40.511Z [WARN] [Smart Plug] Disconnected: Error from socket: read ECONNRESET (up 1h 0m, 62 packets)
> 2026-09-06T16:58:50.937Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 1h 24m, 598 packets)
> 2026-09-06T16:17:36.600Z [WARN] [Smart Plug] Disconnected: Error from socket: read ECONNRESET (up 4m 0s, 5 packets)
> 2026-09-06T16:13:33.268Z [WARN] [Smart Plug] Disconnected: socket closed (up 15m 52s, 17 packets)
> 2026-09-06T15:57:37.691Z [WARN] [Smart Plug] Disconnected: Error from socket: read ECONNRESET (up 10m 0s, 11 packets)
> 2026-09-06T15:54:53.815Z [WARN] [Alex Bad] Disconnected: socket closed (up 11m 3s, 23 packets)
> 2026-09-06T15:47:34.672Z [WARN] [Smart Plug] Disconnected: Error from socket: read ECONNRESET (up 17m 41s, 23 packets)
> 2026-09-06T17:37:43.523Z [ERROR] [Smart Plug] Error from socket: read ECONNRESET — likely a protocol version mismatch. The app retries the other versions on its own after 5 failed attempts. If it stays offline, set Protocol Version manually in the device settings; 3.3 and 3.4 are the common ones. ×5 — 15:47:34, 15:57:37, 16:17:36, 17:17:40, 17:37:43
> 2026-09-06T15:43:48.703Z [WARN] [Alex Bad] Disconnected: socket closed (up 57m 5s, 107 packets)
> 2026-09-06T15:34:51.319Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 22m 2s, 154 packets)
> 2026-09-06T15:29:51.251Z [WARN] [Smart Plug] Disconnected: socket closed (up 17m 32s, 18 packets)
> 2026-09-06T18:00:34.207Z [INFO] [Smart Plug] Connected ×9 since 2026-09-06T15:12:18.875Z
> 2026-09-06T15:05:40.804Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 39m 54s, 280 packets)
> 2026-09-06T14:46:39.995Z [WARN] [Alex Bad] Disconnected: socket closed (up 1h 4m, 112 packets)
> 2026-09-06T14:07:58.091Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 19m 53s, 135 packets)
> 2026-09-06T13:48:01.029Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 5m 2s, 30 packets)
> 2026-09-06T13:42:55.864Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 12m 2s, 79 packets)
> 2026-09-06T13:42:12.595Z [WARN] [Alex Bad] Disconnected: socket closed (up 38m 4s, 68 packets)
> 2026-09-06T13:30:50.911Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 6m 2s, 37 packets)
> 2026-09-06T13:24:45.482Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 18m 33s, 132 packets)
> 2026-09-06T13:06:09.825Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 20m 33s, 142 packets)
> 2026-09-06T13:04:05.991Z [WARN] [Alex Bad] Disconnected: socket closed (up 1h 46m, 201 packets)
> 2026-09-06T17:44:52.576Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 6m 52s, 44 packets) ×2 — 12:45:34, 17:44:52
> 2026-09-06T12:29:23.424Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 1h 25m, 604 packets)
> 2026-09-06T11:17:54.395Z [WARN] [Alex Bad] Disconnected: socket closed (up 2m 22s, 6 packets)
> 2026-09-06T11:15:29.775Z [WARN] [Alex Bad] Disconnected: socket closed (up 1h 22m, 146 packets)
> 2026-09-06T11:04:16.013Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 6m 32s, 38 packets)
> 2026-09-06T14:25:43.734Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 3m 32s, 23 packets) ×2 — 10:57:40, 14:25:43
> 2026-09-06T10:54:04.399Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 2m 22s, 15 packets)
> 2026-09-06T10:48:34.893Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 36m 14s, 258 packets)
> 2026-09-06T10:12:16.941Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 38m 43s, 268 packets)
> 2026-09-06T09:53:41.415Z [WARN] [Alex Bad] Disconnected: socket closed (up 22m 33s, 37 packets)
> 2026-09-06T09:33:30.164Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 16m 43s, 116 packets)
> 2026-09-06T09:31:05.788Z [WARN] [Alex Bad] Disconnected: socket closed (up 20m 3s, 39 packets)
> 2026-09-06T09:16:44.084Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 27m 23s, 248 packets)
> 2026-09-06T09:10:59.672Z [WARN] [Alex Bad] Disconnected: socket closed (up 22s, 2 packets)
> 2026-09-06T09:10:33.717Z [WARN] [Alex Bad] Disconnected: socket closed (up 1h 4m, 120 packets)
> 2026-09-06T08:49:18.184Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 42m 4s, 299 packets)
> 2026-09-06T10:51:39.572Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 3m 2s, 16 packets) ×2 — 08:07:10, 10:51:39
> 2026-09-06T08:06:25.338Z [WARN] [Alex Bad] Disconnected: socket closed (up 3h 7m, 311 packets)
> 2026-09-06T08:04:05.197Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 57m 4s, 397 packets)
> 2026-09-06T07:06:58.476Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 9m 32s, 65 packets)
> 2026-09-06T06:57:23.054Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 1m 32s, 8 packets)
> 2026-09-06T06:55:47.584Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 24m 44s, 170 packets)
> 2026-09-06T06:31:00.363Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 20m 12s, 141 packets)
> 2026-09-06T06:10:45.160Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 1m 2s, 2 packets)
> 2026-09-06T06:09:39.854Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 15m 2s, 100 packets)
> 2026-09-06T05:54:34.393Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 12m 3s, 80 packets)
> 2026-09-06T05:42:28.005Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 15m 2s, 102 packets)
> 2026-09-06T05:27:07.295Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 6m 32s, 44 packets)
> 2026-09-06T05:03:55.913Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 30m 4s, 208 packets)
> 2026-09-06T04:59:29.715Z [WARN] [Alex Bad] Disconnected: socket closed (up 1h 9m, 111 packets)
> 2026-09-06T04:33:48.687Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 10m 32s, 71 packets)
> 2026-09-06T04:23:12.797Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 13m 33s, 93 packets)
> 2026-09-06T04:09:36.908Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 21m 33s, 149 packets)
> 2026-09-06T03:50:52.093Z [WARN] [Alex Bad] Disconnected: socket closed (up 17m 33s, 30 packets)
> 2026-09-06T03:47:45.798Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 3m 42s, 23 packets)
> 2026-09-06T12:38:39.495Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 9m 13s, 64 packets) ×2 — 03:44:00, 12:38:39
> 2026-09-06T03:34:44.541Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 52s, 2 packets)
> 2026-09-06T03:33:48.593Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 47m 3s, 328 packets)
> 2026-09-06T03:33:16.727Z [WARN] [Alex Bad] Disconnected: socket closed (up 1h 0m, 104 packets)
> 2026-09-06T02:46:42.354Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 14m 53s, 100 packets)
> 2026-09-06T02:33:07.936Z [WARN] [Alex Bad] Disconnected: socket closed (up 39m 24s, 64 packets)
> 2026-09-06T02:31:46.569Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 8m 33s, 58 packets)
> 2026-09-06T02:15:05.412Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 13m 3s, 96 packets)
> 2026-09-06T02:23:10.350Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 8m 2s, 51 packets) ×2 — 02:01:58, 02:23:10
> 2026-09-06T01:53:53.904Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 54m 14s, 379 packets)
> 2026-09-06T01:53:40.886Z [WARN] [Alex Bad] Disconnected: socket closed (up 3h 29m, 344 packets)
> 2026-09-06T14:20:02.999Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 12m 2s, 82 packets) ×2 — 00:59:36, 14:20:02
> 2026-09-06T00:47:30.863Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 4m 2s, 26 packets)
> 2026-09-06T00:43:25.986Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 11m 2s, 75 packets)
> 2026-09-06T00:32:21.163Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 33m 43s, 245 packets)
> 2026-09-05T23:58:34.560Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 5m 52s, 37 packets)
> 2026-09-05T23:52:38.932Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 2m 32s, 15 packets)
> 2026-09-05T23:50:03.151Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 44m 3s, 310 packets)
> 2026-09-05T23:05:57.854Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 39m 15s, 279 packets)
> 2026-09-05T22:26:40.507Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 23m 53s, 168 packets)
> 2026-09-05T22:24:43.879Z [WARN] [Alex Bad] Disconnected: socket closed (up 3h 43m, 372 packets)
> 2026-09-05T22:02:43.999Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 10m 32s, 72 packets)
> 2026-09-05T21:52:08.099Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 14m 3s, 97 packets)
> 2026-09-05T21:38:02.367Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 10m 2s, 66 packets)
> 2026-09-05T21:27:56.628Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 56m 44s, 389 packets)
> 2026-09-05T20:31:09.588Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 10m 22s, 71 packets)
> 2026-09-05T20:20:43.739Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 17m 13s, 120 packets)
> 2026-09-05T20:03:27.127Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 22m 2s, 152 packets)
> 2026-09-05T19:41:21.536Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 36m 4s, 252 packets)
> 2026-09-05T19:05:13.616Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 40m 24s, 276 packets)
> 2026-09-05T18:41:47.538Z [WARN] [Alex Bad] Disconnected: socket closed (up 6h 8m, 642 packets)
> 2026-09-05T18:24:46.826Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 7m 32s, 50 packets)
> 2026-09-05T18:17:11.947Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 25m 23s, 176 packets)
> 2026-09-05T17:51:44.876Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 6m 2s, 38 packets)
> 2026-09-05T17:45:40.108Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 28m 34s, 197 packets)
> 2026-09-05T17:17:02.835Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 23m 53s, 163 packets)
> 2026-09-05T16:53:06.725Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 7m 2s, 48 packets)
> 2026-09-05T16:46:00.690Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 55m 14s, 386 packets)
> 2026-09-05T15:50:43.080Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 11m 2s, 72 packets)
> 2026-09-05T15:39:37.971Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 29m 4s, 204 packets)
> 2026-09-05T15:10:30.283Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 6m 12s, 43 packets)
> 2026-09-05T15:04:14.643Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 1h 9m, 478 packets)
> 2026-09-06T05:27:22.147Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 12s, 1 packet) ×3 — 13:55:16, 03:48:00, 05:27:22
> 2026-09-06T05:20:32.533Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 16m 33s, 114 packets) ×2 — 13:55:01, 05:20:32
> 2026-09-05T13:38:25.512Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 1m 2s, 3 packets)
> 2026-09-05T13:37:20.489Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 20m 43s, 142 packets)
> 2026-09-05T13:16:32.947Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 38m 24s, 267 packets)
> 2026-09-05T12:38:05.971Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 34m 4s, 250 packets)
> 2026-09-05T12:33:55.850Z [WARN] [Alex Bad] Disconnected: socket closed (up 4m 22s, 9 packets)
> 2026-09-05T12:29:30.643Z [WARN] [Alex Bad] Disconnected: socket closed (up 1h 45m, 190 packets)
> 2026-09-05T12:03:59.144Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 59m 34s, 409 packets)
> 2026-09-05T11:04:22.407Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 44m 25s, 309 packets)
> 2026-09-05T10:44:41.414Z [WARN] [Alex Bad] Disconnected: socket closed (up 1h 15m, 135 packets)
> 2026-09-05T10:19:54.852Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 12m 2s, 80 packets)
> 2026-09-05T10:07:49.233Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 27m 4s, 187 packets)
> 2026-09-05T09:40:42.918Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 15m 3s, 102 packets)
> 2026-09-05T09:29:33.355Z [WARN] [Alex Bad] Disconnected: socket closed (up 17m 3s, 35 packets)
> 2026-09-05T09:25:37.743Z [WARN] [Licht Badezimmer] Disconnected: socket closed (up 1h 33m, 661 packets)
> … 19 older message(s) not shown.
> 
> ```

---

<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:** [September 6, 2026, 7:29pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/386 "2026-09-06T19:29:13Z")

</div>

Hi Dietrich

Your NX-4473 is a **4-gang switch** , not a metering plug — its Tuya specification lists `switch_1` to `switch_4` and no measurements at all. It is on the **Smart Plug** driver, which knows one switch, so channels 2–4 are invisible. They are alive right now (DP 2 `false`, DP 3 `true`, DP 4 `false`), just out of reach.

A device cannot change driver, so:

1. Note the **Local Key** from its current settings
2. Remove the device
3. **Add device → Tuya Local → Wall Switch**
4. IP `192.168.13.2`, protocol **3.3** , and press **☁ Fetch Device ID & Local Key from Cloud** — your cloud lookup works, so it fills itself in

Afterwards check the advanced settings. Cloud lookup should have set these already:

| Setting | Value |
| --- | --- |
| DP Switch 1–4 | **1, 2, 3, 4** |
| DP Relay Status | **38** |

Optional: **DP Countdown 1–4 → 9, 10, 11, 12** (not auto-detected), and give the four channels names so the tiles read “Mirror light” instead of “Switch 3”.

Two notes: for flows on channels 2–4 use the Wall Switch card **“A switch gang changed”** — Homey’s built-in “Turned on/off” only sees the main switch. And your log shows this device dropping the connection every few minutes; a switch has nothing to measure, so if that continues, set **Polling Interval to 0**. State changes are pushed either way.

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

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