Climate side effect in 0.96 / make behavior more predictable

Tags: #<Tag:0x00007f3f16f43358>

This is not really a bug and too minor to be a feature request, but I thought I’d post it here so it might be noticed by the Climate developers.

I have an Ecobee thermostat and a Mitsubishi AC unit connected via MQTT. I’ve made the changes required for the 0.96 reorganization of the Climate component & noticed that if I turn off/on the climate entities using a service call, they always turn on in the hvac_mode of heat regardless of previous setting.

Is turning on in hvac_mode of heat a new default behavior? If so, is it possible change the default behavior such that the previous hvac_mode state is restored after an off/on cycle? This will make the component behavior more predictable.