Tried versatile thermostat for my ac, after setup with the "use internal temperature of the underlying" i encountered a loop of set temperature:
i set target temperature on VTherm (example: 23)
because internal temp of my ac is lower than real provided by separate sensor, underlying ac climate entity is set temperature to lower than VTherm set point (example: 21)
in about a minute or so VTherm setpoint changes on its own to 21, underlying ac is set to 19
after another minute it repeats: Vtherm set to 19, underlying to 17
I added debug log to print old_state in _async_climate_changed, which triggers the loop. My bet the problem is that the only attribute that changes is current_temperature (internal temperature of ac), as it naturally lowers after ac is started. Then because underlying climate target temp is lower than VTherm setpoint, _async_climate_changed thinks new temperature is set in underlying ac and updates VTherm setpoint
Tried versatile thermostat for my ac, after setup with the "use internal temperature of the underlying" i encountered a loop of set temperature:
I added debug log to print old_state in _async_climate_changed, which triggers the loop. My bet the problem is that the only attribute that changes is current_temperature (internal temperature of ac), as it naturally lowers after ac is started. Then because underlying climate target temp is lower than VTherm setpoint, _async_climate_changed thinks new temperature is set in underlying ac and updates VTherm setpoint
Debug log
Configuration
My VTherm attributes are the following: