LocalTuya not recognizing entities even when DPs are specified

Third party integrations
1

I’ve used localtuya in the past without any issue. Wifi devices has been easy to integrate, if perhaps a bit cumbersome because the developer account in iot.tuya.com expires every few months. But the new device I bought (a irrigation timer) doesn’t seem to work.

LocalTuya doesn’t find any entities (the DPs) automatically, and even if I specify the dp_id of the entities as reported by the API explorer of localtuya, it doesn’t work, all entities report a value of -1. What might be going on? I couldn’t find any troubleshooting for cases like this.

This is what the API explorer report from the device (only the first two fields are important to me).

    "properties": [
      {
        "code": "switch_1",
        "custom_name": "",
        "dp_id": 1,
        "time": 1750682068396,
        "type": "bool",
        "value": false
      },
      {
        "code": "countdown_1",
        "custom_name": "",
        "dp_id": 9,
        "time": 1750681581116,
        "type": "value",
        "value": 4
      },
      {
        "code": "irrigation_log_1",
        "custom_name": "",
        "dp_id": 101,
        "time": 1750682068441,
        "type": "raw",
        "value": "AAfpBhcNIhsGAA=="
      },
      {
        "code": "cycle_timing",
        "custom_name": "",
        "dp_id": 102,
        "time": 1750681581497,
        "type": "raw",
        "value": "AA=="
      },
      {
        "code": "no_irrigation_timing",
        "custom_name": "",
        "dp_id": 103,
        "time": 1750681581689,
        "type": "raw",
        "value": "AAAAAAAAAA=="
      },
      {
        "code": "weather_switch",
        "custom_name": "",
        "dp_id": 104,
        "time": 1750681581116,
        "type": "bool",
        "value": false
      },
      {
        "code": "smart_weather",
        "custom_name": "",
        "dp_id": 105,
        "time": 1750681581116,
        "type": "enum",
        "value": "sun"
      },
      {
        "code": "weather_delay",
        "custom_name": "",
        "dp_id": 106,
        "time": 1750681581116,
        "type": "enum",
        "value": "cancel"
      },
      {
        "code": "rain_sensor_switch",
        "custom_name": "",
        "dp_id": 107,
        "time": 1750681581116,
        "type": "bool",
        "value": false
      },
      {
        "code": "rain_sensor_state",
        "custom_name": "",
        "dp_id": 108,
        "time": 1750681581183,
        "type": "enum",
        "value": "no_rain"
      },
      {
        "code": "switch_choose",
        "custom_name": "",
        "dp_id": 109,
        "time": 1750421451838,
        "type": "raw"
      },
      {
        "code": "timer",
        "custom_name": "",
        "dp_id": 110,
        "time": 1750681581221,
        "type": "raw",
        "value": "AA=="
      }
    ]

Both fields report a value of -1, which seems inconsistent with what the API explorer reports:

Screenshot 2025-06-24 at 13.23.19
Screenshot 2025-06-24 at 13.23.191250×2286 130 KB

Screenshot 2025-06-24 at 13.23.04
Screenshot 2025-06-24 at 13.23.041252×1260 90 KB

Any idea of what is going on?

2

Hello Miguel Camba,

What does the developer say?
Also is there a LocalTuya thread on here where other users may see this better?

Here’s a search string for your favorite search engine, it might help

site:community.home-assistant.io LocalYuya

3

Hmmm…this never happened to me (yet)?
Running it now for more then 3 years now🤔

Which repository are you using?

4

I couldn’t find information about similar problems on a first level search, so I asked here. I also asked on the GH repo before, but no answer yet.l

ChatGPT mentioned something about the dp_ids being obfuscated/hidden but I couldn’t find any information about that either, so I’m not sure if it made that up.

5

And the developer credentials expiring happened a few times but it’s only needed if you want to add new devices, and renewing is just a matter of asking and waiting a few minutes. Not a big deal. Once added devices work even if your develop account expires.