In the past few days I noticed that my heating system would sometimes stop - as if had reached the target temperature - even when the temperature was quite low. The thermostat is set to different target temperatures depending whether the location mode is “away”, “day” or “night” - the usual behavior.
I’ve started monitoring the log files, and during the last two early mornings I’ve noticed this sequence of events:
- Around 5am mode switches from “night” to “day”; as a result the thermostat temperature target is set to X.
- At “some point later” (6:13am today), during a regular time-polling based event, the thermostat app retrieved location.mode, and that value was - instead of the expected “day” - “away”.
- As a result, the thermostat target was set to Y
- One polling cycle later (5 minutes later), the thermostat app retrieved location.mode, and this time it was correctly reported as “day”; temperature target was set again at X.
The change in mode was not reported as an event (several apps are subscribed to that event, and none was triggered); it looks like location.mode “just” returned wrong (old?) information for a short amount of time, and I have no way to trace why that happened. This behavior doesn’t seem to happen frequently, but I have seen it fairly often now during the last few days, and typically happening after several minutes/one hour after the mode has changed.
Has anyone else seen anything similar?