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
We started to restore (turn off) the system. We ran this to change the mode, but we did not get this far before...
At the same time another TRV started to want heat
We handled this request straight away
This was considered to be us starting override mode, and so we stored the current settings of the thermostat, which was still the previous overridden temperature, since the stop action had not finished.
You can see setting temperature to 16.5 for climate.thermostat twice in the log. I think one of them must be the delayed/awaited stop call and one must be the new override.
Hope that makes sense. Seems like a problem caused by async/threads. Not sure right now how best to fix it ...
The text was updated successfully, but these errors were encountered:
Same symptom as #24 (heating stays on when no thermostats want it) but a different cause. See this log (extra debugging added by me previously):
What seems to have happened was this
You can see
setting temperature to 16.5 for climate.thermostat
twice in the log. I think one of them must be the delayed/awaitedstop
call and one must be the new override.Hope that makes sense. Seems like a problem caused by async/threads. Not sure right now how best to fix it ...
The text was updated successfully, but these errors were encountered: