You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some thermostat devices (such as air conditioning with heat/cool) only support a temperature range, identified by the SUPPORT_TARGET_TEMPERATURE_RANGE flag. These thermostats don't have a single temperature attribute, but instead use two seperate attributes for the high and low setpoints (target_temp_high and target_temp_low respectively).
Currently, trying to use one of these thermostats with Schedy results in multiple warnings, and the setpoints not being adjusted as per the schedule:
WARNING schedy_heating: !!! [R:back_room] [A:climate.back_room] Thermostat has no attribute named 'temperature'. Available are
['entity_id', 'state', 'attributes', 'last_changed', 'last_updated', 'context', 'hvac_modes', 'min_temp', 'max_temp', 'current_temperature', 'target_temp_high', 'target_temp_low', 'hvac_action', 'friendly_name', 'supported_features']. Please check your config!
WARNING schedy_heating: !!! [R:back_office] [A:climate.back_room] The value None of attribute 'temperature' is no valid temperature.
ERROR schedy_heating: !!! [R:back_office] [A:climate.back_room] Invalid target temperature, ignoring thermostat.
Are there any configuration changes available that would make these usable with Schedy?
The text was updated successfully, but these errors were encountered:
Some thermostat devices (such as air conditioning with heat/cool) only support a temperature range, identified by the
SUPPORT_TARGET_TEMPERATURE_RANGE
flag. These thermostats don't have a singletemperature
attribute, but instead use two seperate attributes for the high and low setpoints (target_temp_high
andtarget_temp_low
respectively).Currently, trying to use one of these thermostats with Schedy results in multiple warnings, and the setpoints not being adjusted as per the schedule:
Are there any configuration changes available that would make these usable with Schedy?
The text was updated successfully, but these errors were encountered: