Tuya T&H Sensor (001TH0202_CB3S / tdq) – no entities/unsupported, anyone solved?

[mrnmhl87h24-ui]

The problem
I cannot get temperature and humidity entities from my Tuya T&H Sensor (model: 001TH0202_CB3S, category: tdq).
The device is detected in Home Assistant via both Tuya Cloud and LocalTuya integrations, but no entities are created or exposed.
The UI shows "unsupported", and the diagnostic JSON has empty function, status_range, and status fields.

I tried all protocol versions (3.1, 3.2, 3.3, 3.4), mapped DPS manually (1-8), set scan interval, and confirmed the device IP, ID, and local key (from Tuya IoT).
LocalTuya shows an unknown error and doesn’t present any DPS values.

Is there any known solution to expose entities for this device, or is it confirmed not supported?

Environment
Localtuya version: 5.2.3
Home Assistant Core version: 2026.1.1 (HAOS)
Does the device work using the Home Assistant Tuya Cloud component ? Device is detected, but no entities are exposed.
Does the device work using the Tinytuya (https://github.com/jasonacox/tinytuya) command line tool ? Could not get any DP values — only device metadata.
Was the device working with earlier versions of localtuya ? No
Are you using the Tuya/SmartLife App in parallel ? Yes
Steps to reproduce
Add device to Smart Life (Tuya app) — visible/working there.
Set up Tuya integration (cloud) — device detected, shows as unsupported, no entities.
Set up LocalTuya with device IP, ID, and local key, protocol versions tested.
Manual mapping for DPS 1-8, set scan interval (10s).
No entities and no data received.
DP dump
Unfortunately, either through LocalTuya or Tinytuya, all dump attempts return empty "function", "status_range" and "status" fields.
Example diagnostics:

JSON
"function": {},
"status_range": {},
"status": {},
"entities": []
Provide Home Assistant traceback/logs
Text
2026-01-15 20:12:01 ERROR (MainThread) [custom_components.localtuya] Unknown error connecting to device bf5521e446909f2407tq7q at 192.168.1.26
2026-01-15 20:12:01 ERROR (MainThread) [custom_components.localtuya] No DPS value detected for device bf5521e446909f2407tq7q
(The log repeats for every attempt at reconfiguration or protocol change.)

Additional information
Device appears as online in the Tuya/Smart Life app and correctly displays temperature and humidity.
All DP data appears inaccessible via both cloud and LAN/localtuya.
Device info:
Device ID: bf5521e446909f2407tq7q
Model: 001TH0202_CB3S
Category: tdq
IP: 192.168.1.26
Local Key: -?iCstS35?l7#w/;
Is this model known to be completely unsupported (cloud and local)?
Any tips for getting the entities for temperature/humidity to appear in HA?

Thanks in advance!

[millenniumy2k]

same problem

[KraverekPL]

Same problem here. DP is working and IOT Tuya see them. But they are not opened for the world.

[tcnewone]

same problem

[KraverekPL]

I fixed it on my side. Use shadow properties and download those data from Tuya cloud.

[matteshe]

I fixed it on my side. Use shadow properties and download those data from Tuya cloud.

Can you explain this in more detail, what and how you fixed it?

[KraverekPL]

I fixed it on my side. Use shadow properties and download those data from Tuya cloud.

Can you explain this in more detail, what and how you fixed it?

This does NOT use LocalTuya / local keys. It pulls values from Tuya Cloud shadow properties using only device_id + Tuya Cloud API keys.

#!/usr/bin/env python3
import sys, json, hmac, hashlib
from datetime import datetime, timezone
from urllib.request import Request, urlopen

# --- set these ---
CLIENT_ID = "YOUR_ACCESS_ID"
CLIENT_SECRET = "YOUR_ACCESS_SECRET"

# pick your region:
BASE_URL = "https://openapi.tuyaeu.com"   # EU
# BASE_URL = "https://openapi.tuyaus.com" # US
# BASE_URL = "https://openapi.tuyacn.com" # CN

EMPTY_BODY_SHA256 = "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
LOGIN_URL = "/v1.0/token?grant_type=1"
SHADOW_URL = "/v2.0/cloud/thing/{device_id}/shadow/properties"

def ts_ms() -> str:
    return str(int(datetime.now(timezone.utc).timestamp() * 1000))

def sign(msg: str) -> str:
    return hmac.new(CLIENT_SECRET.encode(), msg.encode(), hashlib.sha256).hexdigest().upper()

def http_get(path: str, headers: dict) -> dict:
    req = Request(BASE_URL + path, headers=headers, method="GET")
    with urlopen(req, timeout=15) as r:
        return json.loads(r.read().decode("utf-8"))

def get_token() -> str:
    t = ts_ms()
    s = CLIENT_ID + t + "GET\n" + EMPTY_BODY_SHA256 + "\n\n" + LOGIN_URL
    headers = {"client_id": CLIENT_ID, "t": t, "sign_method": "HMAC-SHA256", "sign": sign(s)}
    data = http_get(LOGIN_URL, headers)
    if not data.get("success"):
        raise RuntimeError(data)
    return data["result"]["access_token"]

def get_shadow(token: str, device_id: str) -> dict:
    path = SHADOW_URL.format(device_id=device_id)
    t = ts_ms()
    s = CLIENT_ID + token + t + "GET\n" + EMPTY_BODY_SHA256 + "\n\n" + path
    headers = {
        "client_id": CLIENT_ID, "access_token": token, "t": t,
        "sign_method": "HMAC-SHA256", "sign": sign(s),
    }
    data = http_get(path, headers)
    if not data.get("success"):
        raise RuntimeError(data)
    props = (data.get("result") or {}).get("properties") or []
    return {p["code"]: p.get("value") for p in props if "code" in p}

if __name__ == "__main__":
    if len(sys.argv) != 2:
        raise SystemExit("usage: python3 tuya.py <device_id>")
    device_id = sys.argv[1]
    token = get_token()
    print(json.dumps(get_shadow(token, device_id)))

Run it: python3 tuya.py YOUR_DEVICE_ID

you shopuld response like this: {"temp_current":229,"humidity_value":31,"battery_state":"high"}

in HA add new sensor to configuration file:

- sensor: command: "python3 /config/tuya.py YOUR_DEVICE_ID" name: "TH01" unique_id: th01 device_class: temperature state_class: measurement unit_of_measurement: "°C" scan_interval: 1800 value_template: "{{ (value_json.temp_current | float / 10) | round(1) }}" json_attributes: - humidity_value - battery_state - temp_unit_convert

remember about scan interval, it cannot be smaller than 15 mins otherwise Tuya Cloud will block it after two days.

and thats all.
you re welcome.

Restart HA, and thats all. new entity will be there.

[KraverekPL]

You need Tuya Cloud API credentials.

Get them here:

1. Go to https://iot.tuya.com
2. Cloud → Projects → select your project
3. Open “Overview”
4. Copy:
   • Access ID → CLIENT_ID
   • Access Secret → CLIENT_SECRET

These are Tuya Cloud API keys (not Smart Life login/password).

[grrolim]

@KraverekPL , thanks for your script. The python code worked perfectly, but I couldn't make it work in Home Assistant...
I wasn't able to make the sensor appear in the developer tools states and when I tried to run the action python_scripts.tuya, I got an error: "Failed to process the returned action response data, expected a dictionary, but got <class 'NoneType'>."

Do you have any idea of what I am doing wrong?

Thanks

[KraverekPL]

@KraverekPL , thanks for your script. The python code worked perfectly, but I couldn't make it work in Home Assistant... I wasn't able to make the sensor appear in the developer tools states and when I tried to run the action python_scripts.tuya, I got an error: "Failed to process the returned action response data, expected a dictionary, but got <class 'NoneType'>."

Do you have any idea of what I am doing wrong?

Thanks

You’re doing two things wrong.
First, you’re running it as python_scripts.tuya – that integration cannot return data and will always give None, so it will never create a sensor. This script must be used via a command_line sensor, not python_script.
Second, Home Assistant runs the command inside its own environment/container, so the script must be accessible as /config/tuya.py from HA, not from your host path.

Put the script in the HA config directory so it is visible as /config/tuya.py, call it with command: "python3 /config/tuya.py DEVICE_ID", restart HA, then the sensor will appear in Developer Tools → States.

[LegionSMOKEZ]

@KraverekPL , thanks for your script. The python code worked perfectly, but I couldn't make it work in Home Assistant... I wasn't able to make the sensor appear in the developer tools states and when I tried to run the action python_scripts.tuya, I got an error: "Failed to process the returned action response data, expected a dictionary, but got <class 'NoneType'>."
Do you have any idea of what I am doing wrong?
Thanks

You’re doing two things wrong. First, you’re running it as python_scripts.tuya – that integration cannot return data and will always give None, so it will never create a sensor. This script must be used via a command_line sensor, not python_script. Second, Home Assistant runs the command inside its own environment/container, so the script must be accessible as /config/tuya.py from HA, not from your host path.

Put the script in the HA config directory so it is visible as /config/tuya.py, call it with command: "python3 /config/tuya.py DEVICE_ID", restart HA, then the sensor will appear in Developer Tools → States.

Appreciate your help thus far, would like to say that much as I'm further now than ever before....

Script works and returns the data as anticipated (from terminal) - My HA is containerized/docker, I'm currently stuck at how to add the entity to HA manually?

What file do I add the "entity" code to? What do you mean by "call it with command" - meaning from terminal? (Did that, returned the data successfully as stated above.)

Much thanks! Anticipating your response. 😀

[KraverekPL]

@KraverekPL , thanks for your script. The python code worked perfectly, but I couldn't make it work in Home Assistant... I wasn't able to make the sensor appear in the developer tools states and when I tried to run the action python_scripts.tuya, I got an error: "Failed to process the returned action response data, expected a dictionary, but got <class 'NoneType'>."
Do you have any idea of what I am doing wrong?
Thanks

You’re doing two things wrong. First, you’re running it as python_scripts.tuya – that integration cannot return data and will always give None, so it will never create a sensor. This script must be used via a command_line sensor, not python_script. Second, Home Assistant runs the command inside its own environment/container, so the script must be accessible as /config/tuya.py from HA, not from your host path.
Put the script in the HA config directory so it is visible as /config/tuya.py, call it with command: "python3 /config/tuya.py DEVICE_ID", restart HA, then the sensor will appear in Developer Tools → States.

Appreciate your help thus far, would like to say that much as I'm further now than ever before....

Script works and returns the data as anticipated (from terminal) - My HA is containerized/docker, I'm currently stuck at how to add the entity to HA manually?

What file do I add the "entity" code to? What do you mean by "call it with command" - meaning from terminal? (Did that, returned the data successfully as stated above.)

Much thanks! Anticipating your response. 😀

Since Home Assistant is running in Docker, the script must be visible inside the container. Put tuya.py in your HA config folder so HA sees it as /config/tuya.py. I have my HA confing outside the container, in /config directory to easier update image.
You do not add the entity manually in the UI. The entity is created by a command_line sensor in YAML.

You must add this directly to your configuration.yaml.
Home Assistant will not create the entity from the UI.

Open configuration.yaml and paste this at the end (adjust DEVICE_ID):

command_line:
  - sensor:
      name: "TH01"
      unique_id: th01
      command: "python3 /config/tuya.py DEVICE_ID"
      scan_interval: 1800
      device_class: temperature
      state_class: measurement
      unit_of_measurement: "°C"
      value_template: "{{ (value_json.temp_current | float / 10) | round(1) }}"
      json_attributes:
        - humidity_value
        - battery_state
        - temp_unit_convert

Make sure tuya.py is inside the HA config directory so it is visible as /config/tuya.py in the container.
Then fully restart Home Assistant.
After restart, the sensor will appear automatically in Developer Tools in states or entities.

So to sum up:
sensors data is going to config file (HA one)
python script need to be in config file becase sensor are invoking them, by "command: "python3 /config/tuya.py DEVICE_ID""

I hope it helps.

[LegionSMOKEZ]

@KraverekPL , thanks for your script. The python code worked perfectly, but I couldn't make it work in Home Assistant... I wasn't able to make the sensor appear in the developer tools states and when I tried to run the action python_scripts.tuya, I got an error: "Failed to process the returned action response data, expected a dictionary, but got <class 'NoneType'>."
Do you have any idea of what I am doing wrong?
Thanks

You’re doing two things wrong. First, you’re running it as python_scripts.tuya – that integration cannot return data and will always give None, so it will never create a sensor. This script must be used via a command_line sensor, not python_script. Second, Home Assistant runs the command inside its own environment/container, so the script must be accessible as /config/tuya.py from HA, not from your host path.
Put the script in the HA config directory so it is visible as /config/tuya.py, call it with command: "python3 /config/tuya.py DEVICE_ID", restart HA, then the sensor will appear in Developer Tools → States.

Appreciate your help thus far, would like to say that much as I'm further now than ever before....

Script works and returns the data as anticipated (from terminal) - My HA is containerized/docker, I'm currently stuck at how to add the entity to HA manually?

What file do I add the "entity" code to? What do you mean by "call it with command" - meaning from terminal? (Did that, returned the data successfully as stated above.)

Much thanks! Anticipating your response. 😀

Since Home Assistant is running in Docker, the script must be visible inside the container. Put tuya.py in your HA config folder so HA sees it as /config/tuya.py. I have my HA confing outside the container, in /config directory to easier update image.
You do not add the entity manually in the UI. The entity is created by a command_line sensor in YAML.

You must add this directly to your configuration.yaml.
Home Assistant will not create the entity from the UI.

Open configuration.yaml and paste this at the end (adjust DEVICE_ID):

command_line:
  - sensor:
      name: "TH01"
      unique_id: th01
      command: "python3 /config/tuya.py DEVICE_ID"
      scan_interval: 1800
      device_class: temperature
      state_class: measurement
      unit_of_measurement: "°C"
      value_template: "{{ (value_json.temp_current | float / 10) | round(1) }}"
      json_attributes:
        - humidity_value
        - battery_state
        - temp_unit_convert

Make sure tuya.py is inside the HA config directory so it is visible as /config/tuya.py in the container.
Then fully restart Home Assistant.
After restart, the sensor will appear automatically in Developer Tools in states or entities.

So to sum up:
sensors data is going to config file (HA one)
python script need to be in config file becase sensor are invoking them, by "command: "python3 /config/tuya.py DEVICE_ID""

I hope it helps.

Extremely happy to report that it's working perfectly! Bravo!!

I do however have one more question to pick your brain with - I noticed that the humidity and battery attributes exist within the sensor... Is there a way that I can convert these attributes into sensors of their own? i.e... also be able to display humidity and battery state(s) on a card? Similar to how I have my others? (Pic attached)

Note: The "Bedroom" temp sensor is the device in question.

Thanks a ton again brother! This solution is going to make quite a few people happy - Assuming this will work similarly for other devices that have support issues?

@Cheng-Logic Appreciate you as well! 👍

[KraverekPL]

Its all about template. Im creating my templates by my own and taking entity data as java script variables so I can do whatever I need to do with them.

[LegionSMOKEZ]

Its all about template. Im creating my templates by my own and taking entity data as java script variables so I can do whatever I need to do with them.

Could you potentially share an example template of yours? Preferably one similiar to this, if possible? 😅 - I'm still familiaring myself with templating, I also have a "GW003" (generic Tuya G2 BT/WiFi gateway from AliExpress.) that is next for me to tackle on the list, as the shadow script also worked for that device. (Again, much appreciated for that.)

It would be nice to vibecode an integration that specifically sets up Tuya devices via pulling shadow properties. (For non-supported devices) - This seems easier than relying on another developer or Tuya themselves for support. Which, the latter have apparently abandoned the "official" (cloud) integration as of sometime in 2025.

As for finalizing this TH02 variant (code from configuration.yaml pasted below) it seems as though I can only manage to get the Temp and Humidity sensors working, not the battery state. I also feel as though I did this incorrectly, as it's calling the command 3 times vs just extracting the attributes into standalone sensors of their own.

Note 1: I currently have the "round" value set to "2" for humidity, as it was reporting as 3.0% instead of 30.0%. (Decimal was off by 1.)

Note 2: Battery state appears to be low/medium/high for reporting instead of percentage, odd... but that's something to note as I currently have it configured for a numerical value/unit as "%".

command_line:
  - sensor:
      name: "Bedroom Climate Sensor - Temperature"
      unique_id: bedroom_climate_sensor
      command: "python3 tuya.py ebd4b4f2a9f80747bxxxxx"
      scan_interval: 1800
      device_class: temperature
      state_class: measurement
      unit_of_measurement: "°C"  #NOTE: Setting to "°F" changes reporting to C°.
      value_template: "{{ (value_json.temp_current | float / 10) | round(1) }}"
      json_attributes:
        - humidity_value
        - battery_state
        - temp_unit_convert
  - sensor:
      name: "Bedroom Climate Sensor - Humidity"
      unique_id: bedroom_climate_sensor_humidity
      command: "python3 tuya.py ebd4b4f2a9f80747bxxxxx"
      scan_interval: 1800
      unit_of_measurement: "%"
      device_class: humidity
      state_class: measurement
      value_template: "{{ value_json.humidity_value | float / 10 | round(2) }}"
  - sensor:
      name: "Bedroom Climate Sensor - Battery"
      unique_id: bedroom_climate_sensor_battery
      command: "python3 tuya.py ebd4b4f2a9f80747bxxxxxx"
      scan_interval: 1800
      unit_of_measurement: "%"
      device_class: battery
      value_template: "{{ value_json.battery_state | float / 10 | round(1) }}"

Thanks again for all this, you rock! 🤟

---

EDIT/FOLLOW-UP: I took the code that @Cheng-Logic posted (and I believe deleted after?) of "template" coding to add to the **"configuration.yaml**" - It appears to have worked as I can now see a helper/template sensor listed for both Humidity and Battery.

The template code block from my configuration.yaml -

template:
  - sensor:
    - name: "Bedroom Climate Sensor - Humidity"
      unique_id: bedroom_sensor_humidity
      unit_of_measurement: "%"
      device_class: humidity
      state: "{{ state_attr('sensor.bedroom_climate_sensor', 'humidity_value') }}"
    - name: "Bedroom Climate Sensor - Battery"
      unique_id: bedroom_sensor_battery
      unit_of_measurement: "%"
      device_class: battery
      state: "{{ state_attr('sensor.bedroom_climate_sensor', 'battery_state') }}"

I would still appreciate looking at your tempating if you don't mind? Since I'm unsure of how other types of sensors would work such as alarms, rebooting, and status (which reports either "OK" or "Problem", for example.)