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
hvac_mode - The current operation (e.g. heat, cool, idle). Used to determine state.
while:
hvac_action - The current HVAC action (heating, cooling)
So climate entity state is not really current state.... And all my climate entities (with hvac_mode === heat) are shown as ON in HA Fusion and there is no difference at all when they are Idle or actually currently heating.
I think for climate entities the actual state for the button should be determined from hvac_action.
Perhaps the following:
Name
Description
HVACMode.HEAT
The device is set to heat to a target temperature.
HVACMode.COOL
The device is set to cool to a target temperature.
HVACMode.HEAT_COOL
The device is set to heat/cool to a target temperature range.
HVACMode.AUTO
The device is set to a schedule, learned behavior, AI.
HVACMode.DRY
The device is set to dry/humidity mode.
HVACMode.FAN_ONLY
The device only has the fan on. No heating or cooling taking place.
I think there is a potential bug in how climate entities state is determined - or it might be a 'feature' of my climate integration (https://github.com/mariusz-ostoja-swierczynski/tech-controllers).
From HA docs:
while:
So climate entity state is not really current state.... And all my climate entities (with
hvac_mode === heat
) are shown as ON in HA Fusion and there is no difference at all when they are Idle or actually currently heating.I think for climate entities the actual state for the button should be determined from
hvac_action
.Perhaps the following:
HVACMode.HEAT
HVACMode.COOL
HVACMode.HEAT_COOL
HVACMode.AUTO
HVACMode.DRY
HVACMode.FAN_ONLY
should be removed from
onStates
store and some specific condition added to https://github.com/matt8707/ha-fusion/blob/main/src/lib/Main/Button.svelte to determine climate state.I can take a stab at a PR if this is real issue (not limited to my old integration).
The text was updated successfully, but these errors were encountered: