# \[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:** 2
**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:** [April 30, 2026, 8:42pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/21 "2026-04-30T20:42:42Z")
I’ve added several new device types to the Tuya Local integration — each with full auto‑detection of DPs during pairing, repair flow, and complete flow card support (triggers, conditions, actions): - **Fan** — speed slider, enum speed, oscillation, and mode - **Humidifier** — humidity sensor, target humidity, and water‑empty alarm - **Heater** — target/current temperature, mode, and fault alarm - **Light** — brightness, color temperature, and HSV color control All drivers are ready for hands‑on testing. If you have compatible devices, please give them a try and share your feedback — it helps refine detection and flow behavior for everyone. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/b/0b802764b4596c57ec268c5d4d314a3cf3c92664.jpeg) ---
**Author:** ![Gabriel\_Laguna](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gabriel_laguna/32/83144_2.png) [@Gabriel\_Laguna](https://community.homey.app/u/Gabriel_Laguna)\ **Post date:** [May 19, 2026, 2:57pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/22 "2026-05-19T14:57:33Z")
Hi Andi, I’m testing Tuya Local with a Tuya ceiling fan, and the basic local control works well. The device was detected successfully and I was able to add it to Homey with these DPs: - DP 60: On/Off - DP 62: Fan speed - DP 64: Timer/countdown However, the fan also supports reverse direction, but I don’t see a way to map this in the current Fan device template. In the Tuya Developer Platform, the device exposes this standard instruction: Code: `fan_direction` Type: `Enum` Values: `forward`, `reverse` In the Tuya Local pairing screen, this appears in the detected DPs as: - DP 63: `forward` So it looks like DP 63 is the fan direction / reverse mode DP. Would it be possible to add support for a “Fan Direction” or “Reverse Mode” capability for ceiling fans, using an enum DP with values `forward` and `reverse`? I’m happy to test this if needed. 🙂 Thx ---
**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:** [May 19, 2026, 5:46pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/23 "2026-05-19T17:46:33Z")
Hi, thanks for the detailed report — that’s exactly the info needed to add this cleanly! **Fan Direction (forward / reverse)** is implemented in v1.0.32 (as soon as I can publish the version / right now Athom seem to have issues…): - A new **Fan Direction** capability (picker: Forward / Reverse) appears on the device tile once enabled - In **Device Settings → Data Points** , set **Fan Direction DP** to **63** (or whatever your device reports) - At pairing time, the DP is **auto-detected** — if the detected snapshot contains a value of `forward` or `reverse`, the DP number is filled in automatically - Three new **Flow cards** : _Fan direction changed_ (trigger with direction + previous direction tokens), _Fan direction is/is not_ (condition), _Set fan direction_ (action) The capability is optional — it stays hidden until you set a non-zero DP number, so it won’t clutter devices that don’t support it. If you’d like to test it: update to v1.0.32, open your fan’s device settings, and enter `63` in the _Fan Direction DP_ field. Let me know how it goes! 🙂 @Gabriel_Laguna edit: now it’s available for testing: [Tuya Local | Homey](https://homey.app/de-ch/app/com.tuyalocal/Tuya-Local/test/) Please let me know if/how it works. ---
**Author:** ![Gabriel\_Laguna](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/gabriel_laguna/32/83144_2.png) [@Gabriel\_Laguna](https://community.homey.app/u/Gabriel_Laguna)\ **Post date:** [May 19, 2026, 10:15pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/24 "2026-05-19T22:15:28Z")
Hi! I’ve just installed the test version and it works perfectly. Thank you so much for the quick response and for all your hard work on this amazing new app! 🙌 ---
**Author:** ![flowerpiece](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/flowerpiece/32/12477_2.png) [@flowerpiece](https://community.homey.app/u/flowerpiece)\ **Post date:** [May 20, 2026, 6:51pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/25 "2026-05-20T18:51:00Z")
Works perfectly here with a dehumidifier. I can even activate the timer on the device. Works incredibly fast too. Thanks so much for this app! Finally a local version of Tuya. ---
**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:** [May 22, 2026, 10:48pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/26 "2026-05-22T22:48:43Z")
Hi everyone, Looking at the install data, I can see that **more than 10 devices** are currently running on the **Generic Tuya Device** driver — which means there are quite a few device types out there that don’t yet have a dedicated driver. The Generic driver is powerful but requires manual DP configuration. A dedicated driver means **auto-detection at pairing, a clean tile, proper icons, and ready-made Flow cards** — no fiddling with DP numbers. * * * **If you’re using the Generic driver, I’d love to know:** 1. What kind of device is it? _(e.g. robot vacuum, curtain motor, garage door, pool pump, IR blaster, …)_ 2. Can you paste the **Raw DP snapshot** from Settings → DP Debug → Raw Data? 3. What capabilities matter most to you? _(on/off, mode, sensor values, flow cards, …)_ 4. Are you willing to test a beta version? The more details you share, the faster a proper driver can be built. You can also open a structured **[device request on GitHub](https://github.com/andiwirz/com.tuyalocal/issues/new/choose)** — the issue template will guide you through exactly what’s needed. Thanks for using the app — every piece of feedback helps! 🙏 _Andi_ ---
**Author:** ![Damian\_Surma](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/damian_surma/32/48817_2.png) [@Damian\_Surma](https://community.homey.app/u/Damian_Surma)\ **Post date:** [May 26, 2026, 9:24am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/27 "2026-05-26T09:24:29Z")
Where can I find: In All Devices, click the pencil icon next to your device → copy Device ID and Device Secret (= Local Key). ![Opera Zrzut ekranu2026-05-26112228eu.platform.tuya.com](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/9/f9331384556018dcb94ee6373ee2da5d2d5cbee4.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:** [May 26, 2026, 10:39am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/28 "2026-05-26T10:39:52Z")
I am not sure about that instruction, but an alternative is the following: - In the screen of your screenshot click Debug Device: ![Tuya IoT 1](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/5/45b573c862368c60184586177b505581b3d21bab.png) - In the next screen, in the Basic Information tab, note your Device ID ![Tuya IoT 2](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/7/d77ac2536290ee3da83621198d876d576ebfa4e2.png) - Next, in the navigation pane (on the left) select API Explorer: ![Tuya IoT 3](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/7/7777b466b7e9343d7066b2475de7e8db72ff7353.png) - Open the Device Management section and select Query Device Details: ![Tuya IoT 4](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/e/0e21ca5337a61c26b564fe934aa61ca48fa9713c.png) - Input your Device ID in the `device_id` search field and click the Submit Request button: ![Tuya IoT 5](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/c/1c4c087b5cae53536399718356fd68b82aaf8925.png) - In the Response section, find your Local Key: ![Tuya IoT 6](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/4/f402e7260e19947184b4acb93395addeeb87de07.png) ---
**Author:** ![Damian\_Surma](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/damian_surma/32/48817_2.png) [@Damian\_Surma](https://community.homey.app/u/Damian_Surma)\ **Post date:** [May 26, 2026, 11:40am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/29 "2026-05-26T11:40:34Z")
I only have this information ![Opera Zrzut ekranu2026-05-26133916eu.platform.tuya.com](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/0/705a4f8fe95ca8ef2f8a06f5a1aa85258fe01788.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:** [May 26, 2026, 12:30pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/30 "2026-05-26T12:30:34Z")
It seems that your Tuya IoT-platform subscription has expired. I assume you have a free subscription. That is only valid for half a year. After that you can extend your free subscription again by a half year. You’ll have to perform this renewal process every half year. - In your project go to the Service API tab: ![Tuya IoT 10](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/a/ca9ad02d7b50f4e7df202fc3d0153b75fffb91e9.png) - Next, in the list of APIs click View Details at the IoT Core API: ![Tuya IoT 11](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/9/896387c74fabc0880aa45290499b7dc2c0f0cc3b.png) - In the following overview, you’ll find the status of your subscription. Normally, when your subscription is about to expire, you’ll find a link there through which you can request an extension. I assume that is also the case for expired subscriptions. In my case that link is not shown, as my subscription is still valid. After requesting an extension, it typically takes a number of days for the request to be approved. ![Tuya IoT 12](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/1/016fbc06432c5008f81eb3b38f6d9a9098aa4482.png) ---
**Author:** ![flowerpiece](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/flowerpiece/32/12477_2.png) [@flowerpiece](https://community.homey.app/u/flowerpiece)\ **Post date:** [May 26, 2026, 8:24pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/31 "2026-05-26T20:24:03Z")
Hi, since this evening I get “socket closed” error on my dehumidifier. What could I try to get this to work again? I get this error in the log’ 26/05/2026, 22:20:55 [ERR] [D820 Ontvochtiger] Connection failed: read ECONNRESET — likely protocol version mismatch. Use Auto-detect in the device Repair screen. But I can’t find the repair screen. Am I blind perhaps? 😄 ---
**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:** [May 26, 2026, 8:28pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/32 "2026-05-26T20:28:24Z")
The “socket closed” error means the device actively terminated the TCP connection — it was reachable on the network, but immediately rejected the connection. This almost always happens for one of three reasons: * * * ### **Most likely causes (in order)** **1. Firmware update pushed tonight** Tuya regularly pushes automatic firmware updates. An update can change the protocol version (e.g. 3.3 → 3.4) or rotate the local key. ➜ **Fix:** Go to device settings, change the protocol version to **Auto-detect** and save. The app will then try 3.3 → 3.4 → 3.1 → 3.5 automatically. * * * **2. Local key rotated** If someone opened the Tuya app or re-linked the device, Tuya rotates the local key. The old key gets rejected immediately. ➜ **Fix:** Fetch the new local key from the [Tuya IoT Developer Portal](https://iot.tuya.com/) and enter it in the device settings. * * * **3. IP address changed** If your router restarted or reassigned IPs via DHCP, the device may now be at a different address. ➜ **Fix:** Check that the IP in the device settings still matches. Assign a static/reserved IP to the device in your router to prevent this in future. You’re not blind — the repair screen was **removed in version 1.0.34**. The hint in the log message is outdated and still points to it. Sorry about that confusion! The settings are now directly on the device page: 1. Open the Homey app 2. Tap on your dehumidifier device 3. Tap the **⚙ gear icon** (top right) → **Settings** 4. Change **Protocol Version** to **Auto-detect (3.3 → 3.4 → 3.1 → 3.5)** 5. Tap **Save** The app will then automatically find the correct protocol version and reconnect. * * * The misleading log message is a bug — it still references the repair screen that no longer exists. I’ll fix that now. ---
**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:** [May 26, 2026, 9:08pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/33 "2026-05-26T21:08:44Z")
## **🐾 Tuya Local v1.0.35 — New Pet Feeder driver (beta) — testers wanted!** Hi everyone, I’ve just pushed **version 1.0.35** to the **test channel** and I’m looking for people with a **Tuya-based automatic pet feeder** to help validate the new driver before it goes stable. * * * ### **What’s new in 1.0.35** #### **🐾 New driver: Pet Feeder** A dedicated driver for Tuya-based automatic pet feeders - It includes: | **Capability** | **What it does** | | --- | --- | | On / Off | Enable / disable the feeder | | Food level (`food_status`) | Enum: `full` / `high` / `half` / `low` / `less` / `lack` / `empty` | | Motor state | `standby` / `feeding` / `blocked` / … | | Feed portions slider | Trigger an immediate feed (1–50 portions) | | Last feed report | How many portions were actually dispensed | | Surplus grain level | Secondary hopper level indicator | | Meal plan count | Number of scheduled meals programmed on the device | | Desiccant remaining (days) | Days left on the built-in desiccant pack | | Child lock | Optional | | Blockage / cleaning / grain-outlet alarms | Optional | **Flow cards:** - _Triggers:_ connected · disconnected · food level is low · feeding completed - _Conditions:_ food level is / is not low · feeder is / is not connected - _Actions:_ Feed now (1–50 portions) · Refresh state · Force reconnect **Push notification** when food drops to `low`, `less`, `lack` or `empty` — configurable via device settings. * * * #### **🔔 Offline grace period (all drivers)** All nine drivers now have an **Offline Grace Period** setting (default **60 s** ). The “device disconnected” flow trigger is held back until the device has been offline for that many seconds. This eliminates the **3–4 spurious disconnect notifications per night** that some devices (especially pet feeders and dehumidifiers) generate due to brief firmware-level TCP reconnect cycles. * * * #### **🐛 Bug fixes** - Fixed a misleading log message that referred to a “Repair screen” that no longer exists — it now correctly says to open **device Settings**. - Food level values `less` and `lack` are recognised by the “food level is low” condition and push notification. * * * ### **How to install the beta** use the direct link: 👉 [https://homey.app/en-gb/app/com.tuyalocal/test/](https://homey.app/en-gb/app/com.tuyalocal/test/) * * * ### **What I need from pet feeder testers ✅** If you have a Tuya pet feeder, please: 1. Install the beta and add your feeder as a **Pet Feeder** device 2. Let the app auto-detect your DPs — note which ones were found (Settings → DP Debug) 3. Test the flow actions 4. Check that the **food level** capability updates correctly when the hopper is filled/emptied 5. Leave the feeder running overnight and confirm whether spurious disconnect notifications are gone 6. Report back with: The more feeder models we validate, the better the auto-detection becomes for everyone. 🙂 ---
**Author:** ![sorted.bits](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sorted.bits/32/149039_2.png) [@sorted.bits](https://community.homey.app/u/sorted.bits)\ **Post date:** [June 3, 2026, 5:38am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/34 "2026-06-03T05:38:33Z")
First of all, thanks for building a real Tuya Local integration. I have a Pool Heat Pump that I can only use through Tuya Local with HA because the other Tuya integrations use the wrong DP. Currently I used it through Tuya Local, through Home Assistant, connected to Homey. Which is the only reason I kept HA alive. So 🎉 🎉 🎉 ! I am trying to get it to work, using both a heater or air conditioner ‘mode’, but the heater does not have a target temperature attribute I can assign, which the air conditioner setting DOES have. I copied the Home Assistant configuration, from here: [tuya-local/custom\_components/tuya\_local/devices/fairland\_iphcr15\_heatpump.yaml at main · make-all/tuya-local · GitHub](https://github.com/make-all/tuya-local/blob/main/custom_components/tuya_local/devices/fairland_iphcr15_heatpump.yaml) In air conditioner mode, it works mostly, but then the icon does not show when it’s heating. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/d/ad8500f9dfc2e13073c02fec53be57e5d42b6d67.png) Currently the heat pump is heating from 24 to 26 degrees, but it does not show the circle around the target temperature (like it does in the screenshot below) : ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/5/45449056755d534c55d9bf52764e2886c646e8e3.png) When opening the properties tab, it does show the orange background though: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/5/655f2786034f29bf201f2789f2f87df023263143.jpeg) Maybe, this partly could be solved by introducing more device classes? ---
**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\ **Post date:** [June 3, 2026, 1:09pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/35 "2026-06-03T13:09:24Z")
The status indicator is likely set incorrectly. Go to the device-\>Settings (top right corner) and select the target temperature status indicator. ---
**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:** [June 3, 2026, 8:02pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/37 "2026-06-03T20:02:11Z")
@sorted.bits Install latest **test** version and let me know if it works: [Tuya Local | Homey](https://homey.app/de-ch/app/com.tuyalocal/Tuya-Local/test/) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/2/52a28d4ae4b5308903f3848736f064cc14f179c8.jpeg) ---
**Author:** ![sorted.bits](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sorted.bits/32/149039_2.png) [@sorted.bits](https://community.homey.app/u/sorted.bits)\ **Post date:** [June 5, 2026, 4:53am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/38 "2026-06-05T04:53:27Z")
Oh dang, my notifications were not on. > The status indicator is likely set incorrectly. Go to the device-\>Settings (top right corner) and select the target temperature status indicator. I tried switching that to different values, but this made no difference ☹ . > Install latest **test** version and let me know if it works: [Tuya Local | Homey](https://homey.app/de-ch/app/com.tuyalocal/Tuya-Local/test/) I just installed it and while I did that, I got an update from the Homey app (beta) and now my tiles look different anyway, so I am not sure this should be fixed right now. In both cases the heater is on, and both have a target temperature and current/water temperature. But please, don’t spend too much time on it, as it is already SUCH an improvement to no longer have to use Home Assistant to connect my devices directly. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/7/27b694c968d56839e8e47936c0c0b361ea8c8d6d.png) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/1/61917c1ecf45cfda5ef51ae7d1813923b0a9ae42.png) Thanks again for the work! ---
**Author:** ![Stephen\_Petitt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stephen_petitt/32/121620_2.png) [@Stephen\_Petitt](https://community.homey.app/u/Stephen_Petitt)\ **Post date:** [June 10, 2026, 11:46pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/39 "2026-06-10T23:46:09Z")
Hi First, let me own up to being a newbie. I have to sets of Tuya compliant bulbs; 4 x white and 3 x colour, all controlled by the LEDVANCE SMART+ app I can add the colour bulbs through your Tuya Local app without problem but the white ones are failing because some part of the data is wrong. I’m copying the device\_id and local\_id directly from the LEDVANCE app, IP is coming from my router validated against the MAC address of the bulb, lastly I have tried your generic setting for protocol and 3.3 and 3.4. Any ideas as to what I am doing wrong. Thanks Stephen ---
**Author:** ![Stephen\_Petitt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stephen_petitt/32/121620_2.png) [@Stephen\_Petitt](https://community.homey.app/u/Stephen_Petitt)\ **Post date:** [June 11, 2026, 2:35am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/40 "2026-06-11T02:35:14Z")
Sorry, a second request. I have a Petlibro Granary pet feeder running in the Tuya Smart+ app, I have a device\_id but not a local\_id being displayed. This appears to be the app hiding it, as I also have a bulb, not one of the ones in my previous message, that is also not displaying the local\_id. Is there any way that I can find this information through another route, Gemini and Co-Pilot have had me going around in circles for literally the last week with no result and I am beginning to lose the will to live. Thanks in advance Stephen ---
**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:** [June 11, 2026, 5:31am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/41 "2026-06-11T05:31:16Z")
Hi - Please read this carefully to get the Information about how adding devices and what the requirements are: [GitHub - andiwirz/com.tuyalocal: Homey App to manage Tuya devices local · GitHub](https://github.com/andiwirz/com.tuyalocal) Thank you [Previous page](https://community.homey.app/t/app-pro-tuya-local/154077.md?page=1) [Next page](https://community.homey.app/t/app-pro-tuya-local/154077.md?page=3)