![]() |
|
Date / Time change in Event Log - Printable Version +- Comfort Automation/ Security System Forums (https://www.comfortforums.com) +-- Forum: Support (https://www.comfortforums.com/forum-2.html) +--- Forum: FAQs - Technical (https://www.comfortforums.com/forum-16.html) +--- Thread: Date / Time change in Event Log (/thread-4317.html) |
- mikeinnc - 09-05-2015 When I read my Comfort Event Log, I see that it records a Date / Time change just about every hour of every day! Of course, this fills the Event Log with a lot of entries that are really not at all interesting....... So, my question is - is there any way I can stop a \'Date / Time Change\' being logged. It will make reading the log far easier! Many thanks, as usual. - slychiu - 09-05-2015 Are you using the UCM/ETH03 which is able to synchronise the time wth an Internet Time Server? This could be what is correcting the Comfort time when it becomes a little out The SNTP (Simple Network Time Protocol) button below ![]() The SNTP setting page is below ![]() The NTP synchronise interval is the time between syncs.It is shown as 30 minutes above. If there is a time difference at the time of sync then the time is updated and iit may be recorded to the event log Upgrade to the latest Comfort firmware to reduce the number of events logged In the current firmware, if the time difference is less than 4 seconds, the time is updated but it is not recorded in the event log. 30 or 60 minutes as the update interval should work, as the comfort time will not be so inaccurate as to be out by 4 seconds during this time interval - mikeinnc - 09-05-2015 Thanks very much for that! I\'ve just upgraded to the latest firmware, and, yes, I do use a UCM/ETH03 synchronised to an Australian NTP pool server. I believe this will be a significant improvement - the event log really didn\'t need all those date/time change events!
- mikeinnc - 09-06-2015 Well, now that the new firmware has been in place for > 24 hrs, I thought I\'d check in the event log.....and it hasn\'t made a scrap of difference! Here\'s a sample of the log AFTER the new firmware has been installed. 09/05 18:57 Date/Time Change 18 09/05 20:07 Date/Time Change 18 09/05 21:18 Date/Time Change 18 09/05 22:28 Date/Time Change 18 09/05 23:39 Date/Time Change 18 09/06 00:49 Date/Time Change 18 09/06 01:59 Date/Time Change 18 09/06 03:10 Date/Time Change 18 09/06 04:20 Date/Time Change 18 09/06 05:31 Date/Time Change 18 09/06 06:41 Date/Time Change 18 09/06 07:51 Date/Time Change 18 09/06 09:02 Date/Time Change 18 09/06 10:12 Date/Time Change 18 09/06 11:23 Date/Time Change 18 Nearly every hour there is an entry - just as before. So either my Comfort clock is very poor at keeping time - or the firmware update hasn\'t worked! Is there any manual way to stop these entries - other than turning off the NTP Synch? - juwi_uk - 09-06-2015 I must admit I unchecked the box after a while too on mine as otherwise 90% of my log file were these. - juwi_uk - 09-06-2015 I originally raised this in this thread: http://www.comfortforums.com/forum25/4146-2.html - slychiu - 09-06-2015 Your Comfort clock is probably inaccurate so that if you wait 1 hour the error is too much Can you change the setting to 10 minutes and see what is the result? - juwi_uk - 09-06-2015 Already IS set to 10 mins. But OK i\'ll; enable and monitor again. Will clear down the log first though. J - juwi_uk - 09-06-2015 Yep you can set your watch by an entry going in the log. I knew there was a reason I turned it off again. You cant tell me this isnt a bug. Something is wrong here big time. It is a daylight savings issue? I think I\'ll turn it off again Julian - Ingo - 09-07-2015 I tend to agree with Julian, something is wrong. If NTP adjusted the time then it stands to good reason that the time can run in the corrected state for at least the 10 minutes before the next NTP check. If however there is really something wrong with the RTC then I agree that NTP will keep correcting the time. If however Julian has disabled NTP, and he can verify that the time is correct to within the 4s, or 10s I can\'t remember, of NTP time then we know there is a bug somewhere. Too many people complain about the same thing to be a coincidence. Julian, do a check for us. Set the time to NTP time and check it exactly 24H later to see how far the time drifted. My guess is that it shouldn\'t drift at all because Comforts RTC is very accurate on its own. I will do the same this side. Ingo |