core: climate.set_temperature not working after upgrade to 0.116.0

The problem

Ever since the latest update, setting the temperature by calling climate.set_temperature for my CT-32 thermostat doesn’t work. I’m still able to click on the thermostat and select a temperature manually and it works successfully, but calling climate.set_temperature, either from the developer tools, or from my node-red flows, does nothing. No messages of any form appear in the logs, or in the logbook, and the temperature settings and mode remain as they were.

Environment

Problem-relevant configuration.yaml


Traceback/Error logs


Additional information

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 34 (5 by maintainers)

Most upvoted comments

So apparently we’re ignoring the fact that this had nothing to do with the ozw integration. Because this issue still exists with the new zwave JS integration, and therefore this should not have been closed.

Hi, guys! I’ve the same issue - I got error: “Failed to call service climate/set_temperature. must contain at least one of temperature, target_temp_high, target_temp_low” with service (from documentation)

Set temperature to 24 in heat mode

automation: trigger: platform: time at: “07:15:00” action: - service: climate.set_temperature data: entity_id: climate.someroom temperature: 24 hvac_mode: heat

I was try to change param.name to target_temp_high: 24 but it doesn’t matter Climate device is Gree (C&H) climate device (conditioner w. heating) This issue with version 0.118.4