Tuya heater: climate state becomes unknown during OFF → HEAT transition

[osem34]

The problem

During OFF → HEAT transition the Tuya climate entity briefly enters state "unknown".

As a result:

• climate/set_hvac_mode fails with error:
  "expected HVACMode or one of 'off', 'heat', 'cool', 'heat_cool', 'auto', 'dry', 'fan_only'"
• Climate UI becomes grey and unusable
• This did not happen before recent Home Assistant updates

Important notes:

• Device is physically heating (work_power ~600–700W)
• Tuya mobile app works correctly
• When climate state is OFF everything is reported correctly
• hvac_modes are exposed as: off, heat

What version of Home Assistant Core has the issue?

Home Assistant version: 2025.12.3 Installation type: Home Assistant OS Tuya integration

What was the last working version of Home Assistant Core?

Unknown (worked before recent updates)

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tuya

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tuya/

Diagnostics information

tuya-01JZ2HC4N9RHTFG9Z5867S4G8N-Эко-обогреватель (с д...-983745add80f915652a69db367c58405 (Ввімкненно).json

Example YAML snippet

Not applicable. Issue occurs without custom YAML.

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @tuya, @zlinoliver, mind taking a look at this issue as it has been labeled with an integration (tuya) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tuya can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign tuya Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

tuya documentation
tuya source
_{^{(message by IssueLinks)}}

[oscarrgarciia]

See this, it may help!

[osem34]

Looks related to #158944. Same regression in 2025.12.3: during OFF → HEAT transition the Tuya climate entity becomes "unknown" and climate/set_hvac_mode fails. This might be the same root cause affecting different Tuya heater devices.

[epenet]

@osem34 can you please post full debug log https://www.home-assistant.io/docs/configuration/troubleshooting/#enabling-debug-logging

Start in OFF state

1 - enable logging
2 - transition from OFF -> HEAT (I want to understand what makes it go unknown as your diagnostics show "warnings": null)
3 - send climate/set_hvac_mode (what arguments are/were you sending?)
4 - disable logging, save, and attach log file to the ticket (maybe hide private information - or you can send it to me on Discord)

[oscarrgarciia]

DEBUG [homeassistant.components.tuya] Sending command to DEVICE_1: switch = False
DEBUG [tuya_sharing] Command accepted for DEVICE_1

DEBUG [tuya_sharing] MQTT message received for DEVICE_1
Payload:
{
"protocol": 4,
"data": {
"devId": "DEVICE_1",
"status": [
{
"dpId": 1,
"value": false
}
]
}
}

DEBUG [homeassistant.components.tuya] State update for DEVICE_1:
{
"switch": false,
"mode": "eco",
"frost": true,
"temp_set": 160,
"upper_temp": 350,
"temp_current": 130,
"humidity": 73,
"lower_temp": 50,
"temp_correction": 0,
"factory_reset": false,
"child_lock": false,
"fault": 0
}

DEBUG [homeassistant.components.tuya] Sending command to DEVICE_1: switch = True
DEBUG [tuya_sharing] Command accepted for DEVICE_1

DEBUG [tuya_sharing] MQTT message received for DEVICE_1
Payload:
{
"protocol": 4,
"data": {
"devId": "DEVICE_1",
"status": [
{
"dpId": 1,
"value": true
}
]
}
}

DEBUG [homeassistant.components.tuya] State update for DEVICE_1:
{
"switch": true,
"mode": "eco",
"frost": true,
"temp_set": 160,
"upper_temp": 350,
"temp_current": 130,
"humidity": 73,
"lower_temp": 50,
"temp_correction": 0,
"factory_reset": false,
"child_lock": false,
"fault": 0
}

[epenet]

Whilst we work on a long-term solution, please check-out
#158944 (comment)

[iAmRenzo]

I have the same issue; but my hvac_modes are not present in the developer tools.

[PaulNBerlin]

Hi guys, is there any progress on that topic? Will it ever been fixed or do we need to find alternative solutions? Thanks a lot for all of your valuable work!

[epenet]

Incorrect datapoints can now (since 2026.5b0) be adjusted using a device quirk: https://github.com/home-assistant-libs/tuya-device-handlers

[movo786]

I have a similar issue with my water heater/geyser showing unknown for heat and only off state. Instead of using the standard climate template I created this custom template. Granted this is only to turn my water heater on and off and display the status:

features:
  - type: toggle
type: custom:mushroom-template-card
entity: switch.geyser_switch
primary: Geyser
secondary: >
  {% set temp = states('sensor.geyser_temp_current') %} {% set work =
  states('sensor.geyser_work_state') %} {{ work }} • {{ temp }}°C
icon: |
  {% if is_state('sensor.geyser_work_state', 'On') %}
    mdi:water-boiler
  {% else %}
    mdi:water-boiler-off
  {% endif %}
tap_action:
  action: toggle
hold_action:
  action: more-info
color: |
  {% if is_state('sensor.geyser_work_state', 'On') %}
    orange
  {% else %}
    grey
  {% endif %}
features_position: bottom
vertical: true

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.