home-assistant/core · error · HomeAssistantError

failed_to_set_clsp

failed_to_set_clsp

Error message

Failed to set cooling setpoint

What it means

HomeAssistantError with translation_key 'failed_to_set_clsp' (cooling setpoint), raised in async_set_temperature when ATTR_TARGET_TEMP_HIGH is provided but set_cooling_setpoint() returns falsy. The gateway did not confirm the cooling setpoint write; the cached target_temperature_high is only updated on success.

Source

Thrown at homeassistant/components/bryant_evolution/climate.py:225

    @override
    async def async_set_hvac_mode(self, hvac_mode: HVACMode) -> None:
        """Set new target hvac mode."""
        if hvac_mode == HVACMode.HEAT_COOL:
            hvac_mode = HVACMode.AUTO
        if not await self._client.set_hvac_mode(hvac_mode):
            raise HomeAssistantError(
                translation_domain=DOMAIN, translation_key="failed_to_set_hvac_mode"
            )
        self._attr_hvac_mode = hvac_mode
        self._async_write_ha_state()

    @override
    async def async_set_temperature(self, **kwargs: Any) -> None:
        """Set new target temperature."""
        if value := kwargs.get(ATTR_TARGET_TEMP_HIGH):
            temp = int(value)
            if not await self._client.set_cooling_setpoint(temp):
                raise HomeAssistantError(
                    translation_domain=DOMAIN, translation_key="failed_to_set_clsp"
                )
            self._attr_target_temperature_high = temp

        if value := kwargs.get(ATTR_TARGET_TEMP_LOW):
            temp = int(value)
            if not await self._client.set_heating_setpoint(temp):
                raise HomeAssistantError(
                    translation_domain=DOMAIN, translation_key="failed_to_set_htsp"
                )
            self._attr_target_temperature_low = temp

        if value := kwargs.get(ATTR_TEMPERATURE):
            temp = int(value)
            fn = (
                self._client.set_heating_setpoint
                if self.hvac_mode == HVACMode.HEAT
                else self._client.set_cooling_setpoint

View on GitHub (pinned to 58a3fdb3ea)

Solutions

  1. Verify gateway connectivity and retry after the next successful coordinator/entity refresh
  2. Reload the integration if failures persist to rebuild the session
  3. Keep the requested setpoint within the thermostat's allowed range
  4. Retry the automation step — transient write failures usually clear immediately
Defensive patterns

Strategy: try-catch

Validate before calling

# Range-check before the call (system-dependent bounds)
MIN_CLSP, MAX_CLSP = 60, 99  # degrees, per your system configuration
if MIN_CLSP <= temp <= MAX_CLSP:
    await climate.async_set_temperature(target_temp_high=temp)

Try / catch

try:
    await climate.async_set_temperature(target_temp_high=75)
except HomeAssistantError as err:
    if 'failed_to_set_clsp' in str(err):
        # setpoint write not acknowledged; retry after gateway recovers

Prevention

When it happens

Trigger: Setting target_temp_high via the climate entity or automation while the gateway is offline or rejects the write; stale client session; value out of the range accepted by the system.

Common situations: Automations lowering cooling setpoints on schedule during gateway downtime; UI slider changes failing after network blips; setpoint outside the system's allowed band.

Related errors

AI-assisted analysis of home-assistant/core@58a3fdb3ea (2026-08-14). Data as JSON: /api/errors/19bb2378f63b37ce. Report an issue: GitHub.