Description

Hello,

Thank you for the recent release. After applying the new update, I was successfully able to add my new device. #4058

Most entities are functioning correctly, but I've encountered an issue with the 'thermal heating mode' entity mapping.

Currently, the 'off' and 'low' (1st level) functions work as expected in Home Assistant. However, the 'high' (2nd level) setting is not working when selected in Home Assistant.

I suspect this is due to a mismatch between the dps_val used in the configuration file and the actual value reported by the Tuya platform.

Configuration Analysis

Based on the referenced YAML file (miro_qtower_humidifier.yaml), the mapping for the 'medium' DPS value is set to 'high' in Home Assistant:

  - entity: select
    name: Heating
    icon: "mdi:radiator"
    category: config
    dps:
      - id: 102
        type: string
        name: option
        mapping:
          - dps_val: "off"
            value: "off"
          - dps_val: low
            value: low
          - dps_val: medium # mismatch ?
            value: high 

Debugging Result from Tuya Platform

When I set the heating level to the 2nd level via the SmartLife App, the Tuya Platform reports the value as "middle".

{
"code": "heating_mode",
"custom_name": "",
"dp_id": 102,
"time": 1765152545034,
"type": "enum",
"value": "middle" // Actual value reported by the device for the 2nd level
}

Proposed Fix

It appears the device reports the 2nd heating level as "middle", not "medium".

The current configuration uses "medium" for the dps_val, but the actual value is likely "middle".

To fix the issue, the dps_val should be changed from "medium" to "middle" in the mapping for the 'high' value.

Thank you for your review and support.

Steps to reproduce

No response

Expected behaviour

No response

Additional context

No response

Confirmation

• I am sure this is a bug or improvement, that is well enough described that it can be implemented.

• This report is for tuya-local, not for localtuya.

• If this is for a specific device, the device config filename is mentioned above, or diagnostics are included.

• Log messages or diagnostics relevant to the issue are included.

• This is not requesting addition of a new device.