Set temperature action was used with the target temperature parameter but the entity does not support it over_climate from Atlantic AC binded with Zigbee2mqtt

[guich59]

Version of the custom_component

7.1.1

Configuration

My VTherm attributes are the following:

hvac_modes:
  - "off"
  - heat
  - cool
  - auto
  - dry
  - fan_only
min_temp: 16
max_temp: 30
target_temp_step: 0.5
fan_modes:
  - low
  - medium
  - high
  - auto
preset_modes:
  - none
  - activity
  - boost
  - eco
swing_modes:
  - "on"
  - "off"
current_temperature: 21
target_temp_high: 29
target_temp_low: 19.5
fan_mode: high
preset_mode: activity
swing_mode: "on"
friendly_name: Split Bureau
supported_features: 442

Describe the bug

I try to use versatile thermostat with a over_climate to control my Atlantic [GW003-AS-IN-TE-FC] linked using Zigbee2Mqtt (not using Cozytouch bridge because link is very unstable).
Controlling operation seems to work well like fan_mode or preset but I can't make the temp control to work.
For exemple, I've set versatile thermostat component at 25°C (with underlying temp change enabled), but I get the following error from logs (see at end of issue).

It's seems that versatile thermostat cannot set the
target_temp_high or target_temp_low to control the temp.

I'm trying to:
Set underlying component temp using versatile thermostat

And I expect:
Vtherm temp to follow versatile thermostat temp

But I observe this ....
Error in event log saying "Set temperature action was used with the target temperature parameter but the entity does not support it"

I read the documentation on the README.md file and I don't find any relevant information about this issue.

Debug log

Enregistreur: homeassistant.core
Source: core.py:2815
S'est produit pour la première fois: 10 janvier 2025 à 12:58:41 (22 occurrences)
Dernier enregistrement: 10:56:40

Error executing service: <ServiceCall climate.set_temperature (c:01JHA3DVFY6AFFCK2SBW2M0N1F): entity_id=['climate.split_bureau'], target_temp_high=25.5, target_temp_low=25.5, temperature=25.5>
Error executing service: <ServiceCall climate.set_temperature (c:01JHA3Q0F1S2AVA0AMC6SCQBVM): entity_id=['climate.split_bureau'], target_temp_high=27.0, target_temp_low=27.0, temperature=27.0>
Error executing service: <ServiceCall climate.set_temperature (c:01JHABJ0MXDADG361E0RGQYD26): entity_id=['climate.split_bureau'], target_temp_high=23.5, target_temp_low=23.5, temperature=23.5>
Error executing service: <ServiceCall climate.set_temperature (c:01JHABJAEMS5828PH73Y6N3WYA): entity_id=['climate.split_bureau'], target_temp_high=23.5, target_temp_low=23.5, temperature=23.5>
Error executing service: <ServiceCall climate.set_temperature (c:01JHACPPPD7RNYCQHCNSY8FA7M): entity_id=['climate.split_bureau'], target_temp_high=30.0, target_temp_low=30.0, temperature=30.0>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 2815, in _run_service_call_catch_exceptions
    await coro_or_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 2838, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1006, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, entity, func, data, call.context
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1078, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 893, in async_service_temperature_set
    raise ServiceValidationError(
    ...<2 lines>...
    )
homeassistant.exceptions.ServiceValidationError: Set temperature action was used with the target temperature parameter but the entity does not support it.

[guich59]

Just to add a maybe usefull information, "Compensating for the Internal Temperature of the Underlying Equipment" is enabled

[jmcollin78]

Hello

My VTherm attributes are the following:

These are not Vtherm attributes. This is certainly the underlying device attributes.

It's seems that versatile thermostat cannot set the target_temp_high or target_temp_low to control the temp.

VTherm can do it and it is already used by other users.

You have the attribute supported_features: 442 which means 110111010 in binary.
Feature of Climate are defined as follow:

class ClimateEntityFeature(IntFlag):
    """Supported features of the climate entity."""

    TARGET_TEMPERATURE = 1
    TARGET_TEMPERATURE_RANGE = 2
    TARGET_HUMIDITY = 4
    FAN_MODE = 8
    PRESET_MODE = 16
    SWING_MODE = 32
    AUX_HEAT = 64
    TURN_OFF = 128
    TURN_ON = 256
    SWING_HORIZONTAL_MODE = 512

this mean you have TARGET_TEMPERATURE_RANGE but not TARGET_TEMPERATURE as feature available (and others).

And Vtherm consider if you have TARGET_TEMPERATURE_RANGE you also have TARGET_TEMPERATURE. But this asumption is certainly wrong.

[jmcollin78]

Finally I create a beta pre-release, if you can give it a try, it will be in the next release (tomorrow).

https://github.com/jmcollin78/versatile_thermostat/releases/tag/7.1.2.beta1

To install a pre-release you should force the release in HACS.

[guich59]

Hello,
Sorry for the inccorect issue opening content.
But thank you very much for you reactivity, it's seems to be working nicely with 7.1.2beta1 since 7am today :)

[jmcollin78]

ok fine. I will release the fix then. I was waiting for your feedback.

[jmcollin78]

https://github.com/jmcollin78/versatile_thermostat/releases/tag/7.1.2