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

<div class="post-metadata">

**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, 9:23pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/224 "2026-08-05T21:23:00Z")

</div>

There you go :  
Chargeur Voiture

| Column 1 | Column 2 | Column 3 | Column 4 | E |
| --- | --- | --- | --- | --- |
| DP 1 | forward\_energy\_total | value | 0 | 0–99999999 step 1 kW·h |
| DP 3 | work\_state | enum | charger\_end | charger\_free, charger\_insert, charger\_free\_fault, charger\_wait, charger\_charging, charger\_pause, charger\_end, charger\_fault |
| DP 4 | charge\_cur\_set | Integer | 13 | 1–255 step 1 A |
| DP 6 | phase\_a | raw | AAAAAAAAAAA= | |
| DP 10 | fault | bitmap | 0 | |
| DP 13 | connection\_state | enum | controlpi\_9v\_pwm | controlpi\_12v, controlpi\_12v\_pwm, controlpi\_9v, controlpi\_9v\_pwm, controlpi\_6v, controlpi\_6v\_pwm, controlpi\_error |
| DP 14 | work\_mode | Enum | charge\_now | charge\_now, charge\_pct, charge\_energy, charge\_schedule |
| DP 18 | switch | Boolean | false | {} |
| DP 19 | local\_timer | raw | AAA= | |
| DP 23 | system\_version | string | SS\_V1.0.2 | |
| DP 24 | temp\_current | value | 35 | -40–200 step 1 ℃ |
| DP 25 | charge\_energy\_once | value | 1 | 1–999999 step 1 kW·h |
| DP 27 | online\_state | enum | online | |
| DP 28 | timer\_on | value | 0 | |
| DP 33 | mode\_set | raw | AQAAAAEAAAA= | |

And in the debug tab :

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

And raw data :  
{  
“devId”: null,  
“uid”: null,  
“t”: null,  
“t\_local”: null,  
“cid”: null,  
“updatedAt”: “05/08/2026 23:17:30”,  
“dps”: {  
“1”: 0,  
“3”: “charger\_end”,  
“4”: 13,  
“10”: 0,  
“13”: “controlpi\_9v\_pwm”,  
“14”: “charge\_now”,  
“18”: false,  
“23”: “SS\_V1.0.2”,  
“24”: 35,  
“25”: 1,  
“27”: “online”  
}  
}

---

<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:** [August 5, 2026, 9:31pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/225 "2026-08-05T21:31:13Z")

</div>

Hi Elliot - perfect. Could you please test the new driver in the TEST version? [Tuya Local | Homey](https://homey.app/a/com.tuyalocal/test/)

Wallbox is ready for a test:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/d/ed2396d9d7098491903cf480edd8f719b68ec3f6.png)

Please check as well if the charger is visible under Energy (Homey App on mobile/tablet)

---

<div class="post-metadata">

**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, 10:02pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/226 "2026-08-05T22:02:08Z")

</div>

Thanks for the quick update.

Seems to work fine, the DP6 is not working (nothing for Power, Current and Voltage), but I guess it’s as expected as the DP itself is not sending any info. Other live datas are correct, but they dont stay for insights.

For energy dashboard, it’s not working, it stays at 0 event after 30min charge.

Other than that everything’s fine.

---

<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:** [August 5, 2026, 10:05pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/227 "2026-08-05T22:05:34Z")

</div>

Could you please send the DP table while charging (need to check the real values)?

---

<div class="post-metadata">

**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, 10:07pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/228 "2026-08-05T22:07:49Z")

</div>

Sure, there it is:  
{  
“devId”: null,  
“uid”: null,  
“t”: 1785967640,  
“t\_local”: “06/08/2026 00:07:20”,  
“cid”: null,  
“updatedAt”: “06/08/2026 00:07:33”,  
“dps”: {  
“1”: 5,  
“3”: “charger\_end”,  
“4”: 13,  
“10”: 0,  
“13”: “controlpi\_9v\_pwm”,  
“14”: “charge\_now”,  
“18”: true,  
“23”: “SS\_V1.0.2”,  
“24”: 52,  
“25”: 174,  
“27”: “online”  
}  
}

---

<div class="post-metadata">

**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, 10:10pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/229 "2026-08-05T22:10:29Z")

</div>

Wait, let me restart the app it seems the synchronization is not on point

---

<div class="post-metadata">

**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, 10:11pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/230 "2026-08-05T22:11:12Z")

</div>

{  
“devId”: null,  
“uid”: null,  
“t”: null,  
“t\_local”: null,  
“cid”: null,  
“updatedAt”: “06/08/2026 00:11:00”,  
“dps”: {  
“1”: 24,  
“3”: “charger\_charging”,  
“4”: 13,  
“10”: 0,  
“13”: “controlpi\_6v”,  
“14”: “charge\_now”,  
“18”: true,  
“23”: “SS\_V1.0.2”,  
“24”: 53,  
“25”: 174,  
“27”: “online”  
}  
}

For DP6, with the help of Claude (i can see the value in your app settings when I look on cloud lookup) :

## Decoding the `phase_a` raw DP (DP 6) on Tuya EV chargers

For anyone else digging into the local Tuya DPs on an EV charger, DP 6 (`phase_a`, type `raw`) isn’t garbage — it’s just Base64-encoded binary data containing the electrical measurements for phase A.

Example value from my charger:

```auto
CXAANA8ADJU=

```

Decoding this Base64 string gives 8 raw bytes:

```auto
09 70 00 34 0f 00 0c 95

```

These 8 bytes break down into three fields (this matches the standard format Tuya uses across several energy-metering/EV-charger devices):

| Field | Bytes | Raw value | Scaling | Result |
| --- | --- | --- | --- | --- |
| Voltage | `09 70` (2 bytes, big-endian uint16) | 2416 | ÷ 10 | **241.6 V** |
| Current | `00 34 0f` (3 bytes, big-endian uint24) | 13327 | ÷ 1000 (mA → A) | **13.327 A** |
| Power | `00 0c 95` (3 bytes, big-endian uint24) | 3221 | no scaling (already in W) | **3221 W** |

Sanity check: V × I = 241.6 × 13.327 ≈ 3220 W, which matches the decoded power value almost exactly — confirming the byte layout and scaling factors are correct.

So in this example, the charger was pulling ~3.2 kW at 241.6 V / 13.3 A on phase A, which also lined up with `charge_cur_set` (DP 4) being set to 13 A and `work_state` (DP 3) showing `charger_charging`.

If your charger is three-phase, you’d likely find equivalent `phase_b` / `phase_c` raw DPs using the same 8-byte layout.

---

<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:** [August 5, 2026, 10:32pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/231 "2026-08-05T22:32:02Z")

</div>

Perfect - new TEST version is published

Please send some screenshots of the device and Energy Dashboard as well.

Thank you (and good night)

---

<div class="post-metadata">

**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, 10:37pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/232 "2026-08-05T22:37:54Z")

</div>

Tested on the latest version ( **1.0.150** )

For the device :

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/c/ec3d6654d25c8a458d6ba98ea43ef824ab024a2b.png)  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/4/e4419dc545c6b7096be7806f3298d68804beb1b1.jpeg)  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/d/6d414379dec463c3b14f6c184586609b54ae5ec7.jpeg)  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/5/e/5e8a343bf65f2ea5726aefb65d4f2038a37c9a3a.jpeg)  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/9/e95aa5a545b060901b6db4b0b893d07d871fd02e.jpeg)  
 ![2026-08-06_00h44_55](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/3/b3ac7c8d55d56b090888035982af680bd29951a7.jpeg)

And device is now showing in energy dashboard with the Instant Power data, but refresh does not seem to respect the 10 or 20sec, like 5min after the app is started, it stops refreshing and shows “2mins ago” for Power, VOltage and Current. I’ll post again tomorrow to see if refresh is still bugged and same for energy dashboard

One more thing I noticed is that icon is not showing on device on mobile app (android).

---

<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:** [August 6, 2026, 4:36pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/233 "2026-08-06T16:36:18Z")

</div>

Hi Elliot

Could you please try version 1.0.153

Andi

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [August 6, 2026, 6:58pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/234 "2026-08-06T18:58:28Z")

</div>

Hi Andy,

EDIT:  
Maybe it is not an issue, while `blinds`, `curtains` and `sunshade` are valid classes as well. It depends on the possibilities of the device:  
[https://apps.developer.homey.app/the-basics/devices/best-practices/window-coverings](https://apps.developer.homey.app/the-basics/devices/best-practices/window-coverings)

**Original post** :  
Is it possible to set the curtain motor class by default to `windowcoverings` instead of `blinds`?  
Usually we can select a virtual class at “what’s plugged in” when the device class is `windowcoverings`.  
(I’m aware of a possible breaking change)

Common curtains setting:

 ![15061](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/d/bda83df5d2e5995b6577fe27f215ccef623d09d5.jpeg)

Developer page device info:

 ![15051](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/7/f7bc785cdfe59e56f3d75b21ec2a9fbcddac850f.jpeg)

Tuya Local curtains (no “plugged in” section):

 ![15064](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/5/15946e09aca012360ea011667e900df5e897594c.jpeg)

Developer page device info:

 ![15048](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/b/6bcad23595a2987ee0b1d594319493a71efe42dd.jpeg)

Background:  
While I wanted to replace a Tuya cloud based curtain device with the Tuya Local version of that device in related flows, using the [Flow Converter app](https://community.homey.app/t/app-pro-flow-converter/154906), it responded with “class mismatch”.  
This can be overridden and it succeeded, but it will leave regular users puzzled I guessume.

---

<div class="post-metadata">

**Author:** ![Pieter\_Pessers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pieter_pessers/32/8848_2.png) [@Pieter\_Pessers](https://community.homey.app/u/Pieter_Pessers)\
**Post date:** [August 6, 2026, 9:05pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/235 "2026-08-06T21:05:21Z")

</div>

Hello @Andi. I just installed v1.0.156 and it seems that my bseed wifi 2 button wall switch is working. Very happy with that. Thanks.

---

<div class="post-metadata">

**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 6, 2026, 9:32pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/236 "2026-08-06T21:32:05Z")

</div>

Hi Andi! Icon is now showing perfectly on mobile as well!

I dont have energy dashboard because i’m on homey pro 2019. But you’ll find below the screenshots of insights view:

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/a/6a6711811f1604b005f98db85fce8a672bb43c92.png)  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/0/e07f854dd7b5b1169d36d75243a4da2a564a90c0.png)  
 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/5/e598a081c830f9161c32755fd6a7961baac060f8.png)

It doesnt seem to show the cumulative energy used or my configuration needs update?

---

<div class="post-metadata">

**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 6, 2026, 10:18pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/237 "2026-08-06T22:18:41Z")

</div>

Andi, other notes relative to my screenshots :

Current handling as target\_power and the local energy accumulation are working well overall. Two things I ran into today, most likely useful for other qccdz units too.

**1. Crash on phase\_a decode (buffer length mismatch)**

Log from the app:

```auto
[ERR] The value of "offset" is out of range. It must be >= 0 and <= 6. Received 8
[WRN] Disconnected: The value of "offset" is out of range. It must be >= 0 and <= 6. Received 8

```

This killed the connection and forced a reconnect. Looks like it’s the phase\_a parser trying to read at a fixed offset assuming an 8-byte buffer, but got a shorter one back (you already handle the 7-byte variant elsewhere in `_parsePhase`, e.g. the Nine/Amperepoint/Noeifevo comment, so probably just this one read call not going through that same length check). Happened once overnight, early morning, charger idle, so it’s not tied to any particular DP value, just an occasional shorter payload from the device.

**2. Firmware-side session energy glitch (not a driver bug, but might be worth a sanity guard)**

Had a weird one today: charged the car at home only, went from 50% to 63% battery (~9-10 kWh by my estimate, matches the ~2kW plateau I saw on the power tile over about 4 hours total). But `charge_session_energy` (dp25 on my unit) suddenly reported **48.30 kWh** for that session, about 2 hours after charging had actually stopped. Pulled the raw DP debug at the time and confirmed it’s not a Homey-side computation. The device itself sent `"25": 4830` (raw), so this is a firmware-side glitch, not your driver misreading anything.

Looking at my car’s charge history, there were two very short restart blips right in the middle of that session (charging stopped/started again twice within 7-10 seconds each, around the same time). My guess is that confused the charger’s own internal session tally.

Not asking you to work around Tuya firmware bugs, but since this flows straight into `meter_power.charged` via the delta accumulation, one bad session reading like this permanently corrupts the lifetime total until someone notices and manually resets it. Might be worth a basic implausibility check before accumulating a delta, e.g. skip/flag deltas that would imply an unrealistic average power for the elapsed time since the last session end (something like delta\_kWh / hours\_since\_last\_session\_end vs. current\_limit × voltage as a rough ceiling). Not a big deal, just flagging it since I only caught it because I happened to be watching the dashboard that day.

---

<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:** [August 6, 2026, 11:44pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/238 "2026-08-06T23:44:48Z")

</div>

> [@Elliot\_Hallais](#):
>
> It doesnt seem to show the cumulative energy used or my configuration needs update?

Your wallbox was added before version 1.0.147, and Homey doesn’t apply updated default values to existing devices. That’s why the session‑energy DP on your setup still points to DP 25 — the counter from the previous session, which doesn’t change while charging. The counter that actually increases during charging is DP 1, but right now it’s being discarded as “Unknown DP”.

Fix: Go to the device settings and change the session‑energy DP from 25 to 1.

---

<div class="post-metadata">

**Author:** ![Andi](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andi/32/160466_2.png) [@Andi](https://community.homey.app/u/Andi)\
**Post date:** [August 6, 2026, 11:49pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/239 "2026-08-06T23:49:30Z")

</div>

Hi Peter - If I change the device class, only newly added drivers will use the new class. So it would not break existing devices. Changing existing drivers with a migration ( `getClass()` and`setClass()`) would break all configured flows ☹

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:** [August 6, 2026, 11:53pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/240 "2026-08-06T23:53:09Z")

</div>

> [@Elliot\_Hallais](#):
>
> Two things I ran into today, most likely useful for other qccdz units too.

Hi Elliot,

Thanks — both of these were spot on, and both are fixed in **1.0.158**. One correction on where the first one actually came from.

**1. The disconnect — it wasn’t the phase parser**

Reasonable inference, but the numbers point elsewhere. `_parsePhase` has a length guard (`if (buf.length < 7) return null`) and only does one bounds-checked read, at fixed offset 0. Everything after that is plain index access, which yields `undefined` rather than throwing.

I reproduced the exact message instead:

```auto
readUInt32BE(8) on a 10-byte buffer
  → "The value of 'offset' is out of range. It must be >= 0 and <= 6. Received 8"

```

Byte-for-byte identical to your log. That call is in tuyapi’s `message-parser.js:148`, reading the _command byte_ out of the packet header — so what arrived was a truncated 10-byte TCP frame, not a short phase payload. Which fits your observation that it happened while the charger was idle and wasn’t tied to any DP value.

The real bug was on my side though: the app’s error handler didn’t recognise parse errors, so it treated them as fatal and tore down the connection. A single malformed frame shouldn’t do that — the socket was fine. Parse errors now join the exemptions I already had for error 904, error 900 and status timeouts: logged, connection kept. That applies to all drivers, not just chargers.

**2. Session energy glitch — guard implemented as you suggested**

Implemented essentially your formula:

```auto
ceiling = current_max × voltage × phases × elapsed_time × 1.25 + 0.5 kWh

```

The 1.25 absorbs mains above nominal, the 0.5 kWh keeps short poll intervals from producing an absurdly tight bound.

Against your case: a 38.8 kWh jump roughly 30 seconds after the previous reading, versus a ceiling of about 0.54 kWh → rejected, logged, lifetime total untouched.

I checked it doesn’t eat legitimate readings:

| Case | Result |
| --- | --- |
| 1.8 kWh over 30 min at 3.7 kW | accepted |
| 29 kWh after Homey was offline 8 h mid-charge | accepted |
| 10 kWh over 30 min, 22 kW three-phase | accepted |
| first reading after a restart | accepted (no baseline to judge against) |
| your 38.8 kWh in 30 s | rejected |

The ceiling scales off the configured current limit and phase count, so it adapts per device.

One thing it can’t do is repair the damage already done — your total is still carrying that bad session. The **Reset energy meter** flow action zeroes it, and it rebuilds cleanly from there.

**While I’m at it — unrelated, but worth checking on your unit**

If your cumulative total looks stuck generally: chargers paired before 1.0.147 still have **Session Energy DP** set to `25`. On this hardware DP 25 holds the _previous_ session and doesn’t move during a charge; the counter that actually climbs is **DP 1**. Homey doesn’t apply changed defaults to existing devices, so it needs changing by hand once. As of 1.0.157 the log now points this out when it spots an unmapped DP counting up.

Thanks again — the raw DP dump and the detail about the two restart blips is exactly what made both of these diagnosable.

Andi

---

<div class="post-metadata">

**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 7, 2026, 3:59pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/241 "2026-08-07T15:59:52Z")

</div>

Perfect I tried with new version after doing a reset and changing DP and here are the graphs :

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/a/2af698a70e24eb1f55b3a8630b18bbcf53b8f5aa.png)

As you can see, the maths seem a bit off because with first charge, Charged Energy only went from 0 to 0,002kWh, and with the second charge it went from 0,002kWh to 2,02kWh. I was expecting (from the power graph) 0,78 kWh for the first charge (30min at 1556W) and 1,556 kWh for the second charge (1h at 1556W). End result 2,02kWh seems almost correct, but it incremented a bit too late?

Other than that all others points are covered from my point of view!

---

<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:** [August 7, 2026, 4:29pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/242 "2026-08-07T16:29:05Z")

</div>

Hi Elliot - Which values do you see in the normal Tuya App?

---

<div class="post-metadata">

**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 7, 2026, 5:21pm UTC](https://community.homey.app/t/app-pro-tuya-local/154077/243 "2026-08-07T17:21:39Z")

</div>

I don’t see any record in Tuya App because charge is done by another user than myself (user is your app so it doesnt show on my Tuya account)

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

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