# \[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:** 11
**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:** [August 3, 2026, 9:50pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/204 "2026-08-03T21:50:27Z")
That’s how Stephen fixed an issue with the Data Center location: > [@\[APP\]\[Pro\] Tuya Local](https://community.homey.app/t/app-pro-tuya-local/154077/48): > > Ignoring everything that Co-Pilot advised!!! I created a new Tuya account based in North America, just for safety I also set my VPN to a server in New York. Created a new project, using EU-Central. Note: All data centres were available for selection not just the EU-West. Note: You can only use one data centre in a free account, so once it is selected, all of your projects will use the same one. If you get it wrong then you will heve to delete all of your projects and start again. Linking to … ---
**Author:** ![Niels\_Hubregtse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/niels_hubregtse/32/169361_2.png) [@Niels\_Hubregtse](https://community.homey.app/u/Niels_Hubregtse)\ **Post date:** [August 3, 2026, 10:21pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/205 "2026-08-03T22:21:59Z")
🙈 Damnit, I spend days to get it working, without success. Now I have created a new smartlife account and added one spare light for testing. Went back to the iot site logged on with my account I created weeks ago. Deleted all projects (they where empty) Created a new project (Central Europe Data Center) linked my app Now i see my device And all of this in less then 20 minutes… Then linked the iot in the conficuration of Tuya local searched the local IP-address (i reserved the IP-address in my DHCP table) Added a new device, filled in th IP-address and let the app search for the diviceID and LocalKey. In short it works… thanks for the golden tip 🙂 Tomorrow ill try if my main account is also connectable (i don’t think so), if not, i have a a lot of devices to migrate from one account to the new account ---
**Author:** ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)\ **Post date:** [August 4, 2026, 8:44pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/206 "2026-08-04T20:44:28Z")
Hi Andi I have two devices (currently running as “generic”, since some DPs are missing in the “driver ones” ### 1. Ceiling Vent with Light - **Model:** Lucande Smart LED Deckenventilator - **Remarks:** I’m using mostly the fan speed, light, brightness, mode. Not all are covered. **DP Configuration (JSON)** [ { “dp”: 1, “cap”: “onoff”, “label”: “Ventilator”, “settable”: true }, { “dp”: 2, “cap”: “generic\_picker\_1”, “label”: “Modus”, “settable”: true, “options”: “normal,sleep,nature”, “labels”: “Normal,Sleep,Nature” }, { “dp”: 3, “cap”: “generic\_number\_1”, “label”: “Geschwindigkeitsstufe”, “settable”: true, “scale”: 0, “min”: 1, “max”: 6, “step”: 1 }, { “dp”: 8, “cap”: “generic\_picker\_2”, “label”: “Fan direction”, “settable”: true, “options”: “forward,reverse”, “labels”: “vorwärts, rückwärts” }, { “dp”: 15, “cap”: “generic\_switch\_1”, “label”: “Licht”, “settable”: true }, { “dp”: 16, “cap”: “dim”, “label”: “Helligkeit”, “settable”: true, “scale”: 0, “min”: 0, “max”: 100, “step”: 1 }, { “dp”: 17, “cap”: “generic\_number\_2”, “label”: “Farbtemperatur”, “settable”: true, “scale”: 0, “min”: 0, “max”: 100, “step”: 1 }, { “dp”: 22, “cap”: “generic\_picker\_3”, “label”: “Timer”, “settable”: true, “options”: “cancel,1h,2h,4h,8h”, “labels”: “cancel,1h,2h,4h,8h” } ] **DP Table (Tuya Raw Specs):** DP 1 switch Boolean false {} DP 2 mode Enum normal normal, sleep, nature DP 3 fan\_speed Enum 6 1, 2, 3, 4, 5, 6 DP 8 fan\_direction Enum forward forward, reverse DP 15 light Boolean false {} DP 16 bright\_value Integer 44 0–100 step 1 DP 17 temp\_value Integer 0 0–100 step 1 DP 22 countdown\_set Enum off cancel, 1h, 2h, 4h, 8h ### 2. Dehumidifier - **Model:** Klarstein Dryfy Connect 50l - **Remarks:** Until now i used a shelly plug and the “auto” mode. FINALLY thx to you i can integrate the klarstein better! **DP Configuration (JSON):** [ {“dp”: 1, “cap”: “onoff”, “label”: “Power”, “settable”: true}, {“dp”: 2, “cap”: “generic\_picker\_1”, “label”: “Modus”, “settable”: true, “options”: “0,1”, “labels”: “Auto, Kontinuierlich”}, {“dp”: 3, “cap”: “measure\_humidity”, “label”: “Luftfeuchtigkeit IST”, “settable”: false, “scale”: 0}, {“dp”: 4, “cap”: “generic\_number\_1”, “label”: “Ziel-Luftfeuchtigkeit”, “settable”: true, “scale”: 0, “unit”: “%”, “min”: 30, “max”: 80, “step”: 5}, {“dp”: 6, “cap”: “generic\_picker\_2”, “label”: “Lüfterstufe”, “settable”: true, “options”: “0,1”, “labels”: “Hoch, Niedrig”}, {“dp”: 7, “cap”: “generic\_switch\_1”, “label”: “Kindersicherung”, “settable”: true}, {“dp”: 8, “cap”: “generic\_switch\_2”, “label”: “Schwenken”, “settable”: true}, {“dp”: 11, “cap”: “generic\_sensor\_2”, “label”: “Tank voll”, “settable”: false, “scale”: 0}, {“dp”: 12, “cap”: “generic\_picker\_3”, “label”: “Timer”, “settable”: true, “options”: “0..24”, “labels”: “Aus, 1h..24h”}, {“dp”: 13, “cap”: “generic\_sensor\_3”, “label”: “Restzeit Timer”, “settable”: false, “scale”: 0}, {“dp”: 101, “cap”: “generic\_switch\_3”, “label”: “Innere Trocknung”, “settable”: true}, {“dp”: 102, “cap”: “generic\_switch\_4”, “label”: “Wasserpumpe”, “settable”: true} ] **DP Table (Tuya Raw Specs):** DP 1 Power bool false DP 2 mode enum 0 DP 3 envhumid value 48 DP 4 humidity value 55 DP 5 anion Boolean false {} DP 6 windspeed enum 0 DP 7 lock bool false DP 8 shake bool true DP 11 fault bitmap 0 {“label”:[“0”,“1”,“2”,“3”,“4”,“5”]} DP 12 countdown enum 0 DP 13 countdown\_left value 0 0–1440 step 1 min DP 101 dry bool false DP 102 pump bool false Is there any chance for the generic ones to “send” custom commands for the DPs? e.g. set the timer to 6h (DP12 dehumidifier)? I can’t find suitable “THEN” cards or a custom function to send the known values thx as usual! 🙂 Rick EDIT: added information (dp table) ---
**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:** [August 4, 2026, 9:06pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/207 "2026-08-04T21:06:21Z")
Hi Rick Could you please share the DP table for those two devices (under App settings → Cloud Lookup)? That way others can finally as well use the devices by choosing the right driver (fan and dehumidifier). Regarding the action card - will be implemented 🙂 Andi ---
**Author:** ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)\ **Post date:** [August 5, 2026, 3:59am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/208 "2026-08-05T03:59:55Z")
As usual fast as hell 🙂 I’ve added the information in the existing post. Will test them this week Thx again! ---
**Author:** ![Niels\_Hubregtse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/niels_hubregtse/32/169361_2.png) [@Niels\_Hubregtse](https://community.homey.app/u/Niels_Hubregtse)\ **Post date:** [August 5, 2026, 10:56am UTC](https://community.homey.app/t/app-pro-tuya-local/154077/209 "2026-08-05T10:56:21Z")
Hi, i have managed to connect all my devices (almost all lights) and they seem to be working perfectly. but I have 4 lights that are unavailable and they wont recover themselves (in the normal homey tuya app connection they are still available). one light is the same as all my other lights (a simple GU10 color), i successfully tested yesterday, but now I can’t reacht it. The other 3 lights are 3 different kind of lights (one E14 color candle, and 2 different moodlights) Is there something I can or have to do for “special” devices? ---
**Author:** ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)\ **Post date:** [August 5, 2026, 3:33pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/210 "2026-08-05T15:33:07Z")
Hi Andi Just tested the “THEN” card → works (tested it with the ceiling fan). Now i just need another favor 😉 could you add a “AND” card to check for certain dp values? e.g. if xy AND “DP 8” is true/false (or number, would leave that open like the “THEN” card). EDIT: a “DP value changed” card for a specific device would fullfill the last needed flow card. e.g. the water alarm of my dehumidifier (DP 11 changed → “tag” true/false" → alert me). merci und schöne aabe Rick ---
**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:** [August 5, 2026, 4:45pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/211 "2026-08-05T16:45:21Z")
Hi Rick - Please try flow cards and modifications of the Dehumidifier and Fan Driver in the next TEST version: [Tuya Local | Homey](https://homey.app/a/com.tuyalocal/test/) **Klarstein:** dp\_onoff = 1 dp\_mode = 2 mode\_values = 0,1 dp\_current\_humidity = 3 dp\_target\_humidity = 4 dp\_anion = 5 ← falls vorhanden dp\_fan\_speed = 6 fan\_speed\_values = 0,1 dp\_child\_lock = 7 dp\_oscillate = 8 dp\_water\_full = 11 dp\_countdown\_timer = 12 dp\_countdown\_timer\_numeric = true ← NEU, unbedingt aktivieren dp\_countdown\_left = 13 dp\_countdown\_left\_minutes = true ← NEU, unbedingt aktivieren dp\_self\_clean = 101 dp\_pump = 102 **Your Fan/Light:** dp\_onoff = 1 dp\_mode = 2 mode\_values = normal,sleep,nature ← Standard ist “normal,sleep,nature,breeze,smart” dp\_speed = 3 speed\_min = 1 speed\_max = 6 dp\_fan\_speed = 0 ← bleibt deaktiviert (kein String-Enum) dp\_direction = 8 dp\_light\_onoff = 15 dp\_light\_dim = 16 dp\_light\_dim\_min = 0 dp\_light\_dim\_max = 100 dp\_light\_color\_temp = 17 dp\_light\_color\_temp\_invert = false ← testen, ggf. umschalten falls warm/kalt vertauscht wirkt dp\_countdown\_timer = 22 ---
**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:** [August 5, 2026, 4:53pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/212 "2026-08-05T16:53:56Z")
Hi Niels If the IP address (you can reach the devices by using test-connection) and Local Key both are correct… ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/0/30f83d5d2cb77d23c852812a75fd685ea3e32568.png) …try switching Protocol Version — some light modules use a newer Tuya protocol (3.4/3.5) than the standard GU10 bulbs (3.3) and play with the settings below. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/8/1/81737a65656137f266fb3a18fae66db7864f7d2d.png) ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/5/6530e495338a9966a4176f7fb8663a70affc6c47.png) And: Check the app’s Settings → Logs tab for that device’s exact error — it’ll say things like “Connection failed” or “No heartbeat received,” which tells us whether it’s a wrong IP (connection refused/timeout) or something else. Let me know what the relevant log lines show ---
**Author:** ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)\ **Post date:** [August 5, 2026, 5:05pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/213 "2026-08-05T17:05:03Z")
Salü Andi Thx! Proposition: Why not create a own driver vor “ceiling fans” and include the light features? in my head the direction / lights is something for ceiling fans and it would be great to get some lights on/off | lights are on |… cards as well 🙂 happ to help with testing (moving my devices from generic to those drivers → gonna start with the dehumidifier now. Ceiling fan i would wait until the “lights on/off” card, since i use this one outside in my garden. thx for your help again ---
**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:** [August 5, 2026, 5:14pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/214 "2026-08-05T17:14:43Z")
Adding the cards is much easier than a separate driver 🙂 Could you please check the new cards in 1.0.134 | Karte | Typ | Wirkung | | --- | --- | --- | | Licht setzen | THEN | Ein/Aus | | Licht ist an | AND/IF | Bedingung | | Licht-Helligkeit setzen | THEN | 0–100 % | ---
**Author:** ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)\ **Post date:** [August 5, 2026, 5:33pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/215 "2026-08-05T17:33:01Z")
I’m missing: - DP 8 (“Schwenkmodus”) - DP 101 (“Gerätetrocknung”) Maybe it would help to give the option to add “custom” DPs’ same as the “generic” one for DPs which are recognized but not in the “template”? my device: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/d/0d38b6209471727493454d4aacc32e2683fba395.png) ---
**Author:** ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)\ **Post date:** [August 5, 2026, 5:44pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/216 "2026-08-05T17:44:11Z")
Hi Andi, Just tried pairing a device under the new **“Ventilator” → “Lüfter”** driver to test the fan/light setup we discussed. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/8/68320f51fcb60ddca9016efbcbd2770a59ffe27d.png) Selected it explicitly (see screenshot: “You’re about to connect Lüfter with Homey”), but the resulting “Device found” DP-mapping screen shows the **same field template as the Humidifier driver** — Humidity, Target Humidity, Water Tank, Ionizer (Anion) — instead of fan-specific fields. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/b/bbd5b68772ffbb22eaebea4d43739ad899b85adf.png) Missing fields I’d need to map: - Fan direction (forward/reverse) — DP 8 on my unit - Light on/off — DP 15 - Light brightness (0-100) — DP 16 - Light color temperature — DP 17 Current fields (Child lock, Timer, Humidity, Target Humidity, Water tank, Temperature, Ionizer) don’t cover any of these, so there’s no way to map them during pairing right now. My device’s full DP layout for reference: | **DP** | **Value** | **Function** | | --- | --- | --- | | 1 | onoff | Fan power | | 2 | normal/sleep/nature | Mode | | 3 | 1-6 | Fan speed | | 8 | forward/reverse | Direction | | 15 | true/false | Light on/off | | 16 | 0-100 | Brightness | | 17 | 0-100 | Color temperature | | 22 | cancel/1h/2h/4h/8h | Timer | Looks like the “Lüfter” driver might have inherited the Humidifier template by mistake? Holding off on pairing for now to avoid losing light/direction control on my existing generic setup. Happy to test further once there’s a fix. Thanks for all the work on this! * * * ---
**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:** [August 5, 2026, 6:43pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/217 "2026-08-05T18:43:41Z")
Could you please try it again with the newest version? ---
**Author:** ![Niels\_Hubregtse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/niels_hubregtse/32/169361_2.png) [@Niels\_Hubregtse](https://community.homey.app/u/Niels_Hubregtse)\ **Post date:** [August 5, 2026, 7:05pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/218 "2026-08-05T19:05:43Z")
> [@Andi](#): > > or something e the 2 moodlights needed to be set on 3.1 protocol, now they seem to be and stay connected. The E14 light doesn’t respond to any protocol, the strange thing is that the log says that it is connected. But i also notice that the other tuya app also has problems keeping it steady, so maybe the light itself is broken. the light isn’t importand, ill replace it. not gonna put hours into it for 6 euros thanks for the support ---
**Author:** ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)\ **Post date:** [August 5, 2026, 7:13pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/219 "2026-08-05T19:13:53Z")
Salü Andi Wow - works! just moved the fan from generic to the “Lüfter” Driver and the device is working. Regarding the dehumidifier - the “Lüfter Schwenkung” is now in the “Lüfter” Driver and not in the “dehumidifier” driver 🙂 I have a card in the ceiling fan now, but not in the dehumidifier. ---
**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:** [August 5, 2026, 7:46pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/220 "2026-08-05T19:46:06Z")
My bad 🙂 fixed now in **1.0.139** ---
**Author:** ![Elliot\_Hallais](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/elliot_hallais/32/114058_2.png) [@Elliot\_Hallais](https://community.homey.app/u/Elliot_Hallais)\ **Post date:** [August 5, 2026, 7:55pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/221 "2026-08-05T19:55:07Z")
Hi, I’ve been using Tuya Local for a while and really like it, but I recently picked up a portable EV charger (Vevor, Type 2, 16A/3.68kW single phase, Tuya modelId `e1mtzkaw`, product `LS-AS/EU-H8`) and had to shoehorn it into the Generic driver. It mostly works after a lot of trial and error, but I think this category of device (Tuya EV chargers, sold under a bunch of rebrands: Vevor, Nine, Tera, Emini, Aimiler, Ecopoint, Dowell…) is common enough now that it might be worth a dedicated driver, similar to what you did for Heat Pump. Home Assistant’s tuya-local integration already has several of these mapped (`nine_ev_charger.yaml`, `tera_w01_evcharger.yaml`, etc.) so there’s a decent reference if you want to look at how they structured it. Also worth noting, Tuya has a dedicated category code for this device class, `qccdz` (shows up in the app’s own device info panel) — might be a good hook to auto-suggest a dedicated driver during pairing instead of relying on people stumbling into the Generic one. Here’s the full DP model I pulled from the Tuya Cloud API for mine, might save you some digging: | DP | Name | R/W | Type | Details | | --- | --- | --- | --- | --- | | 1 | forward\_energy\_total | ro | value | scale 2, unit kWh — lifetime total (see note below) | | 3 | work\_state | ro | enum | charger\_free, charger\_insert, charger\_free\_fault, charger\_wait, charger\_charging, charger\_pause, charger\_end, charger\_fault | | 4 | charge\_cur\_set | rw | value | scale 0, unit A — capped ~6-16A physically, raw cloud range is much wider | | 6 | phase\_a | ro | raw | 8 bytes big-endian: 2B voltage (x0.1V), 3B current (x0.001A), 3B power (x0.001kW) | | 10 | fault | ro | bitmap | 16 bits: ov\_cr, ov2\_cr\_fault, ov\_vol, undervoltage\_alarm, contactor\_adhesion, contactor\_fault, earth\_fault, meter\_hardware\_alarm, scram\_fault, cp\_fault, meter\_commu\_fault, card\_reader\_fault, cir\_short\_fault, adhesion\_fault, self\_test\_alarm, leakagecurr\_alarm | | 13 | connection\_state | ro | enum | controlpi\_12v, controlpi\_12v\_pwm, controlpi\_9v, controlpi\_9v\_pwm, controlpi\_6v, controlpi\_6v\_pwm, controlpi\_error | | 14 | work\_mode | rw | enum | charge\_now, charge\_pct, charge\_energy, charge\_schedule, charge\_delay | | 18 | switch | rw | bool | — | | 19 | local\_timer | rw | raw | 2 bytes: start hour / end hour | | 23 | system\_version | ro | string | — | | 24 | temp\_current | ro | value | scale 0, unit °C | | 25 | charge\_energy\_once | ro | value | scale 2, unit kWh — current/last session energy | | 27 | online\_state | rw | enum | offline, online | | 28 | timer\_on | rw | value | unit h — delay before power-on | | 33 | mode\_set | rw | raw | 8 bytes, capability flags | Some higher power variants (32A/7kW, product `SS_EU_Mode2_7kW` for example) also expose dp5/dp9 (single phase / total power as plain integers) and dp6/7/8 as three separate phase readings, still in that raw byte format. Mine only has the single dp6. A few things I ran into with the Generic driver that a dedicated driver would fix: - The current-limit DP (dp4 above) is a plain integer, not a Tuya enum, so it can only go on generic\_number/Custom Slider. I tried remapping it to a Custom Picker for a clearer stepped display (only 11 possible values, 6 to 16A), but looking at `device.js`, `_dpToCap()` checks `typeof rawValue === 'number'` first and returns before ever touching `options`/`labels`/`readMap` — so readMap is basically dead code for numeric DPs. Worked fine going picker→DP (writeMap), just not the other way. A one-line fix (checking readMap before the number branch, using `rm[String(rawValue)]`) would make numeric enums usable, might be worth it for other device types too, not just EV chargers. - dp10 is a proper 16-bit bitmap with specific fault codes, but the only capability available is a plain boolean alarm. Would be nice to at least expose the raw bitmap value somewhere so people can match it against the fault table without digging into raw DP debug output. - dp1 (lifetime total) never updated locally for me even through a full charge cycle, even though the session counter (dp25) tracked correctly and matched the Tuya app exactly. I checked the HA integration’s config for a similar model and they don’t map dp1 at all either, so I think it’s a known dead end for these chargers over LAN. Might be worth doing the same trick you already do for smart plugs (computing energy locally instead of trusting the local counter), just triggered off dp25 whenever work\_state hits charger\_end, since there’s no live power DP to integrate from on this model. - one more thing if you ever expose dp14 (work\_mode) as a picker: the enum range Tuya reports for it doesn’t seem to reflect what’s actually usable. Mine reports 4 selectable values (charge\_now, charge\_pct, charge\_energy, charge\_schedule), but dp33 (mode\_set, a raw bitmask specifically documented to say which modes are implemented) decodes to `01 00 00 00 01 00 00 00` for my unit — only byte1 (charge\_now) and byte5 (charge\_delay, which isn’t even in the enum range) are set. So percent/quantity/schedule are listed as valid options but don’t seem to do anything on this hardware, and the one that’s actually implemented besides immediate mode isn’t in the enum at all. I’d trust dp33 over the static enum range if you ever build a mode picker for these. Happy to test anything against my actual unit if that helps, I’ve got a working Device ID and Local Key for it already and can grab raw DP dumps on demand (not pasting the local key here obviously, can send by DM if useful). ---
**Author:** ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)\ **Post date:** [August 5, 2026, 8:08pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/222 "2026-08-05T20:08:51Z")
check → works now 🙂 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:** [August 5, 2026, 8:32pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/223 "2026-08-05T20:32:50Z")
Hi Elliot Could you please provide the DP Table? you’ll find it under App settings (should be exact the same data as your DP model) Thank you [Previous page](https://community.homey.app/t/app-pro-tuya-local/154077.md?page=10) [Next page](https://community.homey.app/t/app-pro-tuya-local/154077.md?page=12)