Support for add_ele Handling in LocalTuya

[omerfaruk-aran]

LocalTuya Version

2025.1.1

Home Assistant Version

2025.1.2

Environment

• Does the device work using the Home Assistant Tuya Cloud component?
• Is this device connected to another local integration, including Home Assistant and any other tools?
• The devices are within the same HA subnet, and they get discovered automatically when I add them

What happened?

Local Tuya does not process the add_ele (Incremental Energy Consumption) data point correctly. This data point provides incremental energy consumption (in Wh) over a specific interval, but Home Assistant does not capture these values when they remain constant. This causes energy tracking issues in the Home Assistant Energy Dashboard.

For example, my device sends the following data repeatedly for add_ele:

{ "dp_id": 17, "code": "add_ele", "value": 100, "time": 1737326577000 }

Despite multiple packets being sent, Home Assistant does not update the entity or sum the values, resulting in incorrect total energy consumption readings.

Steps to reproduce.

1. Add a Tuya device with the add_ele data point using Local Tuya.
2. Monitor the add_ele value in Home Assistant while the device sends the same value repeatedly over time.
3. Check the Energy Dashboard and note the incorrect or missing energy consumption calculations.

Relevant log output

No error logs are generated because this issue is related to how data points are processed rather than a runtime error. Below is an example of the add_ele data received from the Tuya device:

{
    "dp_id": 17,
    "code": "add_ele",
    "value": 100,
    "time": 1737326577000
}

This value is sent repeatedly, but Home Assistant does not capture or process the data unless the value changes.

Diagnostics information.

Diagnostics information is attached below for the relevant device. The device supports the following data points:

{
  "code": "add_ele",
  "custom_name": "",
  "dp_id": 17,
  "time": 1737326577000,
  "type": "value",
  "value": 100
},
{
  "code": "cur_current",
  "custom_name": "",
  "dp_id": 18,
  "time": 1737326951985,
  "type": "value",
  "value": 2733
},
{
  "code": "cur_power",
  "custom_name": "",
  "dp_id": 19,
  "time": 1737326951985,
  "type": "value",
  "value": 5489
},
{
  "code": "cur_voltage",
  "custom_name": "",
  "dp_id": 20,
  "time": 1737326941388,
  "type": "value",
  "value": 2309
}

The focus is on the add_ele data point, which provides incremental energy consumption but does not trigger updates in Home Assistant.

[xZetsubou]

And what's is add_ele should be? for my one of device this DP doesn't get automatically detect without cloud so can it works locally?
if so does the value total? because it doesn't then seems that it's increasing forever till reset it manually or perhaps device it self do the reset each reboot? check the device diagnostics add_ele is read-write Integer not read-only.

[omerfaruk-aran]

Thank you for your response and insights regarding the add_ele data point. Based on my observations and tests, here's what I have noticed and my situation:

1. add_ele Value Behavior:

   • The add_ele value always remains at 100 in my case, and the only changing field is "time". This suggests that the data point might not represent cumulative energy consumption directly or is not being updated correctly by the device.
   • I initially thought that add_ele might represent incremental energy consumption in Wh, but without any changes in its value, this assumption cannot be confirmed.

2. Device Purpose:

   • The device provides cur_current, cur_power, and cur_voltage data points, which are correctly displayed in Local Tuya and Home Assistant. However, my primary goal for purchasing this DIN rail breaker was to monitor total energy consumption in my home and track it within Home Assistant's Energy Dashboard.
   • Unfortunately, I currently cannot access total energy consumption data through the device.

3. Additional Context:

   • I found a discussion regarding this device on the Home Assistant Community Forum: Tongou DIN Electricity Monitors. In many cases, users seem to resolve similar issues by flashing custom firmware. However, I would prefer to solve this issue via Local Tuya if possible, as I want to retain the device's stock firmware.

4. Request:

   • Is there a way to implement cumulative energy tracking using the cur_power (current power consumption) field, or could the add_ele value be processed differently to provide meaningful data for total energy consumption?
   • Any guidance on achieving this within Local Tuya would be greatly appreciated. If it's not feasible, recommendations for alternative solutions would also be helpful.

[xZetsubou]

To be honest I don't know if there is other solution to this and honestly I don't monitor my energy consumption so can't give much, however if the add_ele can be used somehow which I doubt then we need to know how it works, Are using cloud API with localtuya if so post the device diagnostics it contains dps_data where it tell what's the maximum/minimum values for it,