climate.set_temperature requires too much information for heat/cool thermostats

[ve6rah]

The problem

When calling climate.set_temperature, you are required to send all of hvac_mode, target_temp_low, target_temp_high even when you only want to set one of those three values. This generates unnecessary traffic on low bandwidth modes (e.g. z-wave), requires additional templating in automations when trying to leave one of the other values at "whatever it was before", and doesn't play nice with some thermostats (e.g. CT32)

Considering that manual temperature changes through lovelace thermostat cards only send the one value you're trying to change, and not all 3, it seems that there is no technical reason to force the user to enter the other information if they do not want it changed, and several problems would be solved by removing the requirement.

What is version of Home Assistant Core has the issue?

core-2021.3.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

climate

Link to integration documentation on our website

https://www.home-assistant.io/integrations/climate

Example YAML snippet

service: climate.set_temperature
target:
  device_id: 621ca738187f2fb3809f05937a0d63b9
data:
  target_temp_low: 21.5

Anything in the logs that might be useful for us?

Failed to call service climate/set_temperature. some but not all values in the same group of inclusion 'temperature' @data[<temperature>]

This would fix several open bugs, while at the same time making automating things much easier.

[probot-home-assistant[bot]]

climate documentation climate source _{^{(message by IssueLinks)}}

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

[ve6rah]

Issue still exists with latest versions

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

[ve6rah]

Issue still exists in latest versions

[frank-dusign]

Still exists in 2021.10.4. Additional findings. Service Viessmann ViCare: Set vicare mode requires to pick an entity, but the system does not offer any.

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

[ve6rah]

Issue still exists in latest versions

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

[ve6rah]

Issue still exists in latest versions

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

[ve6rah]

Issue still exists in latest versions

[sresam89]

Issue still exists on the latest version

[issue-triage-workflows[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.

[ve6rah]

Issue still exists in latest versions

[issue-triage-workflows[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.

[ve6rah]

Issue still exists in latest versions

[issue-triage-workflows[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.

[ve6rah]

Issue still exists in latest versions

[issue-triage-workflows[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.

[ve6rah]

Issue still exists in latest versions

[rrooggiieerr]

@ve6rah I love your perseverance to keeping this issue alive. Looking into it it seems to be integration specific. For instance in the generic_thermostat only a temperature or hvac_mode can be set for climate.set_temperature and none of them are mandatory. I think you should direct your issue to the right integration which in your case seems to be the radiotherm integration.

[ve6rah]

@ve6rah I love your perseverance to keeping this issue alive. Looking into it it seems to be integration specific. For instance in the generic_thermostat only a temperature or hvac_mode can be set for climate.set_temperature and none of them are mandatory. I think you should direct your issue to the right integration which in your case seems to be the radiotherm integration.

This was originally under the ancient z-wave integration, however at that time it was pointed out that it was not integration specific, and was very much an issue with core. I've double checked, this is not integration specific. Currently I am using this through zwave JS UI, however I've also tried through the last three z wave integrations, and they were all the same. After investigating it further it is very much part of climate.set_temperature. I would bet that if your HVAC mode was heat/cool, it would force you to set both a high and low temperature, with no ability to set only the one temperature you are interested in.

[rrooggiieerr]

Yes, you're right, could very well be it's the HVAC mode of my generic_thermostat that is limiting the options

[ve6rah]

As I said in this issue, I have proven that it is not your thermostat limiting it. It is home assistant that is artificially requiring more information than needs to be sent.

[issue-triage-workflows[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.

[ve6rah]

Issue still exists in latest versions

[AJolly]

I'm having the same issue.

[TrueBankai416]

i dont have a fix for this issue but i think I figured out a reliable solution in node-red on home-assistant

[TrueBankai416]

flows.json