Did you try rebooting the controller ? ..... Give it several minutes after it reboots for it to check in with the time server and update the time - sometimes the time will be wrong for a couple of minutes after a reboot.
Clock change (daylight saving) on Evotouch
Collapse
X
-
....and to add to the intrigue....I have just used the controller to set an override on my hot water to be on until 1600 (in old money - GMT). My phone app is showing the DHW override as on until 1700! Intriguing that the controller and the phone app will display an override instruction in different time offsets.
Comment
-
-
Originally posted by Edinburgh2000 View Post....and to add to the intrigue....I have just used the controller to set an override on my hot water to be on until 1600 (in old money - GMT). My phone app is showing the DHW override as on until 1700! Intriguing that the controller and the phone app will display an override instruction in different time offsets.
If I didn't know better I would say that the iPhone app was switching to BST correctly and the controller (last year for me anyway) had not switched until a week later!
Comment
-
-
Originally posted by John Cooper View PostYes, set to UTC.
Have two controllers, new WiFi model, I think both on the latest firmware but I will check.
They are both on the same Total Connect account.
One of them updated automatically - one did not.
--
John Cooper
The one that updated automatically is 01.00.02.01 the one that failed is 01.00.03.00, does that fit the pattern for anyone else?
To try and get it to update I have tried turning the WiFi off and on again, and also forcing a reboot by taking the batteries out. Neither works.
I have noticed that when the WiFi is off the setting is Daylight Saving manual/auto and when Wifi connected the wording is Auto update (Wifi) off/on. On reconnecting Wifi the former wording persists for a while and the setting reverts to manual. I am puzzled as to how it can do auto summer time updates when not connected to the Internet.
Looks like the later firmware is faulty.
--
John Cooper
Comment
-
-
Originally posted by John Cooper View Post
Looks like the later firmware is faulty.
--
John Cooper
Comment
-
-
A workaround
A workaround that I have applied is to go into the Honeywell Total Connect Comfort website and edit my "Location", setting the Timezone to "(UTC+01:00) West Central Africa". I think that is a timezone that does not observe DST and so is always UTC+1. That seems to have worked for me. The hour offset for overrides between my Evotouch and the web app has disappeared. Of course, we will need to remember to change this come the reversion to GMT in the autumn. But, for now, that seems to do the trick.
Comment
-
-
As far as the differences in wifi firmware are concerned, Honeywell did push the 03 firmware to my device when I reported a stuck clock on my Evotouch. I have also found Honeywell to be a first-class company to deal with, and I cannot believe that they would just push the new firmware to my device to keep me quiet. As I said earlier, this is one for Honeywell to give a view on.
Comment
-
-
Originally posted by Edinburgh2000 View PostA workaround that I have applied is to go into the Honeywell Total Connect Comfort website and edit my "Location", setting the Timezone to "(UTC+01:00) West Central Africa". I think that is a timezone that does not observe DST and so is always UTC+1. That seems to have worked for me. The hour offset for overrides between my Evotouch and the web app has disappeared. Of course, we will need to remember to change this come the reversion to GMT in the autumn. But, for now, that seems to do the trick.
Comment
-
-
Originally posted by DBMandrake View PostThe only acknowledged change in the new 03 firmware is additional European country/language support.
So I'm not sure why we're all assuming it might have some bearing on a time related bug.
If it also fixes any bugs they're sure not talking about it.
Comment
-
-
Originally posted by Edinburgh2000 View PostBut that would not stop you moving it to West Africa. Both would be on UTC+1, which is what you need?
Said that without looking. Time zone is not per account in any case, I can have the controllers in different time zones.
Thanks for the suggestion.
Comment
-
-
I have the same problem - firmware 1.00.03.00 and WiFi 01.00.02.00. As far as I can see from my router logs, there is no direct attempt to connect to an NTP server, and the rest of my home network is showing the correct time, so I think the time is being taken from a Honeywell server which has the wrong configuration for the GMT timezone. This should say what offset to apply for DST and when. From an earlier comment, it looks as though the 'when' part is mis-configured for the UK. I have copied this post to Honeywell support and hopefully they will fix quickly. In the meantime, sticking with manual time setting on controller!!
Comment
-
Comment