Closed anpavlov closed 1 month ago
Really strange. It's look like a bug. I have pretty the same configuration without this behavior.
Hello, I improve the behavior when the underlying temperature change and it may fix this issue.
Can you please give it a try and let me know: https://github.com/jmcollin78/versatile_thermostat/releases/tag/6.3.4
Don't hesitate to reopen if you think this issue is still there.
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: