Comfort Automation/ Security System Forums
Wrong date showing on Keypad KP06 - Printable Version

+- Comfort Automation/ Security System Forums (https://www.comfortforums.com)
+-- Forum: Products (https://www.comfortforums.com/forum-3.html)
+--- Forum: UCMs (https://www.comfortforums.com/forum-146.html)
+---- Forum: Ethernet UCM/ETH03 (https://www.comfortforums.com/forum-113.html)
+---- Thread: Wrong date showing on Keypad KP06 (/thread-4379.html)

- mikeinnc - 01-02-2016

The date on my Comfort KP06 keypad is behaving very strangely! This morning - 02 Jan 2016 - at about 8:00am the date said 01 Jan 2016 (01-01-2016), although the time was correct. Using programming mode from the keypad, I set the date to 02-01-2016. Imagine my concern when a little later, I noticed it had reverted to 01-01-2016. The time was still correct, though. I set it to the correct date - again - from the keypad only to find later still it had again reset to 01-01-2016! Looking at the log files, I see the following:

01/01 08:04 Sign in - User # 2
01/02 08:06 Date/Time Change UCM 1  ; I set it correctly
01/02 08:12 Sign in - User # 2               ; still correct....
01/02 08:15 Sign in - User # 2
01/01 09:04 Date/Time Change UCM 1   ; reverts to \'yesterday\'

Note that at 09:04, UCM1 reset to the wrong date! But it gets worse! The time now is 13:25 and the date has changed to read correctly. The corresponding log file entries are here:

01/02 11:44 Date/Time Change 2           ; change it manually again
01/01 12:04 Date/Time Change UCM 1   ; but it gets set back - again!
01/01 13:05 Sign in - User # 2
01/02 13:07 Date/Time Change UCM 1   ; next UCM change is correct!

So you can see I changed the date to 02-01-2016 at 11:44 but UCM1 changed it back at 12:04! Then, at 13:07, UCM1 appears to set it correctly - and it is now \'sticking\'.

For reference,
  • Comfort is Ultra II v7.093.
  • UCM1 is ETH03 v7.075
  • UCM2 is CBus v7.054.
  • The \'Clocks/Timekeeping\' line on the CBus module is OFF.
  • The keypad is KP06 v6.010.
  • Time is synchronised with the Australian pool NTP server at au.pool.ntp.org
  • I\'m in Perth, Western Australia where we do not have DST and 8hrs offset from GMT is set correctly on SNTP setting.
  • The synch interval is set to 60 mins.
So, to me, it looks as though the date is 12 (13?) hours \'wrong\'. Every time I set it correctly before 13:00 or so, it reverted to \'yesterday\' when UCM1 changed it. But, post 13:00, it has been set correctly - and is continuing to show \'today\'.

Any comments gratefully received!

Many thanks - Mike



- slychiu - 01-02-2016

I am seeing the same thing.We will look into it as soon as possible

- mikeinnc - 01-02-2016

A bit more information. It appears it ISN\'T correcting the date! here\'s the latest log entries:

01/02 13:07 Date/Time Change UCM 1
01/02 13:11 Sign in - User # 2
01/02 13:32 Sign in - User # 2
01/01 13:45 Date/Time Change UCM 1     ; so UCM changes it back
01/01 13:46 Sign in - User # 2
01/02 13:47 Date/Time Change UCM 1     ; used \'submit\' button on SNTP dialog
01/01 13:52 Date/Time Change UCM 1     ; ...but UCM changed it back!
01/01 13:55 Sign in - User # 2                  ; still wrong!

So could it be 1 day wrong?

NTP is correct!


- mikeinnc - 01-02-2016

Thanks so much! Smile


- Ingo - 01-02-2016

Same for KP04 and KT03 on Eth03/SNTP connected system. Bus Monitor confirms ETH03 sends back the incorrect date.

- mikeinnc - 01-03-2016

Just to confirm (but I suppose it is already obvious!) that the date this morning is showing 02-10-2016. One day late as expected.


- slychiu - 01-04-2016

Please upgrade the ETH03 Firmware to 2.20 which can be downloaded from https://www.cytech.biz/product_details.php?item_id=400

This was caused by a Leap Year Error


- mikeinnc - 01-04-2016

Thanks very much indeed! That did the trick (although I had to do a manual TFTP transfer of the hex file to ETH03). Date is now correct, and all\'s well again! Great service. Smile

- slychiu - 01-04-2016

All the best to or friends in PerthCool