Missing "full ON" mode for Tuya Valve Radiator Thermostat device

[SerVB]

The problem

I have the following device:

The problem is that there are only two modes: off and target temperature (called "heat/cool" in HA). See the screenshot. But using controls on the thermostat itself, I can also switch it to "full ON" mode.

The current workaround I use is to set mode to "target temp: 30 C", but sometimes its internal sensor reaches this temp while it's still not warm enough in the center of the room where I have my actual temp sensor. And heating stops until the thermostat itself cools down.

If the "full ON" mode in HA was available, I would just use it so the heating would be without pausing.

P.S.: "heat/cool" name is also not perfect: the thermostat is for a heating radiator, so it should be probably called just "heat".

What version of Home Assistant Core has the issue?

core-2024.4.3

What was the last working version of Home Assistant Core?

No response UPD: as long as I use it (even before the new method: even when auth via Tuya Website with a developer account was required), for more than a year I guess, this device is without the 3rd mode.

What type of installation are you running?

Home Assistant Container

Integration causing the issue

integration: tuya

Link to integration documentation on our website

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

Diagnostics information

tuya-5ec150b179d587719747874860481499-Near door-63a1ed2f90890615e250f377b56c6532.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Docker Container: lscr.io/linuxserver/homeassistant

[home-assistant[bot]]

Hey there @tuya, @zlinoliver, @frenck, 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)}}

[issue-triage-workflows[bot]]

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.

[SerVB]

The problem is still actual: no "full ON" mode