I have experienced similar problems when programming software using week numbers involving dates at the end and start of the year when the day falls into the year before or after\'s week number. Might be easier to give a couple of examples...
01 January 2006 fell into week 52 of 2005
31 December 2007 fell into week 1 of 2008
http://personal.ecu.edu/mccartyr/isowdcal.html
This is probably none related but I thought it was worth mentioning just in case.
Good point. We will investigate if this is related to the problem
Ive also got some logic which turns on xmas trees only in december, and up to the 6th Jan.
It\'s still being triggered - heres the code. Even on the 8th Jan it still triggered
If Month = 12 Then
Do XMASLightsON-DO []
End If
If Month = 1 Then
If Day < 7 Then
Do XMASLightsON-DO []
End If
End If
(Newer version of Comfigurator and firmware than original report of this problem - so apologies if I shouldn\'t be posting to a 2-year-old thread, but I couldn\'t find a solution in that thread and am assuming it hasn\'t been resolved??)
NightTime logic appears to have stopped working again on Dec 31 2009. I don\'t know the logic behind the week numbers, but could this be because day 365 is week 53 and there is no Sunset time for week 53? (Using Comfigurator 3.1.3.0 on Comfort II Ultra firmware 5.145.)
No time to test properly now, but have executed a response from within Comfigurator which turns on external lights at Sunset and turns them off at Sunrise. This has worked correctly for years (originally with hard-coded times and converted to NightTime logic when this became available), but today it\'s turning the lights off instead of on. This gets repeated every hour (in case the lights are manually turned off at night or on during the day), so I hope the darkness won\'t attract any unwelcome visitors!
Obviously it\'s too late do anything now - I just hope this doesn\'t happen again at the end of 2010!
Oops - missed that - apologies. Thanks Chiu.