This is very odd... I sent a DT command to Comfort to set the time manually. Comfort is the time Master and this is what I saw in PICED log file: ------------------------Toolkit Application Log------------------------ -------------------------2010/05/28 22:54:03------------------------- Project Name: MIDSTRM Network Address: 254 Network Name: Local Network Number of events: 4 Recorded between 2010/05/28 22:53:56 and 2010/05/28 22:53:59 DateTime= 2010/05/28 22:53:56 App= 056 Lighting Group= 010 Group 10 - Keepalive Feedback Unit= 018 Event= Group off DateTime= 2010/05/28 22:53:57 App= 223 Clock and Timekeeping Group= N/A Unit= 018 Event= Date Broadcast: Date set to Monday 2010-05-28. DateTime= 2010/05/28 22:53:58 App= 223 Clock and Timekeeping Group= N/A Unit= 018 Event= Time Broadcast: Time set to 22:54:00. Daylight saving offset set to 0 hours. DateTime= 2010/05/28 22:53:59 App= 000 Group= 000 Unit= 000 Event= LOG PAUSED Can you spot the 'funny' ??? Is this a cosmetic bug or something real? Ingo
It seems the problem is on the Comfort side. I used the Cbus Diagnostic utility to send a DT update and then Comfort replies with the incorrect day. I've posted on the Comfort forum to see if there are any bugs in the current firmware relating to this. Ingo
We recently discovered some problems with date and time behaviour on the Comfort... I understand they have been advised of this but I don't know what the status is. Nick
