ha-dual-smart-thermostat: preset mode being set on wrong entity

Hi - got a strange issue here. Looks like my preset modes are being set on the wrong entity. Notice how the “Dining Room” has two preset modes - and the boys room has none. I’m seeing this in other entities, too. Screenshot 2023-10-17 at 9 44 37 AM

Here is the configuration for these two:

- platform: dual_smart_thermostat
  name: Boys Room
  heater: switch.boys_room_radiator
  cooler: switch.boys_room_air_conditioner
  target_sensor: sensor.boys_room_temperature_temperature
  min_cycle_duration: 60
  precision: .5
  min_temp: 20
  max_temp: 25
  heat_cool_mode: true
  away:
    temperature: 30
    target_temp_low: 50
    target_temp_high: 0

- platform: dual_smart_thermostat
  name: Dining Room
  heater: switch.dining_room_radiator
  target_sensor: sensor.dining_room_thermostat_temperature
  min_cycle_duration: 60
  precision: .5
  min_temp: 20
  max_temp: 25
  away:
    temperature: 15

Is this something on my end? Thanks!

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 25 (9 by maintainers)

Commits related to this issue

Most upvoted comments

Wait with this @mbrevda. I am currently working on this.

I plan to release a beta today or tomorrow.

I detected an issue that the supported features are detected when you change HVAC modes. supported_features sets if the thermostat supports preset mode or not. It’s bugg. Working on the fix. Will be out in 1-2 days