Thermostat card: should use the Generic Thermostat preset temperature?

[arnaudbreton]

Checklist

• [X] I have updated to the latest available Home Assistant version.
• [X] I have cleared the cache of my browser.
• [X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

Disclaimer: I'm reporting this as a bug as I don't see a consistent feedback but I'm not 100% sure what is the expected behavior

I'm using the Thermostat card combined with Generic Thermostat. Through the built-in scheduler help and automations, I'm setting the Generic Thermostat preset.

The preset name is shown as expected, however, the displayed target temperature remains different from the preset one. From my understanding, the card is displaying the target temperature set for the entity in the configuration.

Describe the behavior you expected

Here's one of my entity which is currently in the "away" preset, configured to 16C, while the card displays 18C:

Steps to reproduce the issue

1. Create a Generic Thermostat (climate) entity, and configure presets.
2. Add a Thermostat card associated to this entity
3. Switch between presets ...

What version of Home Assistant Core has the issue?

2022.12.1

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Brave Version 1.46.134 Chromium: 108.0.5359.94 (Official Build) (x86_64)

Which operating system are you using to run this browser?

macOS Venture

State of relevant entities

hvac_modes: heat, off
min_temp: 15
max_temp: 20
target_temp_step: 0.1
preset_modes: none, away, comfort, home, sleep
current_temperature: 17.4
temperature: 18
hvac_action: idle
preset_mode: away
friendly_name: Chambre
supported_features: 17

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

[popiula]

I am experiencing a similar issue.

In my case, I am using the Thermostat Card together with the Smart Thermostat integration. The prest comfort temperature that I define in configuration.yaml is not the one that appears in the card and it seems the one in the card is the one relevant for the task.

Smart Thermostat settings:

climate:
  - platform: smart_thermostat
    name: Termostato
    unique_id: smart_thermostat_pu
    heater: switch.calefaccion
    target_sensor: sensor.fibaro_salon_air_temperature
    outdoor_sensor: sensor.aemet_temperature
    ac_mode: False
    min_temp: 15
    max_temp: 25
    target_temp: 21.0
    sleep_temp: 17.0
    comfort_temp: 21.0
    away_temp: 17.0
    min_cycle_duration: 00:15:00
    # PID settings:
    keep_alive: #time before update of PID controller
      seconds: 60
    kp : 25
    ki : 10
    kd : 50
    ke : 0.6 # opcional
    # duration of cycle in seconds
    pwm : 00:15:00

Thermostat Card display:

[karwosts]

I don't see a bug here, at least not one in the frontend.

The temperature on the climate card is the one that it is currently trying to reach. When you flipped your thermostat to away mode, the target temperature should have changed to 16C.

The fact that your entity has a temperature attribute of "18" means to me that something changed the target temperature to 18 after away mode was set.

In my generic thermostat I set an away_temp, and then every time I flip it into away mode the target temperature resets to that value. I can change the target temperature afterward, in which case the climate card will reflect the new temperature I set. Nothing says that the target temperature in away mode must always and forever be equal to 16, that's just the initial value when you turn on away mode (or at least it should be).

Do you see anything in your system that disagrees with what I've said here? We can look further at it if that is the case.

[github-actions[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.