Overnight it seems our Evotouch has got a bit confused about what the time is, and this has lead to the heating being off when I got up this morning more than an hour after the scheduled on time of the downstairs zones.
I got up to make a bottle for a 2 month old and as that happens at a different time every day I was a bit disorientated as to what the actual time was... when I came down stairs and looked at the evotouch it reported the time as somewhere around 7:30am (can't remember exactly unfortunately) with the bedroom scheduled to 17 degrees and all other zones to 5 degrees, which is our overnight schedule. The boiler was off and the nearby radiators were cold.
Again, I couldn't quite remember what time the downstairs was scheduled to come on on a weekend as I've changed it a couple of times in the last few months, so I assumed it was 8am which is one of the times it has been in the past. I thought about manually turning individual zones on but then thought why not use custom mode, but I couldn't remember what that was scheduled for either as I never use custom. So I checked that and found is configured to come on to 20 degrees at 7am for all rooms except the bedroom. Perfect.
So I enabled custom mode and all the relevant zones came on. I walked away and then checked my phone, only to discover the time was really just after 8:30am and that the heating should have been on for at least an hour already. Huh ?
I went back to the evotouch and turned off the custom quick action and all the zones remained on as they should have originally been and the time on the screen jumped forward about an hour to the correct time at the instant I cancelled the quick action. Hmmm... I took a photo of the screen just after I turned off the quick action:
![]()
The Bathroom schedule for Sunday is 20 degrees from 7:30am to 10am then 16 degrees from 10am to 8pm. From that it's clear that the Bathroom should have been up to 20 degrees long ago - especially when I use optimal start. Concerned that there may have been a glitch in operation I decided to do a battery out reboot of the controller.
The interesting thing is when it came back on the time was wrong once again, this time it had jumped to Saturday 11:09am - the previous day:
![]()
After a few seconds I went into Settings, and at the moment I did that the time jumped back to the correct time and date, presumably by adjusting the time online as I have wifi time adjustment enabled. However, the zone set points remained at what they would have been for 11:09am on Saturday:
![]()
It's not until I enabled then cancelled the OFF quick action that suddenly the set points were correct again for the current, actual time:
![]()
So there seems to be a couple of things going on here:
1) It looks like some time overnight the controller received a bad time update from the the time server(s) it uses, causing the time to be about an hour behind the real time. It's unclear whether the controller uses standard ntp protocol, whether it uses one or more public servers or whether it uses honeywell servers.
2) Even after a later time update occurs that corrects the time, the set points do not change to reflect the corrected time until a quick action is manually actioned, or perhaps until a scheduled set point change occurs.
Anyone else notice a problem this morning ? I'm tempted to turn off the wifi time update as I suspect that a bad time update was the cause of the problem, however the fact that the set points do not automatically adjust to the new time when the time is corrected again may be a bug.
It's also a little worrying that the date and time was completely wrong after rebooting the device - does it have no real time clock and rely on the online time server to set the time after a reboot ? If I had wifi time update turned off would the date and time remain wrong after a reboot of the controller ?
I got up to make a bottle for a 2 month old and as that happens at a different time every day I was a bit disorientated as to what the actual time was... when I came down stairs and looked at the evotouch it reported the time as somewhere around 7:30am (can't remember exactly unfortunately) with the bedroom scheduled to 17 degrees and all other zones to 5 degrees, which is our overnight schedule. The boiler was off and the nearby radiators were cold.
Again, I couldn't quite remember what time the downstairs was scheduled to come on on a weekend as I've changed it a couple of times in the last few months, so I assumed it was 8am which is one of the times it has been in the past. I thought about manually turning individual zones on but then thought why not use custom mode, but I couldn't remember what that was scheduled for either as I never use custom. So I checked that and found is configured to come on to 20 degrees at 7am for all rooms except the bedroom. Perfect.
So I enabled custom mode and all the relevant zones came on. I walked away and then checked my phone, only to discover the time was really just after 8:30am and that the heating should have been on for at least an hour already. Huh ?
I went back to the evotouch and turned off the custom quick action and all the zones remained on as they should have originally been and the time on the screen jumped forward about an hour to the correct time at the instant I cancelled the quick action. Hmmm... I took a photo of the screen just after I turned off the quick action:
The Bathroom schedule for Sunday is 20 degrees from 7:30am to 10am then 16 degrees from 10am to 8pm. From that it's clear that the Bathroom should have been up to 20 degrees long ago - especially when I use optimal start. Concerned that there may have been a glitch in operation I decided to do a battery out reboot of the controller.
The interesting thing is when it came back on the time was wrong once again, this time it had jumped to Saturday 11:09am - the previous day:
After a few seconds I went into Settings, and at the moment I did that the time jumped back to the correct time and date, presumably by adjusting the time online as I have wifi time adjustment enabled. However, the zone set points remained at what they would have been for 11:09am on Saturday:
It's not until I enabled then cancelled the OFF quick action that suddenly the set points were correct again for the current, actual time:
So there seems to be a couple of things going on here:
1) It looks like some time overnight the controller received a bad time update from the the time server(s) it uses, causing the time to be about an hour behind the real time. It's unclear whether the controller uses standard ntp protocol, whether it uses one or more public servers or whether it uses honeywell servers.
2) Even after a later time update occurs that corrects the time, the set points do not change to reflect the corrected time until a quick action is manually actioned, or perhaps until a scheduled set point change occurs.
Anyone else notice a problem this morning ? I'm tempted to turn off the wifi time update as I suspect that a bad time update was the cause of the problem, however the fact that the set points do not automatically adjust to the new time when the time is corrected again may be a bug.
It's also a little worrying that the date and time was completely wrong after rebooting the device - does it have no real time clock and rely on the online time server to set the time after a reboot ? If I had wifi time update turned off would the date and time remain wrong after a reboot of the controller ?