ha-dual-smart-thermostat: Preset not displayed on panel, disappears from popup when mode is selected

So I can’t get the presets to work. This is how my config looks: - platform: dual_smart_thermostat initial_hvac_mode: "off" name: Kitchen heater: switch.hvac_w_heat cooler: switch.hvac_y_cool target_sensor: sensor.kitchen_temperature min_temp: 60 max_temp: 80 target_temp: 70 cold_tolerance: 1 hot_tolerance: 0 min_cycle_duration: seconds: 5 keep_alive: minutes: 10 away_temp: 65 eco_temp: 67 comfort_temp: 70 anti_freeze_temp: 60 precision: 1 When restarting HA, the card looks like that (no presets): image

When opening the popup, the presets show up, but don’t work: image

As soon as I select heating, presets dissappear: image

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (13 by maintainers)

Most upvoted comments

oh man! thanks a lot! @ollo69 I will test as soon as published. btw, thanks a lot for the ha-smartthinq-sensors component (I browsed your profile hehe), it is super useful too for scheduling my washer/dryer in the cheapest hours of electricity costs.

Ok, but this means that for now it is correct to disable this, because preset mode should not just be a “label”. It should be clear for you but should confuse most of the users having a preset that simply do nothing.

+1. You are right, I was not using the component “as is”, and that confuses other users. When I find time I will change the yaml configuration to allow the preset dictionary as input in the proposed format.

This should be better analyzed, please provide clear case for this issue (may be open new one). I agree with you that min_cycle_duration is important feature and if really there is an issue it should be fixed.

+1. I will test it asap. But I think I will not find enough time in the following days (a lot of work). Sorry. 😞

@alvarocarrera,

I’m working on this past days, I think I will release a PR tonight or tomorrow. Just to avoid to make job 2 times…

I think we should change the current logic. It feels not handy that if I change to a preset mode and then adjust the target temperatures, the preset mode is gone. The UI is there to make such changes easy, not to go to the yaml configuration.

I am currently going through all features, trying to cover them with tests fully, and I will change this behaviour as such:

  • allow modification of the preset mode target temperatures on the UI without changing back to none
  • restore these on restart or reload as we expect our smart home to work as it was before any reason for restarting
  • apply preset mode temperatures from the yaml only when changing preset modes

@dinostapler @alvarocarrera Please check v0.7.0 and let us know if the issue is fixed. Thanks a lot @ollo69 !