card_thermostat gives error when stepping temp up or down manually

[kohlerryan]

Describe the bug
card_thermostat gives error when stepping temp up or down manually. First noticed after upgrade to HA 2024.8.1. Error message appears a bottom of screen. See screenshot for error message.

To Reproduce
Steps to reproduce the behavior:

1. Add card_thermostat with these variables set:

  type: custom:button-card
  template: card_thermostat
  entity: climate.living_room_thermostat
  variables:
    ulm_card_thermostat_name: 'Living Room Thermostat'
    ulm_card_thermostat_enable_collapse: true
    ulm_card_thermostat_enable_controls: true
    ulm_card_thermostat_enable_hvac_modes: true
    ulm_card_thermostat_enable_background_color: true
    ulm_card_thermostat_temp_step: 1.0

2. Click to increase or decrease temp.
3. See error

Expected behavior
Temp should increase by defined step - or default of 1.

Screenshots

Additional context
I attempted to remove variable ulm_card_thermostat_temp_step:, as well as set it as 1 vs 1.0. Same result.

[andrewlelos]

I'm also having this issue!

[Misnaree]

I am also having this issue with the following error: Provided temperature -17.77777777777778 is not valid. Accepted range is 10 to 32.

[gintasb]

I've got the same issue after an update to 2024.8. Seems the issue is only with UI Minimalist.

[suarezcp87]

have the same issue

[andrewlelos]

Downgrading HA to 2024.7.4 fixed this issue for me

[pnaklicki]

Same for me, except it shows that 0.0 is not valid

[gintasb]

same here, it shows that 0.0 is not valid.

[kohlerryan]

Upgraded to 2024.8.3 and have same issue.

[iganeshk]

Found a fix, this seems to be an issue with climate's service_data. My hvac does not support

target_temp_low
target_temp_high

UI/custom_components/ui_lovelace_minimalist/lovelace/ulm_templates/card_templates/cards/card_thermostat.yaml

Lines 228 to 248 in c4079cc

	target_temp_low: |
	[[[
	if (entity.attributes.target_temp_low == null) {
	return 0;
	} else {
	const unit = hass.config.unit_system.temperature
	const step = variables.ulm_card_thermostat_temp_step || entity.attributes.target_temp_step || (unit == '°F' ? 1.0 : 0.5)
	const new_temp = (parseFloat(entity.attributes.target_temp_high) - step)
	return (new_temp - variables.ulm_card_thermostat_minimum_temp_spread < entity.attributes.target_temp_low ? new_temp - variables.ulm_card_thermostat_minimum_temp_spread : entity.attributes.target_temp_low);
	}
	]]]
	target_temp_high: |
	[[[
	if (entity.attributes.target_temp_low == null) {
	return 0;
	} else {
	const unit = hass.config.unit_system.temperature
	const step = variables.ulm_card_thermostat_temp_step || entity.attributes.target_temp_step || (unit == '°F' ? 1.0 : 0.5)
	return (parseFloat(entity.attributes.target_temp_high) - step)
	}
	]]]

UI/custom_components/ui_lovelace_minimalist/lovelace/ulm_templates/card_templates/cards/card_thermostat.yaml

Lines 298 to 315 in c4079cc

	target_temp_low: |
	[[[
	if (entity.attributes.target_temp_low == null) {
	return 0;
	} else {
	return entity.attributes.target_temp_low;
	}
	]]]
	target_temp_high: |
	[[[
	if (entity.attributes.target_temp_high == null) {
	return 0;
	} else {
	const unit = hass.config.unit_system.temperature
	const step = variables.ulm_card_thermostat_temp_step || entity.attributes.target_temp_step || (unit == '°F' ? 1.0 : 0.5)
	return (parseFloat(entity.attributes.target_temp_high) + step)
	}
	]]]

By removing the above lines from card_thermostat.yaml the custom-cards templates under ui_minimalist (default) and of course

• reload UI_minimalist
• reload homepage

now am able to adjust temperature without an issue.