Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parameters cannot be changed retrospectively (away_temp, sleep_temp; home_temp; eco_Themp) #205

Closed
LHBL2003 opened this issue Feb 6, 2024 · 5 comments

Comments

@LHBL2003
Copy link

LHBL2003 commented Feb 6, 2024

Describe the bug
The parameters (away_temp, sleep_temp; home_temp; eco_Themp) can no longer be subsequently adjusted. Unless you assign a new unique_id, which is not expedient.

To Reproduce
Steps to reproduce the behavior:

  1. Create a smart_thermostat
climate:
  - platform: smart_thermostat
    name: DG - Fußbodenheizung - HASmartThermostat
    unique_id: DG-Fussbodenheizung-HASmartThermostat_Test
    heater: switch.eltako_gw1_00_00_00_50
    target_sensor: sensor.hm_tc_it_wm_w_eu_oeq1668843_temperatur
    outdoor_sensor: sensor.heizgeraet1_aussentemperatur
    min_temp: 5
    max_temp: 24
    ac_mode: False
    target_temp: 21.0
    keep_alive:
      seconds: 300
    away_temp: 20.0
    sleep_temp: 20
    home_temp: 21.0
    eco_temp: 18
    kp: 100
    ki: 0.0
    kd: 0.0
    ke: 0.5
    pwm: 00:15:00
    min_cycle_duration: 180
    min_off_cycle_duration: 180
    target_temp_step: 0.1
    precision: 0.1

2 . Restart HA
3 After this has been created, change the values for *.temp e.g. eco_temp: 5
4. Restart HA
3. Change the mode in the visualization.

Result
The value is not changed as specified in the configuration.

Expected behavior
The setpoint should be adjusted to the value from the configuration.

Screenshots

The value from the config is not used.
Even if the parameter is commented out, the mode is still suggested.
image

The value is only accepted if the unique_id is manipulated.
image

Desktop (please complete the following information):

  • OS: 11.5
  • Browser Chrome
  • Version 121.0.6167.140 (Offizieller Build) (64-Bit)

Additional context
Deleting and recreating the entity does not help either.

At first I thought it was a mistake on my part, but now I think it's a bug.
This discussion is therefore rather superfluous.
#204

@ScratMan
Copy link
Owner

ScratMan commented Feb 7, 2024

That's not a bug, it's a feature. The values in YAML are only used at first start or after crashing or cleaning of the HA recorder database.
Once HA is running, please use the services to adjust preset temperatures or PID gains.

This has been added a while ago so the users can easily adjust the preset temperatures and gains without requiring to reboot HA.

@ScratMan ScratMan closed this as not planned Won't fix, can't repro, duplicate, stale Feb 7, 2024
@LHBL2003
Copy link
Author

LHBL2003 commented Feb 8, 2024

@ScratMan

I have already searched for setting options under Devices and Entities. And now again. But I can't find this anywhere. Can you help me to find it. Via a picture or directions?

@ScratMan
Copy link
Owner

ScratMan commented Feb 8, 2024

Follow the link button :
Open your Home Assistant instance and show your service developer tools.

@LHBL2003
Copy link
Author

LHBL2003 commented Feb 8, 2024

Oh man, I would never have guessed that. I went to devices and services.
And searched up and down in the entity. :D
That's very hidden.
I've learnt something new again. Thank you.

@LHBL2003
Copy link
Author

Thank you, that worked perfectly. Even if it is quite hidden.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants